{ "schemaVersion": "1.0", "item": { "slug": "powerpoint-pptx", "name": "PowerPoint PPTX", "source": "tencent", "type": "skill", "category": "效率提升", "sourceUrl": "https://clawhub.ai/ivangdavila/powerpoint-pptx", "canonicalUrl": "https://clawhub.ai/ivangdavila/powerpoint-pptx", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/powerpoint-pptx", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=powerpoint-pptx", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "SKILL.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "slug": "powerpoint-pptx", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T22:03:16.778Z", "expiresAt": "2026-05-07T22:03:16.778Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=powerpoint-pptx", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=powerpoint-pptx", "contentDisposition": "attachment; filename=\"powerpoint-pptx-1.0.1.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "powerpoint-pptx" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/powerpoint-pptx" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/powerpoint-pptx", "agentPageUrl": "https://openagent3.xyz/skills/powerpoint-pptx/agent", "manifestUrl": "https://openagent3.xyz/skills/powerpoint-pptx/agent.json", "briefUrl": "https://openagent3.xyz/skills/powerpoint-pptx/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "When to Use", "body": "Use when the main artifact is a Microsoft PowerPoint presentation or .pptx deck, especially when layouts, templates, placeholders, notes, comments, charts, extraction, editing, or final visual quality matter." }, { "title": "1. Choose the workflow before touching the deck", "body": "Reading text, editing an existing deck, rebuilding from a template, and creating from scratch are different jobs with different failure modes.\nFor text extraction or inspection, read the deck before editing it.\nText extraction plus thumbnail-style visual inspection is safer than editing from shape assumptions alone.\nFor template-driven work, inventory the deck before replacing content.\nFor deep edits, remember a .pptx file is OOXML with separate parts for slides, layouts, masters, media, notes, and comments.\nIf a template exists, template fidelity beats generic slide-design instincts.\nReusing or duplicating a good existing slide is often safer than rebuilding it and hoping the theme still matches." }, { "title": "2. Inventory the deck before replacing content", "body": "Count the reusable layouts, real placeholders, notes, comments, media, and recurring typography or color patterns first.\nPlaceholder indexes and layout indexes are not portable assumptions.\nInspect the actual slide or template before targeting title, body, chart, or image shapes.\nSpeaker notes, comments, and linked assets can live outside the visible slide surface.\nA missing or wrong placeholder target can silently land content in the wrong box or wrong layer.\nMaster and layout settings can override local slide edits, so the visible problem is not always on the slide you are editing." }, { "title": "3. Match content to the actual placeholders", "body": "Count the actual content pieces before choosing a layout.\nPick layouts based on the real number of ideas, columns, images, or charts the slide needs.\nDo not force two ideas into a three-column slide or cram dense text under a chart.\nCategory counts and data series lengths must match or charts will break in ugly ways.\nExplicit sizing beats wishful thinking: text boxes, images, and charts need real space, not \"it should fit\".\nDo not choose a layout with more placeholders than the content can meaningfully fill.\nQuote layouts are for real quotes, and image-led layouts are for slides that actually have images.\nFor chart-, table-, or image-heavy slides, full-slide or two-column layouts are usually safer than stacking dense text above the visual." }, { "title": "4. Preserve the deck's visual language", "body": "Theme, master, and layout files usually decide fonts, colors, and hierarchy more than any one slide does.\nStart from the deck's actual theme, fonts, spacing, and aspect ratio instead of improvising a new style.\nReuse the deck's own alignment and spacing system instead of inventing a second visual language.\nUse common fonts for portability and strong contrast for readability.\nPreserve the template's visual logic first; originality matters less than not breaking the deck's existing language.\nCombining slides from multiple sources requires normalizing themes, masters, and alignment afterward." }, { "title": "5. Run content QA and visual QA separately", "body": "Text overflow, bad alignment, clipped shapes, weak contrast, and placeholder leftovers are normal first-pass failures.\nRun both content QA and visual QA; missing text and broken layout are different failure classes.\nRender or inspect the actual deck output before delivery when layout matters.\nSearch for leftover template junk, sample labels, and placeholder text before calling the deck finished.\nCheck notes, comments, labels, legends, and chart/table semantics separately from the visual pass.\nA deck can pass text extraction and still fail on overlap, clipping, wrong theme inheritance, or broken notes.\nThumbnail grids and rendered slides usually reveal layout bugs faster than code or text inspection.\nAssume the first render is wrong and do at least one fix-and-verify cycle before calling the deck finished.\nRe-check affected slides after each fix because one spacing change often creates another issue." }, { "title": "6. Keep decks portable and review-safe", "body": "Template masters can override direct edits in surprising ways.\nComplex effects may degrade across PowerPoint, LibreOffice, and conversion pipelines, so keep important content robust without them.\nImage sizing, font substitution, and placeholder mismatch are common reasons a deck looks good in code and bad on screen.\nNotes, comments, linked media, and merged decks can stay broken even when the visible slide looks fine." }, { "title": "Common Traps", "body": "Placeholder text and sample charts often survive template reuse if not explicitly replaced.\nDirectly editing one slide can fail if the real issue lives in the master or layout.\nCharts, icons, and text boxes need enough space; near-collisions are usually visible only after rendering.\nLayout indexes vary by template, so built-in assumptions from one deck often break in another.\nA missing placeholder or wrong shape target can silently put content in the wrong place.\nCounting the text ideas after choosing the layout usually leads to empty placeholders, weak hierarchy, or leftover template junk.\nFont substitution can move line breaks and wreck careful spacing.\nSpeaker notes, comments, and linked media can stay broken even when the visible slide looks fine.\nA deck can pass text inspection and still fail visually because of overlap, contrast, or edge clipping.\nEditing from one slide alone can miss the real source of truth in the theme, master, or layout definitions.\nChoosing a quote, comparison, or multi-column layout without matching content usually makes the deck look templated rather than intentional.\nCombining or duplicating slides without checking masters and themes can create subtle inconsistency slide by slide.\nAspect-ratio mismatches like 16:9 versus 4:3 can shift every placement decision even when each slide looks locally reasonable." }, { "title": "Related Skills", "body": "Install with clawhub install if user confirms:\n\ndocuments — Document workflows that often feed presentation content.\ndesign — Visual direction and layout decisions.\nbrief — Concise business messaging for slide narratives." }, { "title": "Feedback", "body": "If useful: clawhub star powerpoint-pptx\nStay updated: clawhub sync" } ], "body": "When to Use\n\nUse when the main artifact is a Microsoft PowerPoint presentation or .pptx deck, especially when layouts, templates, placeholders, notes, comments, charts, extraction, editing, or final visual quality matter.\n\nCore Rules\n1. Choose the workflow before touching the deck\nReading text, editing an existing deck, rebuilding from a template, and creating from scratch are different jobs with different failure modes.\nFor text extraction or inspection, read the deck before editing it.\nText extraction plus thumbnail-style visual inspection is safer than editing from shape assumptions alone.\nFor template-driven work, inventory the deck before replacing content.\nFor deep edits, remember a .pptx file is OOXML with separate parts for slides, layouts, masters, media, notes, and comments.\nIf a template exists, template fidelity beats generic slide-design instincts.\nReusing or duplicating a good existing slide is often safer than rebuilding it and hoping the theme still matches.\n2. Inventory the deck before replacing content\nCount the reusable layouts, real placeholders, notes, comments, media, and recurring typography or color patterns first.\nPlaceholder indexes and layout indexes are not portable assumptions.\nInspect the actual slide or template before targeting title, body, chart, or image shapes.\nSpeaker notes, comments, and linked assets can live outside the visible slide surface.\nA missing or wrong placeholder target can silently land content in the wrong box or wrong layer.\nMaster and layout settings can override local slide edits, so the visible problem is not always on the slide you are editing.\n3. Match content to the actual placeholders\nCount the actual content pieces before choosing a layout.\nPick layouts based on the real number of ideas, columns, images, or charts the slide needs.\nDo not force two ideas into a three-column slide or cram dense text under a chart.\nCategory counts and data series lengths must match or charts will break in ugly ways.\nExplicit sizing beats wishful thinking: text boxes, images, and charts need real space, not \"it should fit\".\nDo not choose a layout with more placeholders than the content can meaningfully fill.\nQuote layouts are for real quotes, and image-led layouts are for slides that actually have images.\nFor chart-, table-, or image-heavy slides, full-slide or two-column layouts are usually safer than stacking dense text above the visual.\n4. Preserve the deck's visual language\nTheme, master, and layout files usually decide fonts, colors, and hierarchy more than any one slide does.\nStart from the deck's actual theme, fonts, spacing, and aspect ratio instead of improvising a new style.\nReuse the deck's own alignment and spacing system instead of inventing a second visual language.\nUse common fonts for portability and strong contrast for readability.\nPreserve the template's visual logic first; originality matters less than not breaking the deck's existing language.\nCombining slides from multiple sources requires normalizing themes, masters, and alignment afterward.\n5. Run content QA and visual QA separately\nText overflow, bad alignment, clipped shapes, weak contrast, and placeholder leftovers are normal first-pass failures.\nRun both content QA and visual QA; missing text and broken layout are different failure classes.\nRender or inspect the actual deck output before delivery when layout matters.\nSearch for leftover template junk, sample labels, and placeholder text before calling the deck finished.\nCheck notes, comments, labels, legends, and chart/table semantics separately from the visual pass.\nA deck can pass text extraction and still fail on overlap, clipping, wrong theme inheritance, or broken notes.\nThumbnail grids and rendered slides usually reveal layout bugs faster than code or text inspection.\nAssume the first render is wrong and do at least one fix-and-verify cycle before calling the deck finished.\nRe-check affected slides after each fix because one spacing change often creates another issue.\n6. Keep decks portable and review-safe\nTemplate masters can override direct edits in surprising ways.\nComplex effects may degrade across PowerPoint, LibreOffice, and conversion pipelines, so keep important content robust without them.\nImage sizing, font substitution, and placeholder mismatch are common reasons a deck looks good in code and bad on screen.\nNotes, comments, linked media, and merged decks can stay broken even when the visible slide looks fine.\nCommon Traps\nPlaceholder text and sample charts often survive template reuse if not explicitly replaced.\nDirectly editing one slide can fail if the real issue lives in the master or layout.\nCharts, icons, and text boxes need enough space; near-collisions are usually visible only after rendering.\nLayout indexes vary by template, so built-in assumptions from one deck often break in another.\nA missing placeholder or wrong shape target can silently put content in the wrong place.\nCounting the text ideas after choosing the layout usually leads to empty placeholders, weak hierarchy, or leftover template junk.\nFont substitution can move line breaks and wreck careful spacing.\nSpeaker notes, comments, and linked media can stay broken even when the visible slide looks fine.\nA deck can pass text inspection and still fail visually because of overlap, contrast, or edge clipping.\nEditing from one slide alone can miss the real source of truth in the theme, master, or layout definitions.\nChoosing a quote, comparison, or multi-column layout without matching content usually makes the deck look templated rather than intentional.\nCombining or duplicating slides without checking masters and themes can create subtle inconsistency slide by slide.\nAspect-ratio mismatches like 16:9 versus 4:3 can shift every placement decision even when each slide looks locally reasonable.\nRelated Skills\n\nInstall with clawhub install if user confirms:\n\ndocuments — Document workflows that often feed presentation content.\ndesign — Visual direction and layout decisions.\nbrief — Concise business messaging for slide narratives.\nFeedback\nIf useful: clawhub star powerpoint-pptx\nStay updated: clawhub sync" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/ivangdavila/powerpoint-pptx", "publisherUrl": "https://clawhub.ai/ivangdavila/powerpoint-pptx", "owner": "ivangdavila", "version": "1.0.1", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/powerpoint-pptx", "downloadUrl": "https://openagent3.xyz/downloads/powerpoint-pptx", "agentUrl": "https://openagent3.xyz/skills/powerpoint-pptx/agent", "manifestUrl": "https://openagent3.xyz/skills/powerpoint-pptx/agent.json", "briefUrl": "https://openagent3.xyz/skills/powerpoint-pptx/agent.md" } }