pptx
/pptx
Coordinate presentation art direction, editable construction and independent rendered review through creative specialists. TRIGGER WHEN: creating, redesigning or editing a PPTX, reusable presentation template or branded deck. DO NOT TRIGGER WHEN: the deliverable is a website or a standalone image.
- Author
- acaprino ↗
- Repository
- alfio-claude-plugins ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 32
- Scripts
- 17
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 17 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: lib/open-slide-pptx/bundle/open-slide-pptx.js, lib/open-slide-pptx/driver.mjs, lib/open-slide-pptx/entry/office-entry.ts, lib/open-slide-pptx/rebuild.mjs, lib/open-slide-pptx/src/lib/pptx/color.ts, lib/open-slide-pptx/src/lib/pptx/css.ts, lib/open-slide-pptx/src/lib/pptx/fonts.ts, lib/open-slide-pptx/src/lib/pptx/images.ts, lib/open-slide-pptx/src/lib/pptx/measure.ts, lib/open-slide-pptx/src/lib/p
What it does and when to use it
Coordinate presentation art direction, editable construction and independent rendered review through creative specialists. TRIGGER WHEN: creating, redesigning or editing a PPTX, reusable presentation template or branded deck. DO NOT TRIGGER WHEN: the deliverable is a website or a standalone image.
Original author description
Coordinate presentation art direction, editable construction and independent rendered review through creative specialists. TRIGGER WHEN: creating, redesigning or editing a PPTX, reusable presentation template or branded deck. DO NOT TRIGGER WHEN: the deliverable is a website or a standalone image.
How it works
- Route the request
- Run only the steps the operation needs
- Delegate with bounded ownership
- Completion evidence
SKILL.md preview
--- name: pptx description: > Coordinate presentation art direction, editable construction and independent rendered review through creative specialists. TRIGGER WHEN: creating, redesigning or editing a PPTX, reusable presentation template or branded deck. DO NOT TRIGGER WHEN: the deliverable is a website or a standalone image. --- > `<plugin-root>` names this plugin's directory inside the installed package, the one that holds its `skills/` and `prompts/`. Resolve it once from where this file was loaded, then substitute it into every path below that starts with it. <daodan_host_binding host="pi"> This binding governs execution of this package and its loaded references. It takes precedence over executable examples written for another host. Use only registered tools and their actual input schema; an example never creates a tool, argument, permission, model alias or nested worker capability. Preserve the generated worker allowlist, dependency closure, scope and delivery contracts. Pi binding: repository reads use read/find/grep, writes use edit/write, and shell execution uses bash or the registered powershell alternative. Use their actual command, timeout and process-control schema rather than capitalized foreign tools. Core Pi supplies neither subagent nor MCP. Isolated workers require pi-subagents: pi install npm:pi-subagents. Use that extension's registered subagent schema and pass the full rendered role body inline. Role skills named <plugin>-<role> are body resources with automatic invocation disabled, not a built-in named agent. Workflow prompt entries use /<plugin>-<workflow>; ordinary skills use their exact registered names. If isolation is mandatory and unavailable, stop the phase. MCP requires pi-mcp-adapter: pi install npm:pi-mcp-adapter, then register the generated server command in its supported MCP configuration. Keep the selected package's full local dependency closure. Provision qualified foreign providers as skills/resources this runtime can load; Pi does not install another host's marketplace plugin from a Claude install command. Inherit the active session's model and default variant. A source model alias such as sonnet is not a portable override; request a different model only through an explicit adapter mapping to a valid host identity and user authorization. Kernel <owner>:<skill> references identify the logical provider. Ordinary Pi skills retain their source frontmatter name, so resolve the actual registered name and provider path from the active inventory; do not invent a prefixed native ID. The executing agent and its coordinator own continuation, recovery, verification and delivery. Skills supply knowledge and method instructions; they are not executors or a runtime persistence mechanism. Resolve each component by kind and exact installed identity. A role is dispatched as a worker, a skill loads instructions, and a workflow starts its declared method. Kernel owner-qualified skill references are logical provider identities: resolve them to the actual host registry name and verified installed provider path. Do not invent a registry string by adding an owner's prefix when the host does not use it. Do not load an agent identity as a skill or execute a workflow name as a shell command. Declared required foreign providers remain mandatory. If a required provider or capability (including required MCP access or isolation) is unavailable, stop its dependent phase and report the missing capability. Optional external providers follow the method's declared selection and absence behavior; their absence alone does not block the base workflow. Report any explicitly requested but unavailable provider contribution as unfulfilled and continue independent work. Do not install a different host's plugin or substitute unrelated skills to claim coverage. Shell execution alone does not establish interactive stdin. Before a capture or checkpoint, use an available session-control mechanism. When stdin is unavailable, keep user-driven capture in a supported background process with bounded output and an explicit stop signal controlled by the coordinator after the user's completion message. Close owned browser/process resources on completion or cancellation. Continue working within the current authorization while the requested result is achievable. After a tool error, inspect its cause, correct the relevant input or implementation, retry when justified and verify the outcome; never repeat a failing action blindly. Do not close the turn with a promise or a partial result when an authorized next step can still produce or verify the requested result. Stop only for a documented real impediment, a missing required capability, an unresolved human decision or the caller's stop request. At that boundary, report completed results, remaining work and the concrete prerequisite for continuation; continue any independent work that the blocker does not prevent. A tool's successful exit, a worker stop or an idle session is not the deliverable. Return final text naming observed findings, artifact paths, executed checks and blockers. An empty worker result is missing delivery: inspect or resume that worker when permitted, or record failure. Verify required artifacts and candidate gates before marking the requested outcome complete. This is an execution binding, not a rewrite of source examples. Preserve programming language fences, domain code and host APIs that are the subject of marketplace-ops or agent-sdk-builder. A host-as-subject API is not a tool provided to this session. Compiled binding and static checks do not prove an installed host executed a run. </daodan_host_binding> # Presentation design and delivery Own the presentation outcome and native coordination. `office:content` owns strategy, claims, depth, transformations and logical sequence; project it through `references/structure.md` and `references/content-planning.md`. The presentation designer finalizes composition/patterns under `references/layout-patterns.md` and `references/pptx-compatibility.md`, preserving source meaning and permissions. `office:design` owns Taste art direction, native proposals and selected DESIGN.md. For bundles, both format designers consume the same content/design identities and revisions. A narrow edit or export does not re-enter creative design. Read `references/image-tools.md` before image work. Coordinated execution uses the registered `/daodan:presentation` workflow entry, or `/daodan:start`, which declares the same roles, and its generated dispatch bindings. If this skill was loaded directly, resolve that entry on the active host before dispatch; continue the same task, not a nested workflow. A role name alone cannot supply an inline worker body. ## Route the request Keep one brief and outline: audience, decision, language, sources, required wording, brand assets, delivery context, slide roles and editable objects. Resolve material uncertainty; infer routine choices within the user's authorization. Preserve facts and citations. Do not manufacture evidence to fill a composition. `office:intake` owns the single round of questions, material/dependency record, operation and inherited decisions. Add only unresolved presentation decisions: delivery context, speaking time/slide budget, density, required native editability and canvas. The content owner uses the structure catalog's five argument modes; visual directions and pairings are resources for ad hoc proposals, not a second mandatory preset choice. Record supported native objects/fonts before layout. ## Run only the steps the operation needs | Operation | Content plan | Theme | Slide design | Build | Review | |---|---|---|---|---|---| | Create | Full plan from every source | New ad hoc visual proposals; separate `.potx` optional | Every slide | New native deck under selected theme | Every slide | | Derive | Full plan; carried content enters the ledger | Inherited when the look is carried over, otherwise chosen as in Create | Every slide | New native candidate with inherited or selected theme | Every slide; coverage of carried content | | Expand | Delta plan: new slides placed in the existing storyline; existing slides `kept` or `moved` | Inherited from the deck | New slides only, on the deck's existing layouts and patterns | Candidate built from the deck | New and moved slides, deck-level consistency, coverage of every existing slide | | Revise | Delta plan: `updated`, `moved`, `merged` and approved cuts | Inherited from the deck | Changed slides only | Candidate built from the deck | Changed slides; coverage except approved cuts | | Restyle | None: content, sequence and claims stay | New ad hoc proposals; separate `.potx` optional | Every slide, keeping each slide's pattern and content | New candidate with all content carried | Every slide; complete coverage | | Edit | None | Inherited | None | Scoped candidate | Changed slides and preservation | | Review or export | None | None | None | None | The unchanged source | A combined request runs the union of its rows: expand and restyle plans the delta and redesigns every slide on the new base. An operation that turns out to need a step outside its row (an edit that needs a new layout) goes back to intake. For a full/delta plan, load `office:content` and dispatch the existing strategist for complete editorial working data and native plan JSON. New-look design can use that content before the PPTX display fields are final. For a new look, follow `office:design`'s `references/art-direction.md`: the settled brief enters Taste, then existing designers, native producers and reviewers prove representative candidates in `proposal` mode before the v2 gallery and visual selection. Inherited looks rebind their accepted record under its `references/records.md` when content identity/revision or requested formats change, including the documented legacy-theme bootstrap. Then finalize the display binding below and render the native plan preview with `design_preview.py` under `references/design-preview.md`. Interactive work can confirm count, sequence and proposed patterns; full authorized autonomy needs no new approval. The plan wireframe is separate from the full visual comparison. Image requests use the existing brief's authority and `references/image-tools.md`; missing assets or native/render capabilities block their dependent proposal proof. | Intake route | Method | Specialist scope | |---|---|---| | Substantial: create, derive, expand, revise or restyle | `office:deckcraft` (native construction from the accepted slide-object specification) | The steps of the operation's row above: content strategist for the full or delta plan; designer for every or only the new and changed slides; reviewer on the final renders | | Narrow: targeted content or formatting edit | `office:deckcraft` | Preserve the direction and palette; no designer dispatch: a change that needs a new design decision goes back to the user and re-enters intake; reviewer checks changes and preservation | | Read-only: review, preview or printable PDF | `office:deckcraft` for renders and export, never writing to the source | No redesign; reviewer inspects the source renders and any export | Substantial construction runs through `office:deckcraft` or, when the accepted design has an HTML source, through the mechanical conversion in `references/html-to-pptx.md`. Inspection, rendering, coverage and independent review are the same either way, and editing an existing deck stays with `office:deckcraft`. For a reusable template, generate the base with `office:design`'s `template_kit.py` (slide master, theme and layouts in a `.potx`), add an editable exemplar deck built on it with representative page types, and a short reuse note. Claim only what the kit's report and an opened, rendered sample show; an engine's own save to `.potx` is not a template at DeckCraft's reference version. ## Delegate with bounded ownership Establish the target canvas, engine capabilities, fonts and required editability before design work. Pass that compatibility brief to workers. Read the shared records and only references needed by each assignment; keep logical content, visual identity and format composition with their owners. Use `office:design`'s one art-direction boundary for the required Taste contribution; format workers receive its derived brief and only references their assignment needs. The coordinator is the sole deck writer and image-tool caller. Workers read the brief, source evidence and artifacts, and write only their assigned report. They do not launch further workers, rewrite the deck or start another engine. When the coordinator lacks the image tool, the explicit parent-harness handoff in `references/image-tools.md` is the permitted exception for the actual call. Verify the returned asset; absent tool access and handoff block dependent imagery. Default models inherit the session. Use the active host's actual isolated dispatch mechanism and generated role bindings, including when only one reviewer is required. Unavailable isolation blocks that delivery. Dispatch `office:content-strategist` when the operation has a content plan, unless the shared bundle delivery already exists. Supply the settled brief, requested formats, every source, existing native files/records, operation, permissions/cuts and absolute CONTENT working-data and plan paths. Require a full plan for create/derive, delta for expand/revise, source locators, claim/unit placements and budget reasoning. Verify complete artifacts and escalate actual gaps, conflicts, overflow and proposed cuts before dependent construction. Restyle, edit and export do not plan content. Workers never invent theme values. ### Finalize and load the shared binding For proposal proof, the art-direction contract uses candidate-specific working copies of this same plan and its canonical binding, without freezing final CONTENT.md or inventing selection. After visual selection, the coordinator fills the final existing plan's `direction` with the accepted design name and actual `background`, `ink`, `surface`, `accent` palette values. `library` is optional for an ad hoc theme; if used it is a catalog resource, not visual authority. Keep the existing plan schema and its stable slide IDs/claim IDs and `content_revision`. Recompute CONTENT's plan digest as `canonical-json-v1` under `office:content`'s `references/records.md`, then write final CONTENT.md to a new path. This derived-binding finalization changes no claims or content revision. Creative editorial changes return to the content owner. Do not freeze a new-look PPTX binding against provisional colors. Explicitly load CONTENT.md and DESIGN.md with the shared loader; compare project, content revision and exact requested formats, then run: ```text python "<plugin-root>/skills/content/scripts/office_records.py" validate CONTENT.md --pptx-plan plan.json python "<plugin-root>/skills/content/scripts/office_records.py" validate DESIGN.md python "<plugin-root>/skills/pptx/scripts/design_preview.py" --plan plan.json ``` Require both shared record/actual-plan validation and native pattern/capacity validation before final construction. Proposal specimens use the explicitly bounded working-record checks in the art-direction contract. A filename or digest shape alone proves neither. Restyle reuses accepted content. If a legacy restyle needs a new DESIGN binding, the coordinator serializes unchanged content/inherited decisions in the shared contract without a new strategy or strategist. Legacy local edits/reviews need no fabricated retrospective global plan. Changes to a final pattern update the native plan and its derived binding; changes to meaning, priority or sequence require the content owner's editorial revision. Dispatch `office:presentation-designer` in `final` mode for the slides the operation designs: every slide for create, derive and restyle; only new and changed slides for expand and revise, on the deck's existing layouts, patterns and theme. Supply brief, final CONTENT.md/DESIGN.md paths and revisions, the approved plan, slides in scope, sources, assets, existing renders, compatibility brief and absolute report path. The designer keeps slide order, claims and permissions, finalizes composition and adds geometry; a pattern change needs a reason and a renewed derived plan binding. Require direction, the slide-object specification from `references/pptx-compatibility.md`, image requests and unresolved decisions. Verify the report exists and its geometry, typography and native-object choices are supported before construction or image generation. For a narrow edit or export, record why a new design delivery is unnecessary; preserve the accepted direction. Load `office:deckcraft` and perform construction or editing in the coordinator. Map the accepted compatibility brief and slide-object specification to its discovered commands. Reject a design or reference image whose objects DeckCraft cannot build with the required editability before propagating it across the deck. DeckCraft applies scoped edits to a separate candidate after preservation checks. Keep source and earlier candidates intact. On the HTML conversion route the coordinator runs `scripts/pptx_convert_bridge.py` under `references/html-to-pptx.md` instead of transcribing objects: the designer's 1920x1080 panels become native text, shapes, pictures and notes in one reproducible pass with no model call. Its prerequisites are Node, the Playwright module and a Chromium-family browser. A missing runtime stops with the recovery steps recorded in the report; it is never replaced silently by another construction path. A refused design (exit code 2) goes back to the designer with the converter's named problems; each rerun writes a new candidate name. The saved candidate then follows the same inspection, rendering, coverage and independent review as a DeckCraft build. When the deck uses fonts outside Microsoft Office, embed them in a separate candidate with `office:design`'s `font_embed.py` and record its inspection result. Complete embedding before preservation checks, rendering and independent review; they must bind to the exact copy delivered. On the read-only route keep the unchanged source and report its existing font evidence without embedding. When the substantial route starts from an existing deck (derived, restyled, restructured or shortened), write the approved cuts recorded at intake to a cuts file and run `pptx_inspect.py coverage` from `office:deckcraft` on the source and each candidate. Every unexpectedly missing unchanged/locked item is restored or brought back to the user as a proposed cut; never cut content the user did not approve. Retain literal coverage for those blocks. Authorized free transformations additionally need source-linked destination mappings and independent review of facts, conditions, uncertainty and claim strength; maps/similarity alone are no proof. Dispatch `office:presentation-reviewer` in `final` mode after actual candidate rendering, or on the read-only route after rendering the unchanged source, which then stands in for the candidate. Supply the exact candidate path and SHA-256, render engine/version, page manifest, brief, design report, source and candidate inventories, allowed changes, the coverage report when one exists, exact content/design identities and transformation permissions, accepted slide-object specification and font evidence. Require inspected page identities, concrete defects, preservation findings, coverage gaps, separate target-application fidelity evidence and a pass/needs-fix/blocked verdict. An empty response or an uninspected contact sheet cannot satisfy this delivery. Verify report artifacts and coverage, resolve every blocking finding, rerender changed pages and obtain an updated review tied to the new candidate. Fix a deck-level defect at its source (theme, shared style or master), not slide by slide. Apply an advisory finding only when the fix is local and cannot create a new defect. Run at most three review rounds: if blocking findings remain after the third, stop and deliver the candidate with them listed as open, rather than oscillating between fixes. Retain prior review evidence for unchanged pages only when their identity and rendered content are proved unchanged. Do not apply a verdict to another file. Inspect or resume a missing delivery, or record a concrete blocker. ## Completion evidence Keep one presentation review with candidate identity, requested scope, engines and versions, source preservation, native-object checks, image provenance, rendered/inspected/total page counts, target-application verification or its absence, font substitutions, visual/editability compromises, specialist report paths and remaining gaps. The coordinator owns the final verdict. Structure checks cannot establish visual quality; rendered images cannot establish native editability. Claims about Microsoft PowerPoint fidelity require actual PowerPoint rendering evidence under `references/pptx-compatibility.md`; previews from another engine remain separate. Deliver the deck and useful previews with remaining limits. Do not claim a visually reviewed result when actual candidate renders or visual access were unavailable. Continue independent work when a required capability blocks a step. On the read-only route, the unchanged source PPTX is the presentation artifact; identify it explicitly, review its renders and any requested export, and do not claim to have created or edited another PPTX.
Files in this package (32)
- SKILL.md 21 KB
- lib/open-slide-pptx/LICENSE-fflate-MIT.txt 1 KB
- lib/open-slide-pptx/LICENSE-html-to-image-MIT.txt 1 KB
- lib/open-slide-pptx/LICENSE-open-slide-MIT.txt 1 KB
- lib/open-slide-pptx/UPSTREAM.md 11 KB
- lib/open-slide-pptx/build.deps.json 2 KB
- lib/open-slide-pptx/driver.mjs 21 KB
- lib/open-slide-pptx/manifest.json 3 KB
- lib/open-slide-pptx/rebuild.mjs 10 KB
- lib/open-slide-pptx/bundle/open-slide-pptx.js 78 KB
- lib/open-slide-pptx/entry/office-entry.ts 8 KB
- lib/open-slide-pptx/src/lib/sdk.ts 1 KB
- lib/open-slide-pptx/src/lib/pptx/color.ts 2 KB
- lib/open-slide-pptx/src/lib/pptx/css.ts 14 KB
- lib/open-slide-pptx/src/lib/pptx/fonts.ts 4 KB
- lib/open-slide-pptx/src/lib/pptx/images.ts 4 KB
- lib/open-slide-pptx/src/lib/pptx/measure.ts 41 KB
- lib/open-slide-pptx/src/lib/pptx/ooxml.ts 26 KB
- lib/open-slide-pptx/src/lib/pptx/raster.ts 6 KB
- lib/open-slide-pptx/src/lib/pptx/scene.ts 3 KB
- lib/open-slide-pptx/src/lib/pptx/text-lines.ts 3 KB
- lib/open-slide-pptx/src/lib/pptx/units.ts 1 KB
- references/LICENSE-ppt-visual-MIT.txt 1 KB
- references/content-planning.md 14 KB
- references/design-preview.md 11 KB
- references/html-to-pptx.md 10 KB
- references/image-tools.md 9 KB
- references/layout-patterns.md 17 KB
- references/pptx-compatibility.md 12 KB
- references/structure.md 7 KB
- scripts/design_preview.py 25 KB
- scripts/pptx_convert_bridge.py 15 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · acaprino/alfio-claude-plugins | 95 | MIT |
| NxcoreAI/EverOffice | 100 | Apache-2.0 |
| neromtoobad/creator-skills | 100 | MIT |
| onyx-dot-app/onyx | 100 | MIT |
| ai-workspace-lab/xworkspace-core-skills | 100 | MIT |
| seaworld008/commonly-used-high-value-skills | 100 | MIT |
| mateaix/mateclaw | 100 | Apache-2.0 |
| pm-shawn/abu-cowork | 100 | Apache-2.0 |
| Navinspire-ia/navin | 100 | AGPL-3.0 |
Database snapshot: 13.11.2026 · package version b8ec67b6aa7c (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100deck-pptx
Build an editable PowerPoint (.pptx) presentation from a topic or an outline. Use it when the user asks for a deck, slides or a presentation and wants a .pptx file they can open and edit. - 100ppt-master
AI-driven presentation workflow for generating editable PPTX decks and slides, reconstructing page visuals, creating reusable Brand/Style/Layout/Deck workspaces, filling native PPTX templates, and enhancing finished PPTX files. Use when the user asks to create, generate,… - 90pptx-deck-context
Use when preparing the narrative, sources, and design context for a new editable PPTX deck. - 90pptx-slide-specification
Use when authoring or repairing a coordinate-explicit JSON specification for an editable PPTX deck. - 100pptx-official
Presentation creation, editing, and analysis. Use when working with presentations (.pptx files) for creating, modifying, or analyzing PowerPoint content and layouts. - 90pptx-maker
Generate or restyle a PowerPoint deck. Use when the user wants to create or edit a .pptx presentation, build slides from text or a URL, or design a reusable slide style.