Preface¶

When preparing presentations or proposals, the common path is to pile materials into a document, manually apply templates, adjust layouts, and export to PPT. While Agents can write outlines and copy, directly modifying the PPTX structure often leads to pitfalls regarding layout, theme consistency, and export quality. Here we introduce api_maker2 (Coordinate @user_7e25a48a/api-maker) on SkillHub: it turns the process of “Research Aggregation → Single-page HTML → Export to .pptx” into a fixed pipeline, covering both zero-to-one generation and incremental editing tasks.

What is this¶

api_maker2 is a community-sourced (community) Agent Skill, currently at version 1.0.1. It is categorized under office-efficiency and published by user_7e25a48a (labeled as author “yazi测试账号” on the SkillHub page). The official description states: Generate professional PowerPoint presentations locally; this Skill should be triggered when users need to create PPTs, slides, decks, Keynote-style presentations, reports, or proposal materials, or when they need to modify single pages, change theme colors, add/delete pages, or export .pptx files. The tag requires_api_key=false indicates it does not rely on external API Keys.

SkillHub Page: https://www.skillhub.cn/skills/user_7e25a48a/api-maker
API Entry (Installation package download, etc.): https://api.skillhub.cn/user_7e25a48a/api-maker

Core Features¶

The following capabilities are derived from SKILL.md within the Skill package and SkillHub search results, and can be verified in the same manner.

Three-stage Pipeline: research.md (unified content layer) → Independent HTML for each page (1280×720, Tailwind CSS + Lucide icons) → Export .pptx via dist/export-pptx.mjs.
State File presentation.json: Records title, theme, and the type / title / content_spec and file mapping for each page; this file acts as the single source of truth for adding, deleting, or modifying pages. HTML filenames are not renamed after creation.
Complete Generation Flow: Collect requirements → Write research.md (Web research / Organize user materials / AI organization) → Plan outline → Blocking Point: Show outline to user and wait for confirmation → Initialize project → Generate HTML for each page in serial or parallel mode → Icon validation → Export.
Incremental Editing: Operations such as changing copy, styles, themes, or adding/deleting pages follow the “minimal change” principle; after modification, sync content_spec, re-run icon validation, and export again.
Helper Scripts: scripts/validate-icons.mjs corrects invalid Lucide icon names; scripts/check-fonts.sh checks or installs fonts; Export relies on Playwright headless Chromium and must be executed in a non-sandboxed environment.

Installation and Enablement¶

Before installation, ensure the skillhub CLI is available. If not installed, follow the official SkillHub instructions:

command -v skillhub && skillhub --version

curl -fsSL https://skillhub-1388575217.cos.ap-guangzhou.myqcloud.com/install/install.sh | bash

When installing api_maker2, you must use --dir to point to the current Agent’s skills directory; otherwise, it defaults to ./skills/ and may not be recognized. The command provided by SkillHub search is:

skillhub install api-maker --namespace user_7e25a48a --dir <your skills directory>

Common paths (excerpted from SkillHub installation docs):

Cursor: ~/.cursor/skills/
Claude Code: ~/.claude/skills/
Codex: ~/.codex/skills/ or .agents/skills/ under the project

You can also ask the Agent to install the coordinate @user_7e25a48a/api-maker via https://skillhub.cn/install/skillhub.md.

Once enabled, the Agent reads SKILL.md in the Skill directory to execute the workflow contained within; SKILL_DIR refers to the directory where this SKILL.md resides.

Typical Usage¶

The steps below correspond to the “Core Workflow” and export sections within the Skill for easy reproduction.

1. Prepare the trio in the project directory

<project_dir>/
├── research.md
├── presentation.json
└── slides/
    ├── slide_001.html
    └── ...

Example structure of presentation.json (see Skill docs for field meanings):

{
  "title": "Presentation Title",
  "theme": "Natural-language style description",
  "slides": [
    {
      "file": "slide_001.html",
      "type": "title",
      "title": "Slide Title",
      "content_spec": "Key points and structural description for this page (do not hardcode copy)"
    }
  ]
}

2. Validate icons after generating HTML

Replace SKILL_DIR with the api-maker directory path in the Skill installation:

node "$SKILL_DIR/scripts/validate-icons.mjs" "<project_dir>"

3. Check fonts before first export

bash "$SKILL_DIR/scripts/check-fonts.sh"
bash "$SKILL_DIR/scripts/check-fonts.sh" --install

4. Export .pptx

Execution requires an environment that allows Playwright to run; export-pptx.mjs is a compiled artifact of approximately 2 MB, and the Skill requires running it directly with node without reading the source code:

node "$SKILL_DIR/dist/export-pptx.mjs" <project_dir> --output <output_path>

If Playwright is missing, the installation method provided by the Skill is:

npm init -y && npm install playwright && npx playwright install chromium

Recommended export filename format: <title>_YYYYMMDD_HHmmss.pptx.

When communicating with users, natural language triggers are sufficient, e.g., “Create a 12-page technical report PPT based on this material” or “Change page 3 to a dark data page and re-export”. The Agent should pause at Step 4 according to the Skill to wait for outline confirmation before proceeding to generation and export.

Scenarios and Notes¶

Who it is for: Developers or office scenarios that require producing editable .pptx locally while expecting the Agent to handle research organization, pagination design, and layout consistency; categorized as office efficiency, it emphasizes deliverable files compared to usages that “only do Markdown outlines without producing files”.

Limitations and Notes:

Export relies on Node.js, Playwright, Chromium, and font environments; export within a sandbox may fail, and the Skill explicitly requires running the export command outside the sandbox.
Default is serial HTML generation page-by-page; consider parallel mode only when confirmed that the platform supports sub-Agent file writing (e.g., Claude Code).
Step 4 is a blocking step in the workflow; do not proceed to HTML generation without user confirmation to avoid unilateral finalization.
The SkillHub crawl page shows a rating of 100000 and 773 downloads (these numbers may differ from user clues due to different statistical times; refer to the SkillHub page for the latest data).

Conclusion¶

api_maker2 breaks PPT creation down into a verifiable project structure and command-line export, suitable for handing over to Agents for full-process or single-page iteration. Installation and instructions are subject to SkillHub:

Skill Page: https://www.skillhub.cn/skills/user_7e25a48a/api-maker
Installation Documentation: https://skillhub.cn/install/skillhub.md

api_maker2: Local Research → HTML → PPTX Presentation Skill