{"id":"189f2b22-6955-4310-8a27-e68329dfc51c","entityType":"agent","slug":"clawhub-callmexhj-image-ppt-maker","name":"PPT 图片生成","canonicalUrl":"https://www.xpersona.co/agent/clawhub-callmexhj-image-ppt-maker","canonicalPath":"/agent/clawhub-callmexhj-image-ppt-maker","generatedAt":"2026-10-10T21:43:44.060Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T19:10:19.237Z","emptyReason":null},"description":"Turns presentation ideas into McKinsey-style outlines, consistent 16:9 slide images, a playable HTML deck, and duration-aware speaker scripts. Supports staged content review, visual style guidance, optional logo space, batch generation, and structured single-slide revisions.","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.3K downloads reported by the source. Last updated 10/10/2026.","installCommand":"clawhub skill install s172f1v6gafam18018mzzfn9198a136e:image-ppt-maker","sourceUrl":"https://clawhub.ai/callmexhj/image-ppt-maker","homepage":"https://clawhub.ai/callmexhj/skills/image-ppt-maker","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/callmexhj/image-ppt-maker","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/callmexhj/skills/image-ppt-maker","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":62,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"PPT 图片生成 technical dossier on Xpersona with agent coverage, OPENCLEW support, and live trust metadata."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-10T19:10:19.237Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T19:10:19.237Z","emptyReason":null},"stars":null,"forks":null,"downloads":1284,"packageName":null,"latestVersion":"0.1.3","tractionLabel":"1.3K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T19:10:19.237Z","emptyReason":null},"lastUpdatedAt":"2026-10-10T19:10:19.237Z","lastCrawledAt":"2026-10-10T19:10:19.237Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-11T19:10:19.237Z","lastVerifiedAt":null,"highlights":[{"version":"0.1.3","createdAt":"2026-07-15T09:58:06.377Z","changelog":"- Removes the redundant skill-card.md file for simplification. - Clarifies workflow: image prompts are now internal and not a user review gate. - Adds explicit rule to never ask users to review/approve image prompts; prompt creation is automatic after content/style approval. - Introduces a dedicated single-page revision loop: reconfirm revised content before regenerating an image; never regenerate from raw feedback. - Updates change-handling: always require explicit content approval on single-page revisions and maintain existing style unless the user requests a change. - Tightens language to align the review points and workflow gates with internal-only prompt handling.","fileCount":8,"zipByteSize":17839},{"version":"0.1.2","createdAt":"2026-07-10T06:00:14.368Z","changelog":"**Stronger image approval and revision workflow before HTML and speaker notes:** - Added an explicit image review gate: users must review and approve all generated images before HTML assembly or speaker note writing. - Users can request revisions to specific images; only approved images are included in the HTML slideshow and speaker notes. - HTML slideshow and speaker notes are now generated only after all images are explicitly approved by the user. - Clarified that the workflow always presents images for feedback and requires approval at the image gate. - Improved instructions on duration-aware, directly readable oral speaker notes after image approval. - Other documentation and workflow clarifications for clearer gating and revision logic.","fileCount":8,"zipByteSize":16419},{"version":"0.1.1","createdAt":"2026-07-10T05:02:50.629Z","changelog":"**Improved reliability for multi-image generation workflows.** - Adds OpenAI agent configuration file. - Removes obsolete skill-card documentation. - Updates image generation process to handle long-running operations: waits for completion, inspects output directories, and prevents duplicate generations. - Refines recommendations for visual styles, including concrete illustration directions. - Clarifies review gates and workflow for handling tool failures and progress reporting.","fileCount":8,"zipByteSize":15833},{"version":"0.1.0","createdAt":"2026-07-09T10:07:21.055Z","changelog":"image-ppt-maker v0.1.0 - Initial release of image-ppt-maker skill. - Provides a structured, human-in-the-loop workflow for generating McKinsey-style PPT slide images using image-2. - Includes multi-step review gates for requirements parsing, outline review, content expansion, visual style selection, prompt approval, and final speaker notes. - Supports automatic assembly of 16:9 slide images into a playable HTML slideshow. - Produces unified-style image prompts, batch-generates slides, and writes oral speaker notes. - Does not create or assemble PPTX files; workflow stops at HTML slideshow and related deliverables.","fileCount":7,"zipByteSize":14109}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s172f1v6gafam18018mzzfn9198a136e:image-ppt-maker","setupComplexity":"low","setupSteps":["Install using `clawhub skill install s172f1v6gafam18018mzzfn9198a136e:image-ppt-maker` in an isolated environment before connecting it to live workloads.","No published capability contract is available yet, so validate auth and request/response behavior manually.","Review the upstream CLAWHUB listing at https://clawhub.ai/callmexhj/image-ppt-maker before using production credentials."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-callmexhj-image-ppt-maker/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-callmexhj-image-ppt-maker/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-callmexhj-image-ppt-maker/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-callmexhj-image-ppt-maker/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-callmexhj-image-ppt-maker/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-callmexhj-image-ppt-maker/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T21:43:44.057Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-callmexhj-image-ppt-maker/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-callmexhj-image-ppt-maker/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-callmexhj-image-ppt-maker/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-callmexhj-image-ppt-maker/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T19:10:19.237Z","emptyReason":null},"readme":"Skill: PPT 图片生成\n\nOwner: callmexhj\n\nSummary: Turns presentation ideas into McKinsey-style outlines, consistent 16:9 slide images, a playable HTML deck, and duration-aware speaker scripts. Supports staged content review, visual style guidance, optional logo space, batch generation, and structured single-slide revisions.\n\nTags: latest:0.1.3\n\nVersion history:\n\nv0.1.3 | 2026-07-15T09:58:06.377Z | user\n\n- Removes the redundant skill-card.md file for simplification.\n- Clarifies workflow: image prompts are now internal and not a user review gate.\n- Adds explicit rule to never ask users to review/approve image prompts; prompt creation is automatic after content/style approval.\n- Introduces a dedicated single-page revision loop: reconfirm revised content before regenerating an image; never regenerate from raw feedback.\n- Updates change-handling: always require explicit content approval on single-page revisions and maintain existing style unless the user requests a change.\n- Tightens language to align the review points and workflow gates with internal-only prompt handling.\n\nv0.1.2 | 2026-07-10T06:00:14.368Z | user\n\n**Stronger image approval and revision workflow before HTML and speaker notes:**\n\n- Added an explicit image review gate: users must review and approve all generated images before HTML assembly or speaker note writing.\n- Users can request revisions to specific images; only approved images are included in the HTML slideshow and speaker notes.\n- HTML slideshow and speaker notes are now generated only after all images are explicitly approved by the user.\n- Clarified that the workflow always presents images for feedback and requires approval at the image gate.\n- Improved instructions on duration-aware, directly readable oral speaker notes after image approval.\n- Other documentation and workflow clarifications for clearer gating and revision logic.\n\nv0.1.1 | 2026-07-10T05:02:50.629Z | user\n\n**Improved reliability for multi-image generation workflows.**\n\n- Adds OpenAI agent configuration file.\n- Removes obsolete skill-card documentation.\n- Updates image generation process to handle long-running operations: waits for completion, inspects output directories, and prevents duplicate generations.\n- Refines recommendations for visual styles, including concrete illustration directions.\n- Clarifies review gates and workflow for handling tool failures and progress reporting.\n\nv0.1.0 | 2026-07-09T10:07:21.055Z | auto\n\nimage-ppt-maker v0.1.0\n\n- Initial release of image-ppt-maker skill.\n- Provides a structured, human-in-the-loop workflow for generating McKinsey-style PPT slide images using image-2.\n- Includes multi-step review gates for requirements parsing, outline review, content expansion, visual style selection, prompt approval, and final speaker notes.\n- Supports automatic assembly of 16:9 slide images into a playable HTML slideshow.\n- Produces unified-style image prompts, batch-generates slides, and writes oral speaker notes.\n- Does not create or assemble PPTX files; workflow stops at HTML slideshow and related deliverables.\n\nArchive index:\n\nArchive v0.1.3: 8 files, 17839 bytes\n\nFiles: agents/openai.yaml (432b), references/image-2-prompts.md (5655b), references/mckinsey-outline.md (3318b), references/workflow.md (11989b), scripts/generate-html-player.mjs (8338b), skill-card.md (2205b), SKILL.md (7811b), _meta.json (134b)\n\nFile v0.1.3:SKILL.md\n\n---\nname: image-ppt-maker\ndescription: \"Create PPT-style images through a human-in-the-loop workflow: clarify presentation requirements including optional top-corner LOGO space, research and draft McKinsey-style master and page-by-page outlines, expand page content, confirm the desired visual style before image prompts, write unified-style image-2 prompts, batch-generate 16:9 slide images, automatically assemble the images into a playable 16:9 HTML slideshow, and finally write oral speaker notes based on the outline and final images. Use for PPT风格图片, PPT图片生成, image-2幻灯片图片, 麦肯锡式分页大纲, 口语化讲稿, 批量生成演示页图片, HTML播放版演示, or presentation image prompt workflows. This skill does not assemble PPTX files.\"\n---\n\n# Image PPT Maker\n\nHelp users create a set of PPT-style slide images with image-2. Use a strict review-gated workflow:\n\n1. Confirm requirements.\n2. Build a McKinsey-style master outline and page-by-page outline.\n3. Expand the outline content.\n4. Confirm the desired visual style for the images.\n5. Write unified-style image-2 prompts.\n6. Batch-generate 16:9 PPT images.\n7. Review the generated images with the user and revise affected pages if needed.\n8. Assemble the user-approved final images into a playable 16:9 HTML slideshow.\n9. Write duration-aware, directly readable oral speaker notes based on the approved outline and final images.\n\nAsk the user whether they want changes only at the review gates listed below. Image prompts are internal execution artifacts, not a review gate. Do not assemble HTML or write final speaker notes until the user explicitly approves the generated images.\n\n## Required References\n\n- Read [workflow.md](references/workflow.md) before starting any task.\n- Read [mckinsey-outline.md](references/mckinsey-outline.md) before drafting or revising outlines.\n- Read [image-2-prompts.md](references/image-2-prompts.md) before writing prompts or generating images.\n- Use [generate-html-player.mjs](scripts/generate-html-player.mjs) only after the user approves final local images for a playable HTML output.\n\n## Core Rules\n\n1. Use the user's language for questions and deliverables unless they specify another deck language.\n2. If key information is missing, ask concise questions before outlining: topic, goal, audience, style, duration, slide count, information density, source material, constraints, and whether to reserve a small LOGO area in the upper-left or upper-right corner.\n3. Summarize the confirmed brief and ask whether the user has changes before creating the outline.\n4. Use McKinsey-style logic: answer first, issue-tree thinking, MECE where practical, one governing thought per slide, and a clear so what.\n5. Every page in the outline must include logic notes. Do not create title-only or decorative pages.\n6. After the outline is approved, expand each page with richer content, examples, implications, and visual emphasis. Do not output speaker notes yet.\n7. Before writing image prompts, ask the user what visual style they prefer and recommend context-aware options such as training style with friendly editorial illustrations, executive report style with restrained illustration accents, illustration-led storytelling with recurring characters and scenes, graphic/chart-heavy, product demo style, or other suitable options.\n8. Generate one image per slide, 16:9, with image-2. Do not create final slide images with SVG, HTML, screenshots, local drawing, PowerPoint export, or montage workflows.\n9. Treat image generation as a long-running operation. Do not interpret a quiet period, a partial preview, or a tool call with no immediate new image as failure. Keep the generation task alive, wait for its final completion signal, inspect the output directory for newly completed files, and report progress without triggering a duplicate generation. Retry only after an explicit tool failure, confirmed timeout, or confirmed missing/corrupt output after completion.\n10. After image generation, present the final image paths or previews and ask the user whether any page needs adjustment. Do not assemble HTML or write final speaker notes until the user explicitly approves the images.\n11. After the user approves the images, automatically generate a playable 16:9 HTML slideshow from the final local images.\n12. After HTML assembly, write final per-slide speaker notes based on the approved outline and final images. Allocate page-level speaking time to match the confirmed duration, and write a complete, directly readable oral script for each page.\n13. This skill does not assemble PPTX files. Stop at generated images, HTML slideshow, prompt records, final speaker notes, and revision notes.\n14. Preserve approved work during revisions. Only regenerate the affected downstream artifacts.\n15. Do not ask the user to review or approve image prompts. After the page content and visual style are approved, write the prompts and proceed directly to image generation.\n16. For every later single-page change, re-run the complete single-page content flow while reusing the approved deck-wide style. Confirm the revised page content before generating that page's image; never regenerate directly from raw feedback.\n\n## Workflow Gates\n\nDo not skip these review points:\n\n- After requirement parsing: ask whether the brief and assumptions need changes.\n- After the master outline and page-by-page outline: ask whether the storyline, page count, or logic needs changes.\n- After the expanded outline content: ask whether the content depth, examples, or emphasis needs changes.\n- Before writing image-2 prompts: ask which visual style the user prefers, offering context-aware recommendations that include concrete illustration directions when illustration is suitable.\n- After image generation: present the completed images and ask whether any page needs changes; wait for explicit approval before HTML assembly and final speaker notes.\n- After HTML assembly and final speaker notes: ask whether any HTML output or speaker note should be adjusted.\n\nNever create a prompt-review gate. Prompt creation proceeds automatically after the preceding content and style approvals.\n\nIf the user requests changes:\n\n- Requirement changes invalidate outline, prompts, and images.\n- Outline changes invalidate affected expanded content, prompts, images, HTML, and final speaker notes.\n- Visual-style changes invalidate prompts, images, HTML, and final speaker notes.\n- Final speaker-note changes do not invalidate prompts, images, or HTML unless the visible slide content or logic changes.\n- Style changes invalidate prompts, images, HTML, and final speaker notes according to the affected scope.\n- Any single-page content or image change must enter the single-page revision loop in [workflow.md](references/workflow.md): clarify the page request, rebuild the page logic and expanded content, obtain explicit content approval, rebuild the prompt internally without asking for prompt approval, generate only that page, and review the new image.\n- Never regenerate a page immediately from user feedback, even when the requested change seems small. Reconfirm the revised page content first. Reuse the existing style lock and do not repeat visual-style confirmation unless the user explicitly asks to change the deck style.\n- HTML output must be regenerated if final image filenames, image count, title, or image folder changes.\n\n## Deliverables\n\nWhen complete, provide:\n\n- confirmed brief;\n- master outline and page-by-page outline;\n- expanded outline content;\n- image-2 prompt set with the shared style lock;\n- generated image paths or previews;\n- playable 16:9 HTML slideshow path;\n- final oral speaker notes based on the outline and generated images;\n- concise notes on pages that may need regeneration.\n\nFile v0.1.3:_meta.json\n\n{\n  \"ownerId\": \"kn7dddd3v8yk96jx32p2gsmnvh8a03gt\",\n  \"slug\": \"image-ppt-maker\",\n  \"version\": \"0.1.3\",\n  \"publishedAt\": 1784109486377\n}\n\nFile v0.1.3:references/image-2-prompts.md\n\n# Image-2 Prompt Rules\n\nWrite prompts for image-2. Each prompt must generate exactly one 16:9 PPT-style slide image.\n\nTreat prompts as internal execution artifacts. Do not ask the user to review or approve prompts. Generate them after content and style approval, then proceed directly to image generation.\n\n## Deck-wide style lock\n\nDefine one shared style lock before per-page prompts. It must specify:\n\n- aspect ratio: 16:9;\n- deck type: professional consulting-style PPT page;\n- layout system: title area, content grid, margins, chart/table/card treatment;\n- palette: primary, secondary, background, accent colors;\n- typography: clear hierarchy, readable slide text, no decorative fonts;\n- visual language: charts, diagrams, icons, photography, or abstract business visuals;\n- density: high, medium, or low;\n- optional LOGO space: no reserved area, upper-left reserved area, or upper-right reserved area;\n- consistency rule: every page must look like part of the same deck.\n\nRepeat the complete style lock inside every page prompt, but mark it as non-visible generation guidance. The style lock must influence layout and visual treatment only; image-2 must not render the style-lock wording as text on the slide.\n\n## Per-page prompt structure\n\nEach page prompt must include:\n\n1. `Model`: image-2.\n2. `Task`: generate only this single 16:9 PPT slide image.\n3. `Style lock`: copy the shared deck-wide style lock.\n4. `Style text handling`: state that style descriptions are instructions only and must not appear as visible text.\n5. `Slide logic`: key question, governing thought, supporting logic, so what, transition.\n6. `Expanded content`: the richer explanation or examples that should guide the visual emphasis.\n7. `LOGO space`: if requested, reserve a small clear area in the chosen top corner; do not invent or render a logo unless the user provided one.\n8. `Page message and content`: explain the thought this page should express, the core content to show, and the recommended title, key messages, labels, and emphasis.\n9. `Composition`: layout, visual hierarchy, chart or diagram structure, spacing, alignment.\n10. `Readability`: clean typography, enough contrast, no tiny unreadable text.\n11. `Constraints`: factual constraints and source-material limits.\n12. `Negative constraints`: forbidden outputs.\n\n## Page message and content\n\nDo not constrain the slide by enumerating every allowed visible word. Instead, describe the page's intended communication clearly enough for image-2 to design the slide:\n\n- State the page's governing thought in an answer-first way.\n- Explain the core content the slide should communicate, including the most important evidence, comparison, process, framework, or recommendation.\n- Suggest the title, short labels, callouts, and chart/table labels that would help express the idea, but keep text concise and slide-like.\n- Preserve McKinsey-style communication: structured, logical, executive-readable, and focused on one message per page.\n- Do not render prompt section labels or internal reasoning labels such as \"Style lock\", \"Slide logic\", \"Expanded content\", \"Page message and content\", \"McKinsey-style\", \"16:9\", \"professional consulting-style\", or \"image-2\".\n- If a style concept needs to show visually, express it through layout, color, spacing, chart treatment, and imagery, not through written words.\n- If a LOGO area is reserved, it is a blank layout area unless the user supplies a logo. Do not render placeholder text such as \"LOGO\".\n- Slide sequence numbers are file-management metadata only. Do not render page numbers, slide numbers, sequence labels, numeric badges, or file names anywhere in the image unless a number is explicitly part of the approved page content.\n- For illustration-led styles, express the approved visual direction through recurring characters, coherent scenes, consistent linework or rendering, and visual metaphors; do not write the style name or illustration instructions on the slide.\n\nAdd this sentence to every prompt:\n\n```text\nRender concise slide text that supports the page message; all style descriptions, prompt section labels, and generation instructions are non-visible guidance and must not appear as words in the slide image.\n```\n\n## Negative constraints\n\nAlways forbid:\n\n- multiple slides in one image;\n- montage, contact sheet, overview, collage, or thumbnail grid;\n- browser screenshot, app screenshot, chat screenshot, or document screenshot;\n- long paragraphs, dense report prose, or text that does not support the page's governing thought;\n- any visible wording copied from style descriptions, prompt section labels, or generation instructions;\n- page numbers, slide numbers, sequence labels, numeric badges, or file names added only to identify the image;\n- meta words such as style lock, deck-wide style, 16:9, image-2, prompt, McKinsey-style, typography, palette, layout system, consulting-style, Page message and content, or LOGO;\n- watermark, signature, logo, model mark, or random brand mark;\n- random icons, people, company names, or data not provided or approved;\n- SVG, HTML, wireframe, or code-like rendering.\n\n## Batch output\n\nGenerate one image per approved prompt. Use ordered names when saving files:\n\n```text\nimages/slide-01.png\nimages/slide-02.png\nimages/slide-03.png\n```\n\nIf a page fails visually, revise or regenerate that page only unless the style lock itself changed.\n\nFor any later single-page change, wait until the revised page logic, expanded content, and visual emphasis are explicitly approved. Then rebuild that page's prompt with the existing deck-wide style lock and generate only that page without adding a prompt-review step.\n\nFile v0.1.3:references/mckinsey-outline.md\n\n# McKinsey-Style Outline\n\nUse this structure for the master outline and every page outline.\n\n## Principles\n\n- Answer first: lead with the conclusion or recommendation.\n- Pyramid structure: conclusion, reasons, evidence.\n- Issue tree: split the topic into a small number of logical questions.\n- MECE where practical: reduce overlap and gaps.\n- One slide, one message: each page has one governing thought.\n- So what: every page explains why the point matters to the audience.\n\n## Master outline format\n\nInclude:\n\n- `coreAnswer`: the answer-first conclusion of the whole deck;\n- `audienceDecision`: what the audience should decide or do;\n- `logicChain`: 3-5 major reasoning steps;\n- `sections`: major sections with the question each section answers;\n- `storyFlow`: why the sequence is persuasive.\n\n## Page-by-page outline format\n\nFor each page, include:\n\n- `pageNumber`;\n- `title`: conclusion-style title, not a topic label;\n- `keyQuestion`: the question this page answers;\n- `governingThought`: the page's answer-first message;\n- `supportingLogic`: 2-4 reasons, evidence points, or observations;\n- `visualIdea`: the visual structure that best supports the logic;\n- `soWhat`: why the audience should care;\n- `transition`: why the next page follows.\n\n## Visual logic mapping\n\n- Compare options: side-by-side comparison.\n- Explain drivers: driver tree, layered model, or waterfall.\n- Show sequence: timeline, roadmap, or process.\n- Prioritize: matrix, ranking, or funnel.\n- Recommend action: chosen path plus reasons.\n- Summarize system: architecture, operating model, or flywheel.\n\nDo not use decorative visuals that fail to carry the logic.\n\n## Expanded outline content\n\nAfter the page-by-page outline is approved, expand each page before writing image prompts.\n\nFor each page, include:\n\n- `expandedContent`: 1-3 short paragraphs that deepen the page logic with evidence, implications, and examples;\n- `exampleIdeas`: 2-4 concrete examples, analogies, or mini-scenarios that make the point easier to understand;\n- `visualEmphasis`: what the generated image should make most obvious;\n- `speakerNoteHints`: brief reminders for final speaker-note writing after images are generated.\n\nDo not write the final speaker notes at this stage. Final notes must be written after images are generated, using the approved outline and the final visual output.\n\n## Single-page revisions\n\nFor every later single-page change, recreate the affected page using the same page-by-page outline and expanded-content fields above. Preserve the approved deck-wide storyline and style, but reconsider the page's governing thought, support, so what, transition, examples, visual emphasis, and speaking-time allocation in light of the new request.\n\nPresent the consolidated revised page content for user approval before generating the replacement image. Do not treat raw image feedback as sufficient approval to regenerate.\n\n## Final speaker notes\n\nAfter the final images and HTML player are generated, write page-by-page speaker notes.\n\nSpeaker notes must:\n\n- sound like a real presenter, not a written report;\n- use clear, warm, direct language;\n- explain the point with concrete examples when useful;\n- refer naturally to what the audience can see on the generated page;\n- avoid over-polished slogans, dense jargon, and reading every slide label.\n\nFile v0.1.3:references/workflow.md\n\n# Workflow\n\nFollow this workflow exactly. Pause only at the designated review gates. Image-prompt creation is not a review gate.\n\n## 1. Confirm requirements\n\nParse the user's request and collect missing key details:\n\n- topic and background;\n- presentation goal: what the audience should understand, believe, decide, or do;\n- audience: executives, customers, internal team, review panel, investors, or another group;\n- duration and approximate slide count; use the duration as the total speaking-time budget for the final script;\n- information density: high, medium, or low;\n- preferred visual style or reference material;\n- source material, facts, data, cases, and constraints;\n- output language and tone;\n- whether to reserve a small LOGO area in the upper-left or upper-right corner, or no LOGO area;\n- any content that must not be invented.\n\nIf the user is unsure, recommend practical defaults:\n\n- duration: 10 minutes;\n- slide count: 8-12 pages;\n- information density: medium;\n- style: clean McKinsey-style consulting deck with restrained color, strong hierarchy, and chart-like logic.\n- LOGO area: no reserved LOGO area unless the user asks; if they want it, recommend a small upper-right area for corporate decks and upper-left for brand-led decks.\n\nThen summarize the brief, including the LOGO-space decision, and ask: \"以上需求和假设是否需要修改？确认后我会生成总纲和分页大纲。\"\n\n## 2. Research and outline\n\nUse the user's source material first. If internet research is requested or required for current facts, browse and cite sources in the final summary.\n\nCreate:\n\n- master outline: core answer, main logic chain, issue tree, and section flow;\n- page-by-page outline: one page per slide, with complete logic notes and a suggested speaking-time allocation. Allocate the total speaking time across pages according to message importance and complexity; keep the sum aligned with the confirmed duration.\n\nAsk: \"这个总纲和分页大纲是否需要调整？确认后我会拓展每页内容。\"\n\n## 3. Expand outline content\n\nAfter the user approves the master outline and page-by-page outline, expand the content before prompt writing.\n\nFor each slide, produce:\n\n- expanded content: richer explanation of the page's message, evidence, implications, and examples;\n- example ideas: practical examples, analogies, or mini-scenarios that make the point concrete;\n- visual emphasis: what the generated image should make most obvious;\n- speaking hints: brief notes that may help final speaker-note writing later, but do not output the final talk track yet.\n\nDo not output the final speaker notes in this stage. Final notes must be written after image generation and HTML assembly, using the approved outline and the final generated images.\n\nAsk: \"拓展后的内容、例子和视觉重点是否需要调整？确认后我会先和你确认图片风格，再生成每页的 image-2 提示词。\"\n\n## 4. Confirm visual style\n\nBefore writing image-2 prompts, ask the user what visual style they want. Recommend options based on the context instead of using a fixed list.\n\nCommon options include:\n\n- 培训风：更亲和，结构清楚，适合课程、工作坊、内部分享；\n- 汇报风：更克制、专业、结论先行，适合管理层汇报和项目汇报；\n- 培训插画风：在清晰的咨询式结构中加入友好人物、课堂/工作场景、轻量叙事插画和统一笔触，适合课程、工作坊、内部分享；\n- 插画叙事风：用连续出现的角色、场景和视觉隐喻讲清问题变化，搭配少量结构化图形，适合传播、培训、文化和用户故事类主题；\n- 汇报插画风：保持结论先行和克制留白，用少量高质量场景插画解释复杂概念，适合管理层汇报中需要提升亲和力的主题；\n- 多图形：更多框架图、流程图、矩阵、图表，适合战略、经营、方案类主题；\n- 科技感：更适合 AI、数字化、产品技术主题；\n- 品牌简洁风：留白更多，适合客户沟通、品牌展示、对外路演。\n\nRecommend 2-4 options that fit the user's topic, audience, duration, and information density, then ask: \"你更倾向哪种图片风格？确认后我会把这个风格锁定到整套 image-2 提示词中。\"\n\n## 5. Write image-2 prompts\n\nBefore writing per-page prompts, define one deck-wide style lock. Apply it to every prompt.\n\nFor each slide, write one self-contained image-2 prompt that includes:\n\n- shared style lock;\n- single-slide 16:9 instruction;\n- LOGO-space instruction if the user requested one;\n- page logic;\n- expanded content and speaker-note intent where useful;\n- the thought and content this page should express, including recommended title, key messages, labels, and emphasis;\n- composition and visual structure;\n- negative constraints.\n\nDo not show the prompt set for approval and do not ask whether the prompts need changes. Once the approved page content and style lock are available, proceed directly to batch image generation.\n\n## 6. Batch-generate images\n\nGenerate exactly one 16:9 image per slide with image-2.\n\nGeneration may take many minutes. When generating several pages in parallel or in a batch:\n\n- announce that the operation is long-running and that no immediate new preview does not mean generation failed;\n- keep the original generation task running and wait for its final return/completion signal;\n- monitor completed files or returned images without launching a second batch;\n- preserve already completed pages and report the current count when progress is available;\n- retry only after explicit failure, confirmed timeout, or confirmed missing/corrupt output after the task has ended.\n\nNever claim that a batch failed merely because it has been quiet for a while. Never start a duplicate batch while the original task may still be producing images.\n\nUse ordered filenames when files can be saved locally:\n\n```text\nimages/slide-01.png\nimages/slide-02.png\nimages/slide-03.png\n```\n\nIf local saving is not supported by the active image tool, explain the limitation and provide the generated previews or prompt set.\n\nThe ordered filename is for storage and HTML sequencing only. It must never be rendered inside the slide image. Do not put slide numbers, page numbers, sequence labels, numeric badges, or file names in the title, footer, corner, diagram, timeline, or any other visible area unless the user explicitly requires a number as part of the page content.\n\nAfter all images are complete, present their paths or previews for a dedicated image review. Ask: \"图片已生成。是否有页面需要修改？确认最终图片后，我会组装 HTML 播放器并生成逐页讲稿。\"\n\nDo not assemble HTML or write final speaker notes until the user explicitly approves the images. If the user requests image changes, regenerate only the affected pages where possible, then return to this image-review gate.\n\n## 7. Automatically assemble playable HTML slideshow\n\nAfter the user approves the final local slide images, automatically:\n\n- create an output folder with `index.html` and `assets/`;\n- copy or reference the final slide images in order as `assets/slide-01.png`, `assets/slide-02.png`, etc.;\n- generate a full-viewport 16:9 player modeled after `C:\\project\\img-ppt\\ai-course-html\\index.html`;\n- include previous/next buttons, click zones, keyboard navigation, progress display, and fullscreen support;\n- keep each image inside a 16:9 frame with `object-fit: contain`;\n- do not alter the slide images while assembling the HTML.\n\nUse `scripts/generate-html-player.mjs` when local image files are available. If images are not local files, explain that HTML assembly requires local image files and ask the user to provide them.\n\n## 8. Write final speaker notes\n\nAfter final images and HTML are ready, write the final speaker notes page by page. Use:\n\n- the confirmed brief;\n- the master outline and page-by-page outline;\n- expanded content and examples;\n- the final generated slide images and what each image visually emphasizes.\n\nTreat the confirmed presentation duration as a delivery constraint. Before writing, allocate target speaking time to every slide and ensure the total matches the requested duration, allowing only a small buffer for natural pauses and page transitions. Give substantive pages more time than title, agenda, or closing pages.\n\nFor every slide, provide:\n\n- `pageNumber`;\n- `imagePath`;\n- `targetDuration`: planned spoken time for the page;\n- `talkTrack`: a complete, directly readable oral script, not an outline or speaking hints;\n- `exampleLines`: examples, analogies, or mini-scenarios woven into the script where they improve clarity;\n- `transition`: a conversational bridge to the next page.\n\nSpeaker notes should sound like a person presenting to the target audience. Write enough natural spoken content to fill each page's target duration at a normal pace: approximately 180-240 Chinese characters per minute for Chinese, or 120-150 words per minute for English; adapt for the target language and the user's requested pace. Use short sentences, warm phrasing, and concrete examples. Include natural pauses, emphasis, and transitions where useful. Avoid report-style prose, slogans, stiff corporate language, terse bullet-point notes, and mechanically reading every visible word on the slide.\n\nAsk at the end: \"已生成图片、HTML 播放器和逐页讲稿。是否有页面、HTML 播放效果或讲稿需要调整？\"\n\n## Revision handling\n\n### Mandatory single-page revision loop\n\nWhenever the user requests any later change to one page, run this loop every time, including for small copy, layout, emphasis, example, data, or image corrections:\n\n1. Identify the target page and clarify the requested outcome, required facts, constraints, and unchanged elements. Ask only for missing information.\n2. Reuse the approved deck brief, LOGO decision, surrounding storyline, and complete deck-wide style lock. Do not repeat visual-style confirmation unless the user explicitly requests a style change.\n3. Rebuild that page's page-by-page outline fields: conclusion-style title, key question, governing thought, supporting logic, visual idea, so what, transition, and speaking-time allocation.\n4. Rebuild that page's expanded content, examples, labels, visual emphasis, and any factual constraints.\n5. Present the consolidated revised page content to the user and ask: \"这页修改后的逻辑、内容和视觉重点是否确认？确认后我会直接生成该页图片。\"\n6. Only after explicit content approval, rebuild the page's image prompt internally with the existing style lock. Do not show or ask the user to approve the prompt.\n7. Generate only the affected page image, preserve all other approved images, and present the new image for review.\n8. If the user requests another change to that page, restart this loop before generating again. Do not patch or regenerate the image directly from the latest feedback.\n9. After the revised image is approved, regenerate the HTML and affected final speaker notes if those downstream artifacts already exist.\n\n- Requirement edits require revising the outline, prompts, and images.\n- Outline edits require revising affected expanded content, prompts, images, HTML, and final speaker notes.\n- Final speaker-note edits require revising prompts only if visible text, page logic, or visual emphasis changes.\n- Style edits require revising all prompts, images, HTML, and final speaker notes unless the user limits the change to specific pages.\n- Internal prompt edits require regenerating affected images, but prompts never require user approval.\n- Image feedback should be applied through the mandatory single-page revision loop, followed by another explicit image review before HTML assembly and final speaker-note writing.\n- HTML output must be regenerated after any final image change.\n\nThis skill stops at PPT-style images, playable HTML, and final speaker notes. Do not assemble a PPTX.\n\nFile v0.1.3:skill-card.md\n\n## Description:\n\nTurns presentation ideas into McKinsey-style outlines, consistent 16:9 slide images, a playable HTML deck, and duration-aware speaker scripts.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[callmexhj](https://clawhub.ai/user/callmexhj)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nEmployees, external users, and presentation creators use this skill to turn a presentation brief into reviewed slide logic, generated 16:9 PPT-style images, a local HTML slideshow, and final spoken notes.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Slide content may be sent to image generation tools during the workflow.\n\nMitigation: Avoid sensitive or restricted content unless the user has approved that use and the image-generation environment is appropriate.\n\nRisk: The workflow writes generated images and a playable HTML deck to local output directories.\n\nMitigation: Use a clean output directory and review generated files before sharing or publishing them.\n\nRisk: Some prompts and player UI text are built around Chinese-language defaults.\n\nMitigation: Ask the agent to adapt the language when the deck or audience requires another locale.\n\n## Reference(s):\n\n- [Workflow](references/workflow.md)\n- [McKinsey-Style Outline](references/mckinsey-outline.md)\n- [Image-2 Prompt Rules](references/image-2-prompts.md)\n- [Generate HTML Player](scripts/generate-html-player.mjs)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Files, Code, Shell commands, Guidance]\n\n**Output Format:** [Markdown workflow outputs plus generated slide image files, prompt records, an HTML slideshow, and speaker notes.]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Produces one 16:9 image per approved slide and requires explicit approval gates before HTML assembly and final speaker notes.]\n\n## Skill Version(s):\n\n0.1.3 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v0.1.3:agents/openai.yaml\n\ninterface:\r\n  display_name: \"PPT 图片生成\"\r\n  short_description: \"生成大纲、PPT 图片、HTML 播放器和最终讲稿\"\n  default_prompt: \"使用 $image-ppt-maker 帮我确认 PPT 需求和 LOGO 预留区域，生成麦肯锡式大纲，先确认图片风格，再生成统一风格的 image-2 提示词和 PPT 图片；图片完成后自动生成 16:9 HTML 播放器，并结合最终图片输出逐页口语化讲稿。\"\n\nArchive v0.1.2: 8 files, 16419 bytes\n\nFiles: agents/openai.yaml (432b), references/image-2-prompts.md (5197b), references/mckinsey-outline.md (2768b), references/workflow.md (10206b), scripts/generate-html-player.mjs (8338b), skill-card.md (2345b), SKILL.md (6736b), _meta.json (134b)\n\nFile v0.1.2:SKILL.md\n\n---\nname: image-ppt-maker\ndescription: \"Create PPT-style images through a human-in-the-loop workflow: clarify presentation requirements including optional top-corner LOGO space, research and draft McKinsey-style master and page-by-page outlines, expand page content, confirm the desired visual style before image prompts, write unified-style image-2 prompts, batch-generate 16:9 slide images, automatically assemble the images into a playable 16:9 HTML slideshow, and finally write oral speaker notes based on the outline and final images. Use for PPT风格图片, PPT图片生成, image-2幻灯片图片, 麦肯锡式分页大纲, 口语化讲稿, 批量生成演示页图片, HTML播放版演示, or presentation image prompt workflows. This skill does not assemble PPTX files.\"\n---\n\n# Image PPT Maker\n\nHelp users create a set of PPT-style slide images with image-2. Use a strict review-gated workflow:\n\n1. Confirm requirements.\n2. Build a McKinsey-style master outline and page-by-page outline.\n3. Expand the outline content.\n4. Confirm the desired visual style for the images.\n5. Write unified-style image-2 prompts.\n6. Batch-generate 16:9 PPT images.\n7. Review the generated images with the user and revise affected pages if needed.\n8. Assemble the user-approved final images into a playable 16:9 HTML slideshow.\n9. Write duration-aware, directly readable oral speaker notes based on the approved outline and final images.\n\nAsk the user whether they want changes at each review gate. Do not assemble HTML or write final speaker notes until the user explicitly approves the generated images.\n\n## Required References\n\n- Read [workflow.md](references/workflow.md) before starting any task.\n- Read [mckinsey-outline.md](references/mckinsey-outline.md) before drafting or revising outlines.\n- Read [image-2-prompts.md](references/image-2-prompts.md) before writing prompts or generating images.\n- Use [generate-html-player.mjs](scripts/generate-html-player.mjs) only after the user approves final local images for a playable HTML output.\n\n## Core Rules\n\n1. Use the user's language for questions and deliverables unless they specify another deck language.\n2. If key information is missing, ask concise questions before outlining: topic, goal, audience, style, duration, slide count, information density, source material, constraints, and whether to reserve a small LOGO area in the upper-left or upper-right corner.\n3. Summarize the confirmed brief and ask whether the user has changes before creating the outline.\n4. Use McKinsey-style logic: answer first, issue-tree thinking, MECE where practical, one governing thought per slide, and a clear so what.\n5. Every page in the outline must include logic notes. Do not create title-only or decorative pages.\n6. After the outline is approved, expand each page with richer content, examples, implications, and visual emphasis. Do not output speaker notes yet.\n7. Before writing image prompts, ask the user what visual style they prefer and recommend context-aware options such as training style with friendly editorial illustrations, executive report style with restrained illustration accents, illustration-led storytelling with recurring characters and scenes, graphic/chart-heavy, product demo style, or other suitable options.\n8. Generate one image per slide, 16:9, with image-2. Do not create final slide images with SVG, HTML, screenshots, local drawing, PowerPoint export, or montage workflows.\n9. Treat image generation as a long-running operation. Do not interpret a quiet period, a partial preview, or a tool call with no immediate new image as failure. Keep the generation task alive, wait for its final completion signal, inspect the output directory for newly completed files, and report progress without triggering a duplicate generation. Retry only after an explicit tool failure, confirmed timeout, or confirmed missing/corrupt output after completion.\n10. After image generation, present the final image paths or previews and ask the user whether any page needs adjustment. Do not assemble HTML or write final speaker notes until the user explicitly approves the images.\n11. After the user approves the images, automatically generate a playable 16:9 HTML slideshow from the final local images.\n12. After HTML assembly, write final per-slide speaker notes based on the approved outline and final images. Allocate page-level speaking time to match the confirmed duration, and write a complete, directly readable oral script for each page.\n13. This skill does not assemble PPTX files. Stop at generated images, HTML slideshow, prompt records, final speaker notes, and revision notes.\n14. Preserve approved work during revisions. Only regenerate the affected downstream artifacts.\n\n## Workflow Gates\n\nDo not skip these review points:\n\n- After requirement parsing: ask whether the brief and assumptions need changes.\n- After the master outline and page-by-page outline: ask whether the storyline, page count, or logic needs changes.\n- After the expanded outline content: ask whether the content depth, examples, or emphasis needs changes.\n- Before writing image-2 prompts: ask which visual style the user prefers, offering context-aware recommendations that include concrete illustration directions when illustration is suitable.\n- After image-2 prompts: ask whether the style, visible text, or page prompts need changes.\n- After image generation: present the completed images and ask whether any page needs changes; wait for explicit approval before HTML assembly and final speaker notes.\n- After HTML assembly and final speaker notes: ask whether any HTML output or speaker note should be adjusted.\n\nIf the user requests changes:\n\n- Requirement changes invalidate outline, prompts, and images.\n- Outline changes invalidate affected expanded content, prompts, images, HTML, and final speaker notes.\n- Visual-style changes invalidate prompts, images, HTML, and final speaker notes.\n- Final speaker-note changes do not invalidate prompts, images, or HTML unless the visible slide content or logic changes.\n- Prompt or style changes invalidate the affected images.\n- Image issues require regenerating only the affected pages when possible; re-run the image review gate after every image revision.\n- HTML output must be regenerated if final image filenames, image count, title, or image folder changes.\n\n## Deliverables\n\nWhen complete, provide:\n\n- confirmed brief;\n- master outline and page-by-page outline;\n- expanded outline content;\n- image-2 prompt set with the shared style lock;\n- generated image paths or previews;\n- playable 16:9 HTML slideshow path;\n- final oral speaker notes based on the outline and generated images;\n- concise notes on pages that may need regeneration.\n\nFile v0.1.2:_meta.json\n\n{\n  \"ownerId\": \"kn7dddd3v8yk96jx32p2gsmnvh8a03gt\",\n  \"slug\": \"image-ppt-maker\",\n  \"version\": \"0.1.2\",\n  \"publishedAt\": 1783663214368\n}\n\nFile v0.1.2:references/image-2-prompts.md\n\n# Image-2 Prompt Rules\n\nWrite prompts for image-2. Each prompt must generate exactly one 16:9 PPT-style slide image.\n\n## Deck-wide style lock\n\nDefine one shared style lock before per-page prompts. It must specify:\n\n- aspect ratio: 16:9;\n- deck type: professional consulting-style PPT page;\n- layout system: title area, content grid, margins, chart/table/card treatment;\n- palette: primary, secondary, background, accent colors;\n- typography: clear hierarchy, readable slide text, no decorative fonts;\n- visual language: charts, diagrams, icons, photography, or abstract business visuals;\n- density: high, medium, or low;\n- optional LOGO space: no reserved area, upper-left reserved area, or upper-right reserved area;\n- consistency rule: every page must look like part of the same deck.\n\nRepeat the complete style lock inside every page prompt, but mark it as non-visible generation guidance. The style lock must influence layout and visual treatment only; image-2 must not render the style-lock wording as text on the slide.\n\n## Per-page prompt structure\n\nEach page prompt must include:\n\n1. `Model`: image-2.\n2. `Task`: generate only this single 16:9 PPT slide image.\n3. `Style lock`: copy the shared deck-wide style lock.\n4. `Style text handling`: state that style descriptions are instructions only and must not appear as visible text.\n5. `Slide logic`: key question, governing thought, supporting logic, so what, transition.\n6. `Expanded content`: the richer explanation or examples that should guide the visual emphasis.\n7. `LOGO space`: if requested, reserve a small clear area in the chosen top corner; do not invent or render a logo unless the user provided one.\n8. `Page message and content`: explain the thought this page should express, the core content to show, and the recommended title, key messages, labels, and emphasis.\n9. `Composition`: layout, visual hierarchy, chart or diagram structure, spacing, alignment.\n10. `Readability`: clean typography, enough contrast, no tiny unreadable text.\n11. `Constraints`: factual constraints and source-material limits.\n12. `Negative constraints`: forbidden outputs.\n\n## Page message and content\n\nDo not constrain the slide by enumerating every allowed visible word. Instead, describe the page's intended communication clearly enough for image-2 to design the slide:\n\n- State the page's governing thought in an answer-first way.\n- Explain the core content the slide should communicate, including the most important evidence, comparison, process, framework, or recommendation.\n- Suggest the title, short labels, callouts, and chart/table labels that would help express the idea, but keep text concise and slide-like.\n- Preserve McKinsey-style communication: structured, logical, executive-readable, and focused on one message per page.\n- Do not render prompt section labels or internal reasoning labels such as \"Style lock\", \"Slide logic\", \"Expanded content\", \"Page message and content\", \"McKinsey-style\", \"16:9\", \"professional consulting-style\", or \"image-2\".\n- If a style concept needs to show visually, express it through layout, color, spacing, chart treatment, and imagery, not through written words.\n- If a LOGO area is reserved, it is a blank layout area unless the user supplies a logo. Do not render placeholder text such as \"LOGO\".\n- Slide sequence numbers are file-management metadata only. Do not render page numbers, slide numbers, sequence labels, numeric badges, or file names anywhere in the image unless a number is explicitly part of the approved page content.\n- For illustration-led styles, express the approved visual direction through recurring characters, coherent scenes, consistent linework or rendering, and visual metaphors; do not write the style name or illustration instructions on the slide.\n\nAdd this sentence to every prompt:\n\n```text\nRender concise slide text that supports the page message; all style descriptions, prompt section labels, and generation instructions are non-visible guidance and must not appear as words in the slide image.\n```\n\n## Negative constraints\n\nAlways forbid:\n\n- multiple slides in one image;\n- montage, contact sheet, overview, collage, or thumbnail grid;\n- browser screenshot, app screenshot, chat screenshot, or document screenshot;\n- long paragraphs, dense report prose, or text that does not support the page's governing thought;\n- any visible wording copied from style descriptions, prompt section labels, or generation instructions;\n- page numbers, slide numbers, sequence labels, numeric badges, or file names added only to identify the image;\n- meta words such as style lock, deck-wide style, 16:9, image-2, prompt, McKinsey-style, typography, palette, layout system, consulting-style, Page message and content, or LOGO;\n- watermark, signature, logo, model mark, or random brand mark;\n- random icons, people, company names, or data not provided or approved;\n- SVG, HTML, wireframe, or code-like rendering.\n\n## Batch output\n\nGenerate one image per approved prompt. Use ordered names when saving files:\n\n```text\nimages/slide-01.png\nimages/slide-02.png\nimages/slide-03.png\n```\n\nIf a page fails visually, revise or regenerate that page only unless the style lock itself changed.\n\nFile v0.1.2:references/mckinsey-outline.md\n\n# McKinsey-Style Outline\n\nUse this structure for the master outline and every page outline.\n\n## Principles\n\n- Answer first: lead with the conclusion or recommendation.\n- Pyramid structure: conclusion, reasons, evidence.\n- Issue tree: split the topic into a small number of logical questions.\n- MECE where practical: reduce overlap and gaps.\n- One slide, one message: each page has one governing thought.\n- So what: every page explains why the point matters to the audience.\n\n## Master outline format\n\nInclude:\n\n- `coreAnswer`: the answer-first conclusion of the whole deck;\n- `audienceDecision`: what the audience should decide or do;\n- `logicChain`: 3-5 major reasoning steps;\n- `sections`: major sections with the question each section answers;\n- `storyFlow`: why the sequence is persuasive.\n\n## Page-by-page outline format\n\nFor each page, include:\n\n- `pageNumber`;\n- `title`: conclusion-style title, not a topic label;\n- `keyQuestion`: the question this page answers;\n- `governingThought`: the page's answer-first message;\n- `supportingLogic`: 2-4 reasons, evidence points, or observations;\n- `visualIdea`: the visual structure that best supports the logic;\n- `soWhat`: why the audience should care;\n- `transition`: why the next page follows.\n\n## Visual logic mapping\n\n- Compare options: side-by-side comparison.\n- Explain drivers: driver tree, layered model, or waterfall.\n- Show sequence: timeline, roadmap, or process.\n- Prioritize: matrix, ranking, or funnel.\n- Recommend action: chosen path plus reasons.\n- Summarize system: architecture, operating model, or flywheel.\n\nDo not use decorative visuals that fail to carry the logic.\n\n## Expanded outline content\n\nAfter the page-by-page outline is approved, expand each page before writing image prompts.\n\nFor each page, include:\n\n- `expandedContent`: 1-3 short paragraphs that deepen the page logic with evidence, implications, and examples;\n- `exampleIdeas`: 2-4 concrete examples, analogies, or mini-scenarios that make the point easier to understand;\n- `visualEmphasis`: what the generated image should make most obvious;\n- `speakerNoteHints`: brief reminders for final speaker-note writing after images are generated.\n\nDo not write the final speaker notes at this stage. Final notes must be written after images are generated, using the approved outline and the final visual output.\n\n## Final speaker notes\n\nAfter the final images and HTML player are generated, write page-by-page speaker notes.\n\nSpeaker notes must:\n\n- sound like a real presenter, not a written report;\n- use clear, warm, direct language;\n- explain the point with concrete examples when useful;\n- refer naturally to what the audience can see on the generated page;\n- avoid over-polished slogans, dense jargon, and reading every slide label.\n\nFile v0.1.2:references/workflow.md\n\n# Workflow\n\nFollow this workflow exactly. Each stage ends with a user review question before moving to the next stage.\n\n## 1. Confirm requirements\n\nParse the user's request and collect missing key details:\n\n- topic and background;\n- presentation goal: what the audience should understand, believe, decide, or do;\n- audience: executives, customers, internal team, review panel, investors, or another group;\n- duration and approximate slide count; use the duration as the total speaking-time budget for the final script;\n- information density: high, medium, or low;\n- preferred visual style or reference material;\n- source material, facts, data, cases, and constraints;\n- output language and tone;\n- whether to reserve a small LOGO area in the upper-left or upper-right corner, or no LOGO area;\n- any content that must not be invented.\n\nIf the user is unsure, recommend practical defaults:\n\n- duration: 10 minutes;\n- slide count: 8-12 pages;\n- information density: medium;\n- style: clean McKinsey-style consulting deck with restrained color, strong hierarchy, and chart-like logic.\n- LOGO area: no reserved LOGO area unless the user asks; if they want it, recommend a small upper-right area for corporate decks and upper-left for brand-led decks.\n\nThen summarize the brief, including the LOGO-space decision, and ask: \"以上需求和假设是否需要修改？确认后我会生成总纲和分页大纲。\"\n\n## 2. Research and outline\n\nUse the user's source material first. If internet research is requested or required for current facts, browse and cite sources in the final summary.\n\nCreate:\n\n- master outline: core answer, main logic chain, issue tree, and section flow;\n- page-by-page outline: one page per slide, with complete logic notes and a suggested speaking-time allocation. Allocate the total speaking time across pages according to message importance and complexity; keep the sum aligned with the confirmed duration.\n\nAsk: \"这个总纲和分页大纲是否需要调整？确认后我会生成每页的 image-2 提示词。\"\n\n## 3. Expand outline content\n\nAfter the user approves the master outline and page-by-page outline, expand the content before prompt writing.\n\nFor each slide, produce:\n\n- expanded content: richer explanation of the page's message, evidence, implications, and examples;\n- example ideas: practical examples, analogies, or mini-scenarios that make the point concrete;\n- visual emphasis: what the generated image should make most obvious;\n- speaking hints: brief notes that may help final speaker-note writing later, but do not output the final talk track yet.\n\nDo not output the final speaker notes in this stage. Final notes must be written after image generation and HTML assembly, using the approved outline and the final generated images.\n\nAsk: \"拓展后的内容、例子和视觉重点是否需要调整？确认后我会先和你确认图片风格，再生成每页的 image-2 提示词。\"\n\n## 4. Confirm visual style\n\nBefore writing image-2 prompts, ask the user what visual style they want. Recommend options based on the context instead of using a fixed list.\n\nCommon options include:\n\n- 培训风：更亲和，结构清楚，适合课程、工作坊、内部分享；\n- 汇报风：更克制、专业、结论先行，适合管理层汇报和项目汇报；\n- 培训插画风：在清晰的咨询式结构中加入友好人物、课堂/工作场景、轻量叙事插画和统一笔触，适合课程、工作坊、内部分享；\n- 插画叙事风：用连续出现的角色、场景和视觉隐喻讲清问题变化，搭配少量结构化图形，适合传播、培训、文化和用户故事类主题；\n- 汇报插画风：保持结论先行和克制留白，用少量高质量场景插画解释复杂概念，适合管理层汇报中需要提升亲和力的主题；\n- 多图形：更多框架图、流程图、矩阵、图表，适合战略、经营、方案类主题；\n- 科技感：更适合 AI、数字化、产品技术主题；\n- 品牌简洁风：留白更多，适合客户沟通、品牌展示、对外路演。\n\nRecommend 2-4 options that fit the user's topic, audience, duration, and information density, then ask: \"你更倾向哪种图片风格？确认后我会把这个风格锁定到整套 image-2 提示词中。\"\n\n## 5. Write image-2 prompts\n\nBefore writing per-page prompts, define one deck-wide style lock. Apply it to every prompt.\n\nFor each slide, write one self-contained image-2 prompt that includes:\n\n- shared style lock;\n- single-slide 16:9 instruction;\n- LOGO-space instruction if the user requested one;\n- page logic;\n- expanded content and speaker-note intent where useful;\n- the thought and content this page should express, including recommended title, key messages, labels, and emphasis;\n- composition and visual structure;\n- negative constraints.\n\nAsk: \"这些 image-2 提示词是否需要修改？确认后我会批量生成 PPT 图片。\"\n\n## 6. Batch-generate images\n\nGenerate exactly one 16:9 image per slide with image-2.\n\nGeneration may take many minutes. When generating several pages in parallel or in a batch:\n\n- announce that the operation is long-running and that no immediate new preview does not mean generation failed;\n- keep the original generation task running and wait for its final return/completion signal;\n- monitor completed files or returned images without launching a second batch;\n- preserve already completed pages and report the current count when progress is available;\n- retry only after explicit failure, confirmed timeout, or confirmed missing/corrupt output after the task has ended.\n\nNever claim that a batch failed merely because it has been quiet for a while. Never start a duplicate batch while the original task may still be producing images.\n\nUse ordered filenames when files can be saved locally:\n\n```text\nimages/slide-01.png\nimages/slide-02.png\nimages/slide-03.png\n```\n\nIf local saving is not supported by the active image tool, explain the limitation and provide the generated previews or prompt set.\n\nThe ordered filename is for storage and HTML sequencing only. It must never be rendered inside the slide image. Do not put slide numbers, page numbers, sequence labels, numeric badges, or file names in the title, footer, corner, diagram, timeline, or any other visible area unless the user explicitly requires a number as part of the page content.\n\nAfter all images are complete, present their paths or previews for a dedicated image review. Ask: \"图片已生成。是否有页面需要修改？确认最终图片后，我会组装 HTML 播放器并生成逐页讲稿。\"\n\nDo not assemble HTML or write final speaker notes until the user explicitly approves the images. If the user requests image changes, regenerate only the affected pages where possible, then return to this image-review gate.\n\n## 7. Automatically assemble playable HTML slideshow\n\nAfter the user approves the final local slide images, automatically:\n\n- create an output folder with `index.html` and `assets/`;\n- copy or reference the final slide images in order as `assets/slide-01.png`, `assets/slide-02.png`, etc.;\n- generate a full-viewport 16:9 player modeled after `C:\\project\\img-ppt\\ai-course-html\\index.html`;\n- include previous/next buttons, click zones, keyboard navigation, progress display, and fullscreen support;\n- keep each image inside a 16:9 frame with `object-fit: contain`;\n- do not alter the slide images while assembling the HTML.\n\nUse `scripts/generate-html-player.mjs` when local image files are available. If images are not local files, explain that HTML assembly requires local image files and ask the user to provide them.\n\n## 8. Write final speaker notes\n\nAfter final images and HTML are ready, write the final speaker notes page by page. Use:\n\n- the confirmed brief;\n- the master outline and page-by-page outline;\n- expanded content and examples;\n- the final generated slide images and what each image visually emphasizes.\n\nTreat the confirmed presentation duration as a delivery constraint. Before writing, allocate target speaking time to every slide and ensure the total matches the requested duration, allowing only a small buffer for natural pauses and page transitions. Give substantive pages more time than title, agenda, or closing pages.\n\nFor every slide, provide:\n\n- `pageNumber`;\n- `imagePath`;\n- `targetDuration`: planned spoken time for the page;\n- `talkTrack`: a complete, directly readable oral script, not an outline or speaking hints;\n- `exampleLines`: examples, analogies, or mini-scenarios woven into the script where they improve clarity;\n- `transition`: a conversational bridge to the next page.\n\nSpeaker notes should sound like a person presenting to the target audience. Write enough natural spoken content to fill each page's target duration at a normal pace: approximately 180-240 Chinese characters per minute for Chinese, or 120-150 words per minute for English; adapt for the target language and the user's requested pace. Use short sentences, warm phrasing, and concrete examples. Include natural pauses, emphasis, and transitions where useful. Avoid report-style prose, slogans, stiff corporate language, terse bullet-point notes, and mechanically reading every visible word on the slide.\n\nAsk at the end: \"已生成图片、HTML 播放器和逐页讲稿。是否有页面、HTML 播放效果或讲稿需要调整？\"\n\n## Revision handling\n\n- Requirement edits require revising the outline, prompts, and images.\n- Outline edits require revising affected expanded content, prompts, images, HTML, and final speaker notes.\n- Final speaker-note edits require revising prompts only if visible text, page logic, or visual emphasis changes.\n- Style edits require revising all prompts, images, HTML, and final speaker notes unless the user limits the change to specific pages.\n- Prompt edits require regenerating affected images.\n- Image feedback should be applied page by page when possible, followed by another explicit image review before HTML assembly and final speaker-note writing.\n- HTML output must be regenerated after any final image change.\n\nThis skill stops at PPT-style images, playable HTML, and final speaker notes. Do not assemble a PPTX.\n\nFile v0.1.2:skill-card.md\n\n## Description: <br>\nCreate PPT-style slide images through a review-gated workflow that clarifies requirements, drafts and expands McKinsey-style outlines, writes image-2 prompts, generates 16:9 slide images, assembles an HTML slideshow, and writes speaker notes. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[callmexhj](https://clawhub.ai/user/callmexhj) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nPresentation creators, consultants, trainers, and business users use this skill to turn a brief or source material into a review-gated set of PPT-style slide images, an HTML slideshow, and oral speaker notes. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The HTML slideshow helper copies approved slide images and writes index.html and assets into the selected output folder. <br>\nMitigation: Use a dedicated output folder and review the final approved images before HTML assembly. <br>\nRisk: Generated outlines, slide images, and speaker notes may contain factual, visual, or presentation-quality issues. <br>\nMitigation: Use the built-in review gates to check requirements, outlines, prompts, generated images, HTML output, and speaker notes before relying on the deliverables. <br>\n\n\n## Reference(s): <br>\n- [Workflow](references/workflow.md) <br>\n- [McKinsey-Style Outline](references/mckinsey-outline.md) <br>\n- [Image-2 Prompt Rules](references/image-2-prompts.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Text, Markdown, Code, Shell commands, Guidance, Files] <br>\n**Output Format:** [Markdown workflow outputs with image prompts, local image paths, HTML/CSS/JavaScript slideshow files, and speaker notes] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [The workflow is review-gated and ends at generated images, a playable HTML slideshow, prompt records, speaker notes, and revision notes; it does not assemble PPTX files.] <br>\n\n## Skill Version(s): <br>\n0.1.2 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nFile v0.1.2:agents/openai.yaml\n\ninterface:\r\n  display_name: \"PPT 图片生成\"\r\n  short_description: \"生成大纲、PPT 图片、HTML 播放器和最终讲稿\"\n  default_prompt: \"使用 $image-ppt-maker 帮我确认 PPT 需求和 LOGO 预留区域，生成麦肯锡式大纲，先确认图片风格，再生成统一风格的 image-2 提示词和 PPT 图片；图片完成后自动生成 16:9 HTML 播放器，并结合最终图片输出逐页口语化讲稿。\"\n\nArchive v0.1.1: 8 files, 15833 bytes\n\nFiles: agents/openai.yaml (432b), references/image-2-prompts.md (5197b), references/mckinsey-outline.md (2768b), references/workflow.md (8704b), scripts/generate-html-player.mjs (8338b), skill-card.md (2690b), SKILL.md (6182b), _meta.json (134b)\n\nFile v0.1.1:SKILL.md\n\n---\nname: image-ppt-maker\ndescription: \"Create PPT-style images through a human-in-the-loop workflow: clarify presentation requirements including optional top-corner LOGO space, research and draft McKinsey-style master and page-by-page outlines, expand page content, confirm the desired visual style before image prompts, write unified-style image-2 prompts, batch-generate 16:9 slide images, automatically assemble the images into a playable 16:9 HTML slideshow, and finally write oral speaker notes based on the outline and final images. Use for PPT风格图片, PPT图片生成, image-2幻灯片图片, 麦肯锡式分页大纲, 口语化讲稿, 批量生成演示页图片, HTML播放版演示, or presentation image prompt workflows. This skill does not assemble PPTX files.\"\n---\n\n# Image PPT Maker\n\nHelp users create a set of PPT-style slide images with image-2. Use a strict review-gated workflow:\n\n1. Confirm requirements.\n2. Build a McKinsey-style master outline and page-by-page outline.\n3. Expand the outline content.\n4. Confirm the desired visual style for the images.\n5. Write unified-style image-2 prompts.\n6. Batch-generate 16:9 PPT images.\n7. Wait for the image-generation task to finish and verify the files before assembling a playable 16:9 HTML slideshow.\n8. Write final oral speaker notes based on the approved outline and final images.\n\nAsk the user whether they want changes at each review gate. Do not ask before HTML assembly; generate the HTML player automatically after final images are available.\n\n## Required References\n\n- Read [workflow.md](references/workflow.md) before starting any task.\n- Read [mckinsey-outline.md](references/mckinsey-outline.md) before drafting or revising outlines.\n- Read [image-2-prompts.md](references/image-2-prompts.md) before writing prompts or generating images.\n- Use [generate-html-player.mjs](scripts/generate-html-player.mjs) only when the user asks for a playable HTML output after images exist.\n\n## Core Rules\n\n1. Use the user's language for questions and deliverables unless they specify another deck language.\n2. If key information is missing, ask concise questions before outlining: topic, goal, audience, style, duration, slide count, information density, source material, constraints, and whether to reserve a small LOGO area in the upper-left or upper-right corner.\n3. Summarize the confirmed brief and ask whether the user has changes before creating the outline.\n4. Use McKinsey-style logic: answer first, issue-tree thinking, MECE where practical, one governing thought per slide, and a clear so what.\n5. Every page in the outline must include logic notes. Do not create title-only or decorative pages.\n6. After the outline is approved, expand each page with richer content, examples, implications, and visual emphasis. Do not output speaker notes yet.\n7. Before writing image prompts, ask the user what visual style they prefer and recommend context-aware options such as training style with friendly editorial illustrations, executive report style with restrained illustration accents, illustration-led storytelling with recurring characters and scenes, graphic/chart-heavy, product demo style, or other suitable options.\n8. Generate one image per slide, 16:9, with image-2. Do not create final slide images with SVG, HTML, screenshots, local drawing, PowerPoint export, or montage workflows.\n9. Treat image generation as a long-running operation. Do not interpret a quiet period, a partial preview, or a tool call with no immediate new image as failure. Keep the generation task alive, wait for its final completion signal, inspect the output directory for newly completed files, and report progress without triggering a duplicate generation. Retry only after an explicit tool failure, confirmed timeout, or confirmed missing/corrupt output after completion.\n10. After image generation, automatically generate a playable 16:9 HTML slideshow from the final images when local image files exist.\n11. After HTML assembly, write final per-slide speaker notes based on the approved outline and the generated images. The notes must sound oral, natural, sincere, friendly, and example-driven.\n12. This skill does not assemble PPTX files. Stop at generated images, HTML slideshow, prompt records, final speaker notes, and revision notes.\n13. Preserve approved work during revisions. Only regenerate the affected downstream artifacts.\n\n## Workflow Gates\n\nDo not skip these review points:\n\n- After requirement parsing: ask whether the brief and assumptions need changes.\n- After the master outline and page-by-page outline: ask whether the storyline, page count, or logic needs changes.\n- After the expanded outline content: ask whether the content depth, examples, or emphasis needs changes.\n- Before writing image-2 prompts: ask which visual style the user prefers, offering context-aware recommendations that include concrete illustration directions when illustration is suitable.\n- After image-2 prompts: ask whether the style, visible text, or page prompts need changes.\n- After HTML assembly and final speaker notes: ask whether any page, HTML output, or speaker note should be adjusted.\n\nIf the user requests changes:\n\n- Requirement changes invalidate outline, prompts, and images.\n- Outline changes invalidate affected expanded content, prompts, images, HTML, and final speaker notes.\n- Visual-style changes invalidate prompts, images, HTML, and final speaker notes.\n- Final speaker-note changes do not invalidate prompts, images, or HTML unless the visible slide content or logic changes.\n- Prompt or style changes invalidate the affected images.\n- Image issues require regenerating only the affected pages when possible.\n- HTML output must be regenerated if final image filenames, image count, title, or image folder changes.\n\n## Deliverables\n\nWhen complete, provide:\n\n- confirmed brief;\n- master outline and page-by-page outline;\n- expanded outline content;\n- image-2 prompt set with the shared style lock;\n- generated image paths or previews;\n- playable 16:9 HTML slideshow path;\n- final oral speaker notes based on the outline and generated images;\n- concise notes on pages that may need regeneration.\n\nFile v0.1.1:_meta.json\n\n{\n  \"ownerId\": \"kn7dddd3v8yk96jx32p2gsmnvh8a03gt\",\n  \"slug\": \"image-ppt-maker\",\n  \"version\": \"0.1.1\",\n  \"publishedAt\": 1783659770629\n}\n\nFile v0.1.1:references/image-2-prompts.md\n\n# Image-2 Prompt Rules\n\nWrite prompts for image-2. Each prompt must generate exactly one 16:9 PPT-style slide image.\n\n## Deck-wide style lock\n\nDefine one shared style lock before per-page prompts. It must specify:\n\n- aspect ratio: 16:9;\n- deck type: professional consulting-style PPT page;\n- layout system: title area, content grid, margins, chart/table/card treatment;\n- palette: primary, secondary, background, accent colors;\n- typography: clear hierarchy, readable slide text, no decorative fonts;\n- visual language: charts, diagrams, icons, photography, or abstract business visuals;\n- density: high, medium, or low;\n- optional LOGO space: no reserved area, upper-left reserved area, or upper-right reserved area;\n- consistency rule: every page must look like part of the same deck.\n\nRepeat the complete style lock inside every page prompt, but mark it as non-visible generation guidance. The style lock must influence layout and visual treatment only; image-2 must not render the style-lock wording as text on the slide.\n\n## Per-page prompt structure\n\nEach page prompt must include:\n\n1. `Model`: image-2.\n2. `Task`: generate only this single 16:9 PPT slide image.\n3. `Style lock`: copy the shared deck-wide style lock.\n4. `Style text handling`: state that style descriptions are instructions only and must not appear as visible text.\n5. `Slide logic`: key question, governing thought, supporting logic, so what, transition.\n6. `Expanded content`: the richer explanation or examples that should guide the visual emphasis.\n7. `LOGO space`: if requested, reserve a small clear area in the chosen top corner; do not invent or render a logo unless the user provided one.\n8. `Page message and content`: explain the thought this page should express, the core content to show, and the recommended title, key messages, labels, and emphasis.\n9. `Composition`: layout, visual hierarchy, chart or diagram structure, spacing, alignment.\n10. `Readability`: clean typography, enough contrast, no tiny unreadable text.\n11. `Constraints`: factual constraints and source-material limits.\n12. `Negative constraints`: forbidden outputs.\n\n## Page message and content\n\nDo not constrain the slide by enumerating every allowed visible word. Instead, describe the page's intended communication clearly enough for image-2 to design the slide:\n\n- State the page's governing thought in an answer-first way.\n- Explain the core content the slide should communicate, including the most important evidence, comparison, process, framework, or recommendation.\n- Suggest the title, short labels, callouts, and chart/table labels that would help express the idea, but keep text concise and slide-like.\n- Preserve McKinsey-style communication: structured, logical, executive-readable, and focused on one message per page.\n- Do not render prompt section labels or internal reasoning labels such as \"Style lock\", \"Slide logic\", \"Expanded content\", \"Page message and content\", \"McKinsey-style\", \"16:9\", \"professional consulting-style\", or \"image-2\".\n- If a style concept needs to show visually, express it through layout, color, spacing, chart treatment, and imagery, not through written words.\n- If a LOGO area is reserved, it is a blank layout area unless the user supplies a logo. Do not render placeholder text such as \"LOGO\".\n- Slide sequence numbers are file-management metadata only. Do not render page numbers, slide numbers, sequence labels, numeric badges, or file names anywhere in the image unless a number is explicitly part of the approved page content.\n- For illustration-led styles, express the approved visual direction through recurring characters, coherent scenes, consistent linework or rendering, and visual metaphors; do not write the style name or illustration instructions on the slide.\n\nAdd this sentence to every prompt:\n\n```text\nRender concise slide text that supports the page message; all style descriptions, prompt section labels, and generation instructions are non-visible guidance and must not appear as words in the slide image.\n```\n\n## Negative constraints\n\nAlways forbid:\n\n- multiple slides in one image;\n- montage, contact sheet, overview, collage, or thumbnail grid;\n- browser screenshot, app screenshot, chat screenshot, or document screenshot;\n- long paragraphs, dense report prose, or text that does not support the page's governing thought;\n- any visible wording copied from style descriptions, prompt section labels, or generation instructions;\n- page numbers, slide numbers, sequence labels, numeric badges, or file names added only to identify the image;\n- meta words such as style lock, deck-wide style, 16:9, image-2, prompt, McKinsey-style, typography, palette, layout system, consulting-style, Page message and content, or LOGO;\n- watermark, signature, logo, model mark, or random brand mark;\n- random icons, people, company names, or data not provided or approved;\n- SVG, HTML, wireframe, or code-like rendering.\n\n## Batch output\n\nGenerate one image per approved prompt. Use ordered names when saving files:\n\n```text\nimages/slide-01.png\nimages/slide-02.png\nimages/slide-03.png\n```\n\nIf a page fails visually, revise or regenerate that page only unless the style lock itself changed.\n\nFile v0.1.1:references/mckinsey-outline.md\n\n# McKinsey-Style Outline\n\nUse this structure for the master outline and every page outline.\n\n## Principles\n\n- Answer first: lead with the conclusion or recommendation.\n- Pyramid structure: conclusion, reasons, evidence.\n- Issue tree: split the topic into a small number of logical questions.\n- MECE where practical: reduce overlap and gaps.\n- One slide, one message: each page has one governing thought.\n- So what: every page explains why the point matters to the audience.\n\n## Master outline format\n\nInclude:\n\n- `coreAnswer`: the answer-first conclusion of the whole deck;\n- `audienceDecision`: what the audience should decide or do;\n- `logicChain`: 3-5 major reasoning steps;\n- `sections`: major sections with the question each section answers;\n- `storyFlow`: why the sequence is persuasive.\n\n## Page-by-page outline format\n\nFor each page, include:\n\n- `pageNumber`;\n- `title`: conclusion-style title, not a topic label;\n- `keyQuestion`: the question this page answers;\n- `governingThought`: the page's answer-first message;\n- `supportingLogic`: 2-4 reasons, evidence points, or observations;\n- `visualIdea`: the visual structure that best supports the logic;\n- `soWhat`: why the audience should care;\n- `transition`: why the next page follows.\n\n## Visual logic mapping\n\n- Compare options: side-by-side comparison.\n- Explain drivers: driver tree, layered model, or waterfall.\n- Show sequence: timeline, roadmap, or process.\n- Prioritize: matrix, ranking, or funnel.\n- Recommend action: chosen path plus reasons.\n- Summarize system: architecture, operating model, or flywheel.\n\nDo not use decorative visuals that fail to carry the logic.\n\n## Expanded outline content\n\nAfter the page-by-page outline is approved, expand each page before writing image prompts.\n\nFor each page, include:\n\n- `expandedContent`: 1-3 short paragraphs that deepen the page logic with evidence, implications, and examples;\n- `exampleIdeas`: 2-4 concrete examples, analogies, or mini-scenarios that make the point easier to understand;\n- `visualEmphasis`: what the generated image should make most obvious;\n- `speakerNoteHints`: brief reminders for final speaker-note writing after images are generated.\n\nDo not write the final speaker notes at this stage. Final notes must be written after images are generated, using the approved outline and the final visual output.\n\n## Final speaker notes\n\nAfter the final images and HTML player are generated, write page-by-page speaker notes.\n\nSpeaker notes must:\n\n- sound like a real presenter, not a written report;\n- use clear, warm, direct language;\n- explain the point with concrete examples when useful;\n- refer naturally to what the audience can see on the generated page;\n- avoid over-polished slogans, dense jargon, and reading every slide label.\n\nFile v0.1.1:references/workflow.md\n\n# Workflow\n\nFollow this workflow exactly. Each stage ends with a user review question before moving to the next stage.\n\n## 1. Confirm requirements\n\nParse the user's request and collect missing key details:\n\n- topic and background;\n- presentation goal: what the audience should understand, believe, decide, or do;\n- audience: executives, customers, internal team, review panel, investors, or another group;\n- duration and approximate slide count;\n- information density: high, medium, or low;\n- preferred visual style or reference material;\n- source material, facts, data, cases, and constraints;\n- output language and tone;\n- whether to reserve a small LOGO area in the upper-left or upper-right corner, or no LOGO area;\n- any content that must not be invented.\n\nIf the user is unsure, recommend practical defaults:\n\n- duration: 10 minutes;\n- slide count: 8-12 pages;\n- information density: medium;\n- style: clean McKinsey-style consulting deck with restrained color, strong hierarchy, and chart-like logic.\n- LOGO area: no reserved LOGO area unless the user asks; if they want it, recommend a small upper-right area for corporate decks and upper-left for brand-led decks.\n\nThen summarize the brief, including the LOGO-space decision, and ask: \"以上需求和假设是否需要修改？确认后我会生成总纲和分页大纲。\"\n\n## 2. Research and outline\n\nUse the user's source material first. If internet research is requested or required for current facts, browse and cite sources in the final summary.\n\nCreate:\n\n- master outline: core answer, main logic chain, issue tree, and section flow;\n- page-by-page outline: one page per slide, with complete logic notes.\n\nAsk: \"这个总纲和分页大纲是否需要调整？确认后我会生成每页的 image-2 提示词。\"\n\n## 3. Expand outline content\n\nAfter the user approves the master outline and page-by-page outline, expand the content before prompt writing.\n\nFor each slide, produce:\n\n- expanded content: richer explanation of the page's message, evidence, implications, and examples;\n- example ideas: practical examples, analogies, or mini-scenarios that make the point concrete;\n- visual emphasis: what the generated image should make most obvious;\n- speaking hints: brief notes that may help final speaker-note writing later, but do not output the final talk track yet.\n\nDo not output the final speaker notes in this stage. Final notes must be written after image generation and HTML assembly, using the approved outline and the final generated images.\n\nAsk: \"拓展后的内容、例子和视觉重点是否需要调整？确认后我会先和你确认图片风格，再生成每页的 image-2 提示词。\"\n\n## 4. Confirm visual style\n\nBefore writing image-2 prompts, ask the user what visual style they want. Recommend options based on the context instead of using a fixed list.\n\nCommon options include:\n\n- 培训风：更亲和，结构清楚，适合课程、工作坊、内部分享；\n- 汇报风：更克制、专业、结论先行，适合管理层汇报和项目汇报；\n- 培训插画风：在清晰的咨询式结构中加入友好人物、课堂/工作场景、轻量叙事插画和统一笔触，适合课程、工作坊、内部分享；\n- 插画叙事风：用连续出现的角色、场景和视觉隐喻讲清问题变化，搭配少量结构化图形，适合传播、培训、文化和用户故事类主题；\n- 汇报插画风：保持结论先行和克制留白，用少量高质量场景插画解释复杂概念，适合管理层汇报中需要提升亲和力的主题；\n- 多图形：更多框架图、流程图、矩阵、图表，适合战略、经营、方案类主题；\n- 科技感：更适合 AI、数字化、产品技术主题；\n- 品牌简洁风：留白更多，适合客户沟通、品牌展示、对外路演。\n\nRecommend 2-4 options that fit the user's topic, audience, duration, and information density, then ask: \"你更倾向哪种图片风格？确认后我会把这个风格锁定到整套 image-2 提示词中。\"\n\n## 5. Write image-2 prompts\n\nBefore writing per-page prompts, define one deck-wide style lock. Apply it to every prompt.\n\nFor each slide, write one self-contained image-2 prompt that includes:\n\n- shared style lock;\n- single-slide 16:9 instruction;\n- LOGO-space instruction if the user requested one;\n- page logic;\n- expanded content and speaker-note intent where useful;\n- the thought and content this page should express, including recommended title, key messages, labels, and emphasis;\n- composition and visual structure;\n- negative constraints.\n\nAsk: \"这些 image-2 提示词是否需要修改？确认后我会批量生成 PPT 图片。\"\n\n## 6. Batch-generate images\n\nGenerate exactly one 16:9 image per slide with image-2.\n\nGeneration may take many minutes. When generating several pages in parallel or in a batch:\n\n- announce that the operation is long-running and that no immediate new preview does not mean generation failed;\n- keep the original generation task running and wait for its final return/completion signal;\n- monitor completed files or returned images without launching a second batch;\n- preserve already completed pages and report the current count when progress is available;\n- retry only after explicit failure, confirmed timeout, or confirmed missing/corrupt output after the task has ended.\n\nNever claim that a batch failed merely because it has been quiet for a while. Never start a duplicate batch while the original task may still be producing images.\n\nUse ordered filenames when files can be saved locally:\n\n```text\nimages/slide-01.png\nimages/slide-02.png\nimages/slide-03.png\n```\n\nIf local saving is not supported by the active image tool, explain the limitation and provide the generated previews or prompt set.\n\nThe ordered filename is for storage and HTML sequencing only. It must never be rendered inside the slide image. Do not put slide numbers, page numbers, sequence labels, numeric badges, or file names in the title, footer, corner, diagram, timeline, or any other visible area unless the user explicitly requires a number as part of the page content.\n\nDo not ask whether to create HTML. If local image files exist, proceed directly to HTML assembly.\n\n## 7. Automatically assemble playable HTML slideshow\n\nAfter generating local slide images, automatically:\n\n- create an output folder with `index.html` and `assets/`;\n- copy or reference the final slide images in order as `assets/slide-01.png`, `assets/slide-02.png`, etc.;\n- generate a full-viewport 16:9 player modeled after `C:\\project\\img-ppt\\ai-course-html\\index.html`;\n- include previous/next buttons, click zones, keyboard navigation, progress display, and fullscreen support;\n- keep each image inside a 16:9 frame with `object-fit: contain`;\n- do not alter the slide images while assembling the HTML.\n\nUse `scripts/generate-html-player.mjs` when local image files are available. If images are not local files, explain that HTML assembly requires local image files and ask the user to provide them.\n\n## 8. Write final speaker notes\n\nAfter final images and HTML are ready, write the final speaker notes page by page. Use:\n\n- the confirmed brief;\n- the master outline and page-by-page outline;\n- expanded content and examples;\n- the final generated slide images and what each image visually emphasizes.\n\nFor every slide, provide:\n\n- `pageNumber`;\n- `imagePath`;\n- `talkTrack`: an oral, natural, sincere, friendly script;\n- `exampleLines`: optional examples, analogies, or mini-scenarios that make the point concrete;\n- `transition`: a conversational bridge to the next page.\n\nSpeaker notes should sound like a person presenting to the target audience. Use short sentences, warm phrasing, and concrete examples. Avoid report-style prose, slogans, stiff corporate language, and reading every visible word on the slide.\n\nAsk at the end: \"已生成图片、HTML 播放器和逐页讲稿。是否有页面、HTML 播放效果或讲稿需要调整？\"\n\n## Revision handling\n\n- Requirement edits require revising the outline, prompts, and images.\n- Outline edits require revising affected expanded content, prompts, images, HTML, and final speaker notes.\n- Final speaker-note edits require revising prompts only if visible text, page logic, or visual emphasis changes.\n- Style edits require revising all prompts, images, HTML, and final speaker notes unless the user limits the change to specific pages.\n- Prompt edits require regenerating affected images.\n- Image feedback should be applied page by page when possible.\n- HTML output must be regenerated after any final image change.\n\nThis skill stops at PPT-style images, playable HTML, and final speaker notes. Do not assemble a PPTX.\n\nFile v0.1.1:skill-card.md\n\n## Description: <br>\nImage PPT Maker guides agents through a review-gated workflow to create PPT-style slide images, McKinsey-style outlines, image-2 prompts, a 16:9 HTML slideshow, and oral speaker notes without assembling PPTX files. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[callmexhj](https://clawhub.ai/user/callmexhj) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEmployees, external presenters, and developers use this skill to plan presentation image sets, generate structured consulting-style outlines, produce image-2 prompts and slide images, assemble a local HTML slideshow, and write final speaker notes. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill creates local output folders, copies generated slide images, and writes an HTML player after images are ready. <br>\nMitigation: Choose or review the output directory in the agent workflow and run the skill only where those local file writes are expected. <br>\nRisk: The generated slides and speaker notes may contain incorrect, unapproved, or misleading presentation content if the brief or source constraints are wrong. <br>\nMitigation: Use the required review gates to confirm the brief, outline, expanded content, prompts, generated images, HTML player, and speaker notes before sharing them. <br>\nRisk: The workflow documentation includes an example Windows path for the HTML player style reference. <br>\nMitigation: Treat the path as an example only; do not treat it as a file the agent should access. <br>\n\n\n## Reference(s): <br>\n- [Image Ppt Maker on ClawHub](https://clawhub.ai/callmexhj/skills/image-ppt-maker) <br>\n- [Workflow](references/workflow.md) <br>\n- [McKinsey-Style Outline](references/mckinsey-outline.md) <br>\n- [Image-2 Prompt Rules](references/image-2-prompts.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, code, files, guidance] <br>\n**Output Format:** [Markdown guidance, image-generation prompts, generated slide image files, a local HTML slideshow, and speaker notes.] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Uses review gates before downstream work, expects one 16:9 image per slide, and requires local image files before assembling the HTML player.] <br>\n\n## Skill Version(s): <br>\n0.1.1 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nFile v0.1.1:agents/openai.yaml\n\ninterface:\r\n  display_name: \"PPT 图片生成\"\r\n  short_description: \"生成大纲、PPT 图片、HTML 播放器和最终讲稿\"\n  default_prompt: \"使用 $image-ppt-maker 帮我确认 PPT 需求和 LOGO 预留区域，生成麦肯锡式大纲，先确认图片风格，再生成统一风格的 image-2 提示词和 PPT 图片；图片完成后自动生成 16:9 HTML 播放器，并结合最终图片输出逐页口语化讲稿。\"\n\nArchive v0.1.0: 7 files, 14109 bytes\n\nFiles: references/image-2-prompts.md (4605b), references/mckinsey-outline.md (2768b), references/workflow.md (7182b), scripts/generate-html-player.mjs (8338b), skill-card.md (2550b), SKILL.md (5480b), _meta.json (134b)\n\nFile v0.1.0:SKILL.md\n\n---\nname: image-ppt-maker\ndescription: \"Create PPT-style images through a human-in-the-loop workflow: clarify presentation requirements including optional top-corner LOGO space, research and draft McKinsey-style master and page-by-page outlines, expand page content, confirm the desired visual style before image prompts, write unified-style image-2 prompts, batch-generate 16:9 slide images, automatically assemble the images into a playable 16:9 HTML slideshow, and finally write oral speaker notes based on the outline and final images. Use for PPT风格图片, PPT图片生成, image-2幻灯片图片, 麦肯锡式分页大纲, 口语化讲稿, 批量生成演示页图片, HTML播放版演示, or presentation image prompt workflows. This skill does not assemble PPTX files.\"\n---\n\n# Image PPT Maker\n\nHelp users create a set of PPT-style slide images with image-2. Use a strict review-gated workflow:\n\n1. Confirm requirements.\n2. Build a McKinsey-style master outline and page-by-page outline.\n3. Expand the outline content.\n4. Confirm the desired visual style for the images.\n5. Write unified-style image-2 prompts.\n6. Batch-generate 16:9 PPT images.\n7. Automatically assemble the generated images into a playable 16:9 HTML slideshow.\n8. Write final oral speaker notes based on the approved outline and final images.\n\nAsk the user whether they want changes at each review gate. Do not ask before HTML assembly; generate the HTML player automatically after final images are available.\n\n## Required References\n\n- Read [workflow.md](references/workflow.md) before starting any task.\n- Read [mckinsey-outline.md](references/mckinsey-outline.md) before drafting or revising outlines.\n- Read [image-2-prompts.md](references/image-2-prompts.md) before writing prompts or generating images.\n- Use [generate-html-player.mjs](scripts/generate-html-player.mjs) only when the user asks for a playable HTML output after images exist.\n\n## Core Rules\n\n1. Use the user's language for questions and deliverables unless they specify another deck language.\n2. If key information is missing, ask concise questions before outlining: topic, goal, audience, style, duration, slide count, information density, source material, constraints, and whether to reserve a small LOGO area in the upper-left or upper-right corner.\n3. Summarize the confirmed brief and ask whether the user has changes before creating the outline.\n4. Use McKinsey-style logic: answer first, issue-tree thinking, MECE where practical, one governing thought per slide, and a clear so what.\n5. Every page in the outline must include logic notes. Do not create title-only or decorative pages.\n6. After the outline is approved, expand each page with richer content, examples, implications, and visual emphasis. Do not output speaker notes yet.\n7. Before writing image prompts, ask the user what visual style they prefer and recommend context-aware options such as training style, executive report style, illustration-heavy, graphic/chart-heavy, product demo style, or other suitable options.\n8. Generate one image per slide, 16:9, with image-2. Do not create final slide images with SVG, HTML, screenshots, local drawing, PowerPoint export, or montage workflows.\n9. After image generation, automatically generate a playable 16:9 HTML slideshow from the final images when local image files exist.\n10. After HTML assembly, write final per-slide speaker notes based on the approved outline and the generated images. The notes must sound oral, natural, sincere, friendly, and example-driven.\n11. This skill does not assemble PPTX files. Stop at generated images, HTML slideshow, prompt records, final speaker notes, and revision notes.\n12. Preserve approved work during revisions. Only regenerate the affected downstream artifacts.\n\n## Workflow Gates\n\nDo not skip these review points:\n\n- After requirement parsing: ask whether the brief and assumptions need changes.\n- After the master outline and page-by-page outline: ask whether the storyline, page count, or logic needs changes.\n- After the expanded outline content: ask whether the content depth, examples, or emphasis needs changes.\n- Before writing image-2 prompts: ask which visual style the user prefers, offering context-aware recommendations.\n- After image-2 prompts: ask whether the style, visible text, or page prompts need changes.\n- After HTML assembly and final speaker notes: ask whether any page, HTML output, or speaker note should be adjusted.\n\nIf the user requests changes:\n\n- Requirement changes invalidate outline, prompts, and images.\n- Outline changes invalidate affected expanded content, prompts, images, HTML, and final speaker notes.\n- Visual-style changes invalidate prompts, images, HTML, and final speaker notes.\n- Final speaker-note changes do not invalidate prompts, images, or HTML unless the visible slide content or logic changes.\n- Prompt or style changes invalidate the affected images.\n- Image issues require regenerating only the affected pages when possible.\n- HTML output must be regenerated if final image filenames, image count, title, or image folder changes.\n\n## Deliverables\n\nWhen complete, provide:\n\n- confirmed brief;\n- master outline and page-by-page outline;\n- expanded outline content;\n- image-2 prompt set with the shared style lock;\n- generated image paths or previews;\n- playable 16:9 HTML slideshow path;\n- final oral speaker notes based on the outline and generated images;\n- concise notes on pages that may need regeneration.\n\nFile v0.1.0:_meta.json\n\n{\n  \"ownerId\": \"kn7dddd3v8yk96jx32p2gsmnvh8a03gt\",\n  \"slug\": \"image-ppt-maker\",\n  \"version\": \"0.1.0\",\n  \"publishedAt\": 1783591641055\n}\n\nFile v0.1.0:references/image-2-prompts.md\n\n# Image-2 Prompt Rules\n\nWrite prompts for image-2. Each prompt must generate exactly one 16:9 PPT-style slide image.\n\n## Deck-wide style lock\n\nDefine one shared style lock before per-page prompts. It must specify:\n\n- aspect ratio: 16:9;\n- deck type: professional consulting-style PPT page;\n- layout system: title area, content grid, margins, chart/table/card treatment;\n- palette: primary, secondary, background, accent colors;\n- typography: clear hierarchy, readable slide text, no decorative fonts;\n- visual language: charts, diagrams, icons, photography, or abstract business visuals;\n- density: high, medium, or low;\n- optional LOGO space: no reserved area, upper-left reserved area, or upper-right reserved area;\n- consistency rule: every page must look like part of the same deck.\n\nRepeat the complete style lock inside every page prompt, but mark it as non-visible generation guidance. The style lock must influence layout and visual treatment only; image-2 must not render the style-lock wording as text on the slide.\n\n## Per-page prompt structure\n\nEach page prompt must include:\n\n1. `Model`: image-2.\n2. `Task`: generate only this single 16:9 PPT slide image.\n3. `Style lock`: copy the shared deck-wide style lock.\n4. `Style text handling`: state that style descriptions are instructions only and must not appear as visible text.\n5. `Slide logic`: key question, governing thought, supporting logic, so what, transition.\n6. `Expanded content`: the richer explanation or examples that should guide the visual emphasis.\n7. `LOGO space`: if requested, reserve a small clear area in the chosen top corner; do not invent or render a logo unless the user provided one.\n8. `Page message and content`: explain the thought this page should express, the core content to show, and the recommended title, key messages, labels, and emphasis.\n9. `Composition`: layout, visual hierarchy, chart or diagram structure, spacing, alignment.\n10. `Readability`: clean typography, enough contrast, no tiny unreadable text.\n11. `Constraints`: factual constraints and source-material limits.\n12. `Negative constraints`: forbidden outputs.\n\n## Page message and content\n\nDo not constrain the slide by enumerating every allowed visible word. Instead, describe the page's intended communication clearly enough for image-2 to design the slide:\n\n- State the page's governing thought in an answer-first way.\n- Explain the core content the slide should communicate, including the most important evidence, comparison, process, framework, or recommendation.\n- Suggest the title, short labels, callouts, and chart/table labels that would help express the idea, but keep text concise and slide-like.\n- Preserve McKinsey-style communication: structured, logical, executive-readable, and focused on one message per page.\n- Do not render prompt section labels or internal reasoning labels such as \"Style lock\", \"Slide logic\", \"Expanded content\", \"Page message and content\", \"McKinsey-style\", \"16:9\", \"professional consulting-style\", or \"image-2\".\n- If a style concept needs to show visually, express it through layout, color, spacing, chart treatment, and imagery, not through written words.\n- If a LOGO area is reserved, it is a blank layout area unless the user supplies a logo. Do not render placeholder text such as \"LOGO\".\n\nAdd this sentence to every prompt:\n\n```text\nRender concise slide text that supports the page message; all style descriptions, prompt section labels, and generation instructions are non-visible guidance and must not appear as words in the slide image.\n```\n\n## Negative constraints\n\nAlways forbid:\n\n- multiple slides in one image;\n- montage, contact sheet, overview, collage, or thumbnail grid;\n- browser screenshot, app screenshot, chat screenshot, or document screenshot;\n- long paragraphs, dense report prose, or text that does not support the page's governing thought;\n- any visible wording copied from style descriptions, prompt section labels, or generation instructions;\n- meta words such as style lock, deck-wide style, 16:9, image-2, prompt, McKinsey-style, typography, palette, layout system, consulting-style, Page message and content, or LOGO;\n- watermark, signature, logo, model mark, or random brand mark;\n- random icons, people, company names, or data not provided or approved;\n- SVG, HTML, wireframe, or code-like rendering.\n\n## Batch output\n\nGenerate one image per approved prompt. Use ordered names when saving files:\n\n```text\nimages/slide-01.png\nimages/slide-02.png\nimages/slide-03.png\n```\n\nIf a page fails visually, revise or regenerate that page only unless the style lock itself changed.\n\nFile v0.1.0:references/mckinsey-outline.md\n\n# McKinsey-Style Outline\n\nUse this structure for the master outline and every page outline.\n\n## Principles\n\n- Answer first: lead with the conclusion or recommendation.\n- Pyramid structure: conclusion, reasons, evidence.\n- Issue tree: split the topic into a small number of logical questions.\n- MECE where practical: reduce overlap and gaps.\n- One slide, one message: each page has one governing thought.\n- So what: every page explains why the point matters to the audience.\n\n## Master outline format\n\nInclude:\n\n- `coreAnswer`: the answer-first conclusion of the whole deck;\n- `audienceDecision`: what the audience should decide or do;\n- `logicChain`: 3-5 major reasoning steps;\n- `sections`: major sections with the question each section answers;\n- `storyFlow`: why the sequence is persuasive.\n\n## Page-by-page outline format\n\nFor each page, include:\n\n- `pageNumber`;\n- `title`: conclusion-style title, not a topic label;\n- `keyQuestion`: the question this page answers;\n- `governingThought`: the page's answer-first message;\n- `supportingLogic`: 2-4 reasons, evidence points, or observations;\n- `visualIdea`: the visual structure that best supports the logic;\n- `soWhat`: why the audience should care;\n- `transition`: why the next page follows.\n\n## Visual logic mapping\n\n- Compare options: side-by-side comparison.\n- Explain drivers: driver tree, layered model, or waterfall.\n- Show sequence: timeline, roadmap, or process.\n- Prioritize: matrix, ranking, or funnel.\n- Recommend action: chosen path plus reasons.\n- Summarize system: architecture, operating model, or flywheel.\n\nDo not use decorative visuals that fail to carry the logic.\n\n## Expanded outline content\n\nAfter the page-by-page outline is approved, expand each page before writing image prompts.\n\nFor each page, include:\n\n- `expandedContent`: 1-3 short paragraphs that deepen the page logic with evidence, implications, and examples;\n- `exampleIdeas`: 2-4 concrete examples, analogies, or mini-scenarios that make the point easier to understand;\n- `visualEmphasis`: what the generated image should make most obvious;\n- `speakerNoteHints`: brief reminders for final speaker-note writing after images are generated.\n\nDo not write the final speaker notes at this stage. Final notes must be written after images are generated, using the approved outline and the final visual output.\n\n## Final speaker notes\n\nAfter the final images and HTML player are generated, write page-by-page speaker notes.\n\nSpeaker notes must:\n\n- sound like a real presenter, not a written report;\n- use clear, warm, direct language;\n- explain the point with concrete examples when useful;\n- refer naturally to what the audience can see on the generated page;\n- avoid over-polished slogans, dense jargon, and reading every slide label.\n\nFile v0.1.0:references/workflow.md\n\n# Workflow\n\nFollow this workflow exactly. Each stage ends with a user review question before moving to the next stage.\n\n## 1. Confirm requirements\n\nParse the user's request and collect missing key details:\n\n- topic and background;\n- presentation goal: what the audience should understand, believe, decide, or do;\n- audience: executives, customers, internal team, review panel, investors, or another group;\n- duration and approximate slide count;\n- information density: high, medium, or low;\n- preferred visual style or reference material;\n- source material, facts, data, cases, and constraints;\n- output language and tone;\n- whether to reserve a small LOGO area in the upper-left or upper-right corner, or no LOGO area;\n- any content that must not be invented.\n\nIf the user is unsure, recommend practical defaults:\n\n- duration: 10 minutes;\n- slide count: 8-12 pages;\n- information density: medium;\n- style: clean McKinsey-style consulting deck with restrained color, strong hierarchy, and chart-like logic.\n- LOGO area: no reserved LOGO area unless the user asks; if they want it, recommend a small upper-right area for corporate decks and upper-left for brand-led decks.\n\nThen summarize the brief, including the LOGO-space decision, and ask: \"以上需求和假设是否需要修改？确认后我会生成总纲和分页大纲。\"\n\n## 2. Research and outline\n\nUse the user's source material first. If internet research is requested or required for current facts, browse and cite sources in the final summary.\n\nCreate:\n\n- master outline: core answer, main logic chain, issue tree, and section flow;\n- page-by-page outline: one page per slide, with complete logic notes.\n\nAsk: \"这个总纲和分页大纲是否需要调整？确认后我会生成每页的 image-2 提示词。\"\n\n## 3. Expand outline content\n\nAfter the user approves the master outline and page-by-page outline, expand the content before prompt writing.\n\nFor each slide, produce:\n\n- expanded content: richer explanation of the page's message, evidence, implications, and examples;\n- example ideas: practical examples, analogies, or mini-scenarios that make the point concrete;\n- visual emphasis: what the generated image should make most obvious;\n- speaking hints: brief notes that may help final speaker-note writing later, but do not output the final talk track yet.\n\nDo not output the final speaker notes in this stage. Final notes must be written after image generation and HTML assembly, using the approved outline and the final generated images.\n\nAsk: \"拓展后的内容、例子和视觉重点是否需要调整？确认后我会先和你确认图片风格，再生成每页的 image-2 提示词。\"\n\n## 4. Confirm visual style\n\nBefore writing image-2 prompts, ask the user what visual style they want. Recommend options based on the context instead of using a fixed list.\n\nCommon options include:\n\n- 培训风：更亲和，结构清楚，适合课程、工作坊、内部分享；\n- 汇报风：更克制、专业、结论先行，适合管理层汇报和项目汇报；\n- 多插画：画面更有故事性和亲和力，适合传播、培训、文化类主题；\n- 多图形：更多框架图、流程图、矩阵、图表，适合战略、经营、方案类主题；\n- 科技感：更适合 AI、数字化、产品技术主题；\n- 品牌简洁风：留白更多，适合客户沟通、品牌展示、对外路演。\n\nRecommend 2-4 options that fit the user's topic, audience, duration, and information density, then ask: \"你更倾向哪种图片风格？确认后我会把这个风格锁定到整套 image-2 提示词中。\"\n\n## 5. Write image-2 prompts\n\nBefore writing per-page prompts, define one deck-wide style lock. Apply it to every prompt.\n\nFor each slide, write one self-contained image-2 prompt that includes:\n\n- shared style lock;\n- single-slide 16:9 instruction;\n- LOGO-space instruction if the user requested one;\n- page logic;\n- expanded content and speaker-note intent where useful;\n- the thought and content this page should express, including recommended title, key messages, labels, and emphasis;\n- composition and visual structure;\n- negative constraints.\n\nAsk: \"这些 image-2 提示词是否需要修改？确认后我会批量生成 PPT 图片。\"\n\n## 6. Batch-generate images\n\nGenerate exactly one 16:9 image per slide with image-2.\n\nUse ordered filenames when files can be saved locally:\n\n```text\nimages/slide-01.png\nimages/slide-02.png\nimages/slide-03.png\n```\n\nIf local saving is not supported by the active image tool, explain the limitation and provide the generated previews or prompt set.\n\nDo not ask whether to create HTML. If local image files exist, proceed directly to HTML assembly.\n\n## 7. Automatically assemble playable HTML slideshow\n\nAfter generating local slide images, automatically:\n\n- create an output folder with `index.html` and `assets/`;\n- copy or reference the final slide images in order as `assets/slide-01.png`, `assets/slide-02.png`, etc.;\n- generate a full-viewport 16:9 player modeled after `C:\\project\\img-ppt\\ai-course-html\\index.html`;\n- include previous/next buttons, click zones, keyboard navigation, progress display, and fullscreen support;\n- keep each image inside a 16:9 frame with `object-fit: contain`;\n- do not alter the slide images while assembling the HTML.\n\nUse `scripts/generate-html-player.mjs` when local image files are available. If images are not local files, explain that HTML assembly requires local image files and ask the user to provide them.\n\n## 8. Write final speaker notes\n\nAfter final images and HTML are ready, write the final speaker notes page by page. Use:\n\n- the confirmed brief;\n- the master outline and page-by-page outline;\n- expanded content and examples;\n- the final generated slide images and what each image visually emphasizes.\n\nFor every slide, provide:\n\n- `pageNumber`;\n- `imagePath`;\n- `talkTrack`: an oral, natural, sincere, friendly script;\n- `exampleLines`: optional examples, analogies, or mini-scenarios that make the point concrete;\n- `transition`: a conversational bridge to the next page.\n\nSpeaker notes should sound like a person presenting to the target audience. Use short sentences, warm phrasing, and concrete examples. Avoid report-style prose, slogans, stiff corporate language, and reading every visible word on the slide.\n\nAsk at the end: \"已生成图片、HTML 播放器和逐页讲稿。是否有页面、HTML 播放效果或讲稿需要调整？\"\n\n## Revision handling\n\n- Requirement edits require revising the outline, prompts, and images.\n- Outline edits require revising affected expanded content, prompts, images, HTML, and final speaker notes.\n- Final speaker-note edits require revising prompts only if visible text, page logic, or visual emphasis changes.\n- Style edits require revising all prompts, images, HTML, and final speaker notes unless the user limits the change to specific pages.\n- Prompt edits require regenerating affected images.\n- Image feedback should be applied page by page when possible.\n- HTML output must be regenerated after any final image change.\n\nThis skill stops at PPT-style images, playable HTML, and final speaker notes. Do not assemble a PPTX.\n\nFile v0.1.0:skill-card.md\n\n## Description: <br>\nCreates PPT-style slide images through a review-gated workflow that clarifies requirements, drafts McKinsey-style outlines, writes unified image-2 prompts, generates 16:9 slide images, assembles a local HTML slideshow, and writes speaker notes without assembling PPTX files. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[callmexhj](https://clawhub.ai/user/callmexhj) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEmployees, external users, and developers can use this skill to turn presentation requirements and source material into consulting-style slide images, prompt sets, a local HTML viewer, and oral speaker notes. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may create a local HTML slideshow folder after images are generated without a separate final confirmation. <br>\nMitigation: Review or specify the output path before image generation, and inspect the generated HTML folder and copied slide assets after assembly. <br>\nRisk: Generated slide images and speaker notes can carry unsupported or inaccurate claims if the source material is incomplete. <br>\nMitigation: Use the built-in review gates to confirm requirements, outline logic, expanded content, prompts, and final pages; regenerate affected slides when issues are found. <br>\n\n\n## Reference(s): <br>\n- [Workflow](references/workflow.md) <br>\n- [McKinsey-Style Outline](references/mckinsey-outline.md) <br>\n- [Image-2 Prompt Rules](references/image-2-prompts.md) <br>\n- [ClawHub Skill Page](https://clawhub.ai/callmexhj/skills/image-ppt-maker) <br>\n- [Server-Resolved Source Repository](https://github.com/callmexhj/image-ppt-maker) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, code, shell commands, guidance, files] <br>\n**Output Format:** [Markdown guidance with image prompts, generated image files, a local HTML slideshow, and speaker notes] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Creates one 16:9 slide image per approved prompt and may write an HTML slideshow when local image files exist.] <br>\n\n## Skill Version(s): <br>\n0.1.0 (source: server release metadata and auto changelog) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>","readmeExcerpt":"Skill: PPT 图片生成 Owner: callmexhj Summary: Turns presentation ideas into McKinsey-style outlines, consistent 16:9 slide images, a playable HTML deck, and duration-aware speaker scripts. Supports staged content review, visual style guidance, optional logo space, batch generation, and structured single-slide revisions. Tags: latest:0.1.3 Version history: v0.1.3 | 2026-07-15T09:58:06.377Z | user - Removes the redundant s","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"Render concise slide text that supports the page message; all style descriptions, prompt section labels, and generation instructions are non-visible guidance and must not appear as words in the slide image."},{"language":"text","snippet":"images/slide-01.png\nimages/slide-02.png\nimages/slide-03.png"},{"language":"text","snippet":"images/slide-01.png\nimages/slide-02.png\nimages/slide-03.png"},{"language":"text","snippet":"Render concise slide text that supports the page message; all style descriptions, prompt section labels, and generation instructions are non-visible guidance and must not appear as words in the slide image."},{"language":"text","snippet":"images/slide-01.png\nimages/slide-02.png\nimages/slide-03.png"},{"language":"text","snippet":"images/slide-01.png\nimages/slide-02.png\nimages/slide-03.png"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: image-ppt-maker\ndescription: \"Create PPT-style images through a human-in-the-loop workflow: clarify presentation requirements including optional top-corner LOGO space, research and draft McKinsey-style master and page-by-page outlines, expand page content, confirm the desired visual style before image prompts, write unified-style image-2 prompts, batch-generate 16:9 slide images, automatically assemble the images into a playable 16:9 HTML slideshow, and finally write oral speaker notes based on the outline and final images. Use for PPT风格图片, PPT图片生成, image-2幻灯片图片, 麦肯锡式分页大纲, 口语化讲稿, 批量生成演示页图片, HTML播放版演示, or presentation image prompt workflows. This skill does not assemble PPTX files.\"\n---\n\n# Image PPT Maker\n\nHelp users create a set of PPT-style slide images with image-2. Use a strict review-gated workflow:\n\n1. Confirm requirements.\n2. Build a McKinsey-style master outline and page-by-page outline.\n3. Expand the outline content.\n4. Confirm the desired visual style for the images.\n5. Write unified-style image-2 prompts.\n6. Batch-generate 16:9 PPT images.\n7. Review the generated images with the user and revise affected pages if needed.\n8. Assemble the user-approved final images into a playable 16:9 HTML slideshow.\n9. Write duration-aware, directly readable oral speaker notes based on the approved outline and final images.\n\nAsk the user whether they want changes only at the review gates listed below. Image prompts are internal execution artifacts, not a review gate. Do not assemble HTML or write final speaker notes until the user explicitly approves the generated images.\n\n## Required References\n\n- Read [workflow.md](references/workflow.md) before starting any task.\n- Read [mckinsey-outline.md](references/mckinsey-outline.md) before drafting or revising outlines.\n- Read [image-2-prompts.md](references/image-2-prompts.md) before writing prompts or generating images.\n- Use [generate-html-player.mjs](scripts/generate-html-player.mjs) only after the user approves final local images for a playable HTML output.\n\n## Core Rules\n\n1. Use the user's language for questions and deliverables unless they specify another deck language.\n2. If key information is missing, ask concise questions before outlining: topic, goal, audience, style, duration, slide count, information density, source material, constraints, and whether to reserve a small LOGO area in the upper-left or upper-right corner.\n3. Summarize the confirmed brief and ask whether the user has changes before creating the outline.\n4. Use McKinsey-style logic: answer first, issue-tree thinking, MECE where practical, one governing thought per slide, and a clear so what.\n5. Every page in the outline must include logic notes. Do not create title-only or decorative pages.\n6. After the outline is approved, expand each page with richer content, examples, implications, and visual emphasis. Do not output speaker notes yet.\n7. Before writing image prompts, ask the user what visual style they prefer and recommend "},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn7dddd3v8yk96jx32p2gsmnvh8a03gt\",\n  \"slug\": \"image-ppt-maker\",\n  \"version\": \"0.1.3\",\n  \"publishedAt\": 1784109486377\n}"},{"path":"references/image-2-prompts.md","content":"# Image-2 Prompt Rules\n\nWrite prompts for image-2. Each prompt must generate exactly one 16:9 PPT-style slide image.\n\nTreat prompts as internal execution artifacts. Do not ask the user to review or approve prompts. Generate them after content and style approval, then proceed directly to image generation.\n\n## Deck-wide style lock\n\nDefine one shared style lock before per-page prompts. It must specify:\n\n- aspect ratio: 16:9;\n- deck type: professional consulting-style PPT page;\n- layout system: title area, content grid, margins, chart/table/card treatment;\n- palette: primary, secondary, background, accent colors;\n- typography: clear hierarchy, readable slide text, no decorative fonts;\n- visual language: charts, diagrams, icons, photography, or abstract business visuals;\n- density: high, medium, or low;\n- optional LOGO space: no reserved area, upper-left reserved area, or upper-right reserved area;\n- consistency rule: every page must look like part of the same deck.\n\nRepeat the complete style lock inside every page prompt, but mark it as non-visible generation guidance. The style lock must influence layout and visual treatment only; image-2 must not render the style-lock wording as text on the slide.\n\n## Per-page prompt structure\n\nEach page prompt must include:\n\n1. `Model`: image-2.\n2. `Task`: generate only this single 16:9 PPT slide image.\n3. `Style lock`: copy the shared deck-wide style lock.\n4. `Style text handling`: state that style descriptions are instructions only and must not appear as visible text.\n5. `Slide logic`: key question, governing thought, supporting logic, so what, transition.\n6. `Expanded content`: the richer explanation or examples that should guide the visual emphasis.\n7. `LOGO space`: if requested, reserve a small clear area in the chosen top corner; do not invent or render a logo unless the user provided one.\n8. `Page message and content`: explain the thought this page should express, the core content to show, and the recommended title, key messages, labels, and emphasis.\n9. `Composition`: layout, visual hierarchy, chart or diagram structure, spacing, alignment.\n10. `Readability`: clean typography, enough contrast, no tiny unreadable text.\n11. `Constraints`: factual constraints and source-material limits.\n12. `Negative constraints`: forbidden outputs.\n\n## Page message and content\n\nDo not constrain the slide by enumerating every allowed visible word. Instead, describe the page's intended communication clearly enough for image-2 to design the slide:\n\n- State the page's governing thought in an answer-first way.\n- Explain the core content the slide should communicate, including the most important evidence, comparison, process, framework, or recommendation.\n- Suggest the title, short labels, callouts, and chart/table labels that would help express the idea, but keep text concise and slide-like.\n- Preserve McKinsey-style communication: structured, logical, executive-readable, and focused on one message per page.\n- Do not render promp"},{"path":"references/mckinsey-outline.md","content":"# McKinsey-Style Outline\n\nUse this structure for the master outline and every page outline.\n\n## Principles\n\n- Answer first: lead with the conclusion or recommendation.\n- Pyramid structure: conclusion, reasons, evidence.\n- Issue tree: split the topic into a small number of logical questions.\n- MECE where practical: reduce overlap and gaps.\n- One slide, one message: each page has one governing thought.\n- So what: every page explains why the point matters to the audience.\n\n## Master outline format\n\nInclude:\n\n- `coreAnswer`: the answer-first conclusion of the whole deck;\n- `audienceDecision`: what the audience should decide or do;\n- `logicChain`: 3-5 major reasoning steps;\n- `sections`: major sections with the question each section answers;\n- `storyFlow`: why the sequence is persuasive.\n\n## Page-by-page outline format\n\nFor each page, include:\n\n- `pageNumber`;\n- `title`: conclusion-style title, not a topic label;\n- `keyQuestion`: the question this page answers;\n- `governingThought`: the page's answer-first message;\n- `supportingLogic`: 2-4 reasons, evidence points, or observations;\n- `visualIdea`: the visual structure that best supports the logic;\n- `soWhat`: why the audience should care;\n- `transition`: why the next page follows.\n\n## Visual logic mapping\n\n- Compare options: side-by-side comparison.\n- Explain drivers: driver tree, layered model, or waterfall.\n- Show sequence: timeline, roadmap, or process.\n- Prioritize: matrix, ranking, or funnel.\n- Recommend action: chosen path plus reasons.\n- Summarize system: architecture, operating model, or flywheel.\n\nDo not use decorative visuals that fail to carry the logic.\n\n## Expanded outline content\n\nAfter the page-by-page outline is approved, expand each page before writing image prompts.\n\nFor each page, include:\n\n- `expandedContent`: 1-3 short paragraphs that deepen the page logic with evidence, implications, and examples;\n- `exampleIdeas`: 2-4 concrete examples, analogies, or mini-scenarios that make the point easier to understand;\n- `visualEmphasis`: what the generated image should make most obvious;\n- `speakerNoteHints`: brief reminders for final speaker-note writing after images are generated.\n\nDo not write the final speaker notes at this stage. Final notes must be written after images are generated, using the approved outline and the final visual output.\n\n## Single-page revisions\n\nFor every later single-page change, recreate the affected page using the same page-by-page outline and expanded-content fields above. Preserve the approved deck-wide storyline and style, but reconsider the page's governing thought, support, so what, transition, examples, visual emphasis, and speaking-time allocation in light of the new request.\n\nPresent the consolidated revised page content for user approval before generating the replacement image. Do not treat raw image feedback as sufficient approval to regenerate.\n\n## Final speaker notes\n\nAfter the final images and HTML player are generated, write page-by-page speaker no"},{"path":"references/workflow.md","content":"# Workflow\n\nFollow this workflow exactly. Pause only at the designated review gates. Image-prompt creation is not a review gate.\n\n## 1. Confirm requirements\n\nParse the user's request and collect missing key details:\n\n- topic and background;\n- presentation goal: what the audience should understand, believe, decide, or do;\n- audience: executives, customers, internal team, review panel, investors, or another group;\n- duration and approximate slide count; use the duration as the total speaking-time budget for the final script;\n- information density: high, medium, or low;\n- preferred visual style or reference material;\n- source material, facts, data, cases, and constraints;\n- output language and tone;\n- whether to reserve a small LOGO area in the upper-left or upper-right corner, or no LOGO area;\n- any content that must not be invented.\n\nIf the user is unsure, recommend practical defaults:\n\n- duration: 10 minutes;\n- slide count: 8-12 pages;\n- information density: medium;\n- style: clean McKinsey-style consulting deck with restrained color, strong hierarchy, and chart-like logic.\n- LOGO area: no reserved LOGO area unless the user asks; if they want it, recommend a small upper-right area for corporate decks and upper-left for brand-led decks.\n\nThen summarize the brief, including the LOGO-space decision, and ask: \"以上需求和假设是否需要修改？确认后我会生成总纲和分页大纲。\"\n\n## 2. Research and outline\n\nUse the user's source material first. If internet research is requested or required for current facts, browse and cite sources in the final summary.\n\nCreate:\n\n- master outline: core answer, main logic chain, issue tree, and section flow;\n- page-by-page outline: one page per slide, with complete logic notes and a suggested speaking-time allocation. Allocate the total speaking time across pages according to message importance and complexity; keep the sum aligned with the confirmed duration.\n\nAsk: \"这个总纲和分页大纲是否需要调整？确认后我会拓展每页内容。\"\n\n## 3. Expand outline content\n\nAfter the user approves the master outline and page-by-page outline, expand the content before prompt writing.\n\nFor each slide, produce:\n\n- expanded content: richer explanation of the page's message, evidence, implications, and examples;\n- example ideas: practical examples, analogies, or mini-scenarios that make the point concrete;\n- visual emphasis: what the generated image should make most obvious;\n- speaking hints: brief notes that may help final speaker-note writing later, but do not output the final talk track yet.\n\nDo not output the final speaker notes in this stage. Final notes must be written after image generation and HTML assembly, using the approved outline and the final generated images.\n\nAsk: \"拓展后的内容、例子和视觉重点是否需要调整？确认后我会先和你确认图片风格，再生成每页的 image-2 提示词。\"\n\n## 4. Confirm visual style\n\nBefore writing image-2 prompts, ask the user what visual style they want. Recommend options based on the context instead of using a fixed list.\n\nCommon options include:\n\n- 培训风：更亲和，结构清楚，适合课程、工作坊、内部分享；\n- 汇报风：更克制、专业、结论先行，适合管理层汇报和项目汇报；\n- 培训插画风：在清晰的咨询式结构"}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":null,"editorialQuality":{"score":100,"threshold":65,"status":"thin","wordCount":2418,"uniquenessScore":35,"reasons":["uniqueness-below-45"]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-10T19:10:19.237Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-10T19:10:19.237Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-10T21:43:44.060Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}