SlideClaw Skill (OpenClaw + ClawHub)

Use this skill to run end-to-end Marp slide production with SlideClaw.

When to use

• User asks to create slides with Marp.
• User asks to turn a topic or requirements into a deck.
• User asks to render slides.md to PDF/HTML/PPTX/PNG.
• User asks to reuse or save slide design templates.

When not to use

• Task is not about slides/Marp.
• User only wants generic writing without file operations.
• User asks for a different slide stack (e.g., Google Slides API directly).

ClawHub-first assumptions

This skill is designed to work even when installed from ClawHub into a workspace that does not have this repository cloned.

• Prefer a local slideclaw binary when available.
• Otherwise use npx -y slideclaw@latest.
• If this is not yet a SlideClaw workspace, initialize it in the current directory.

Command resolver (use this order)

1. If slideclaw exists on PATH, use it.
2. Else if ./bin/slideclaw.js exists, use node ./bin/slideclaw.js.
3. Else use npx -y slideclaw@latest.

In steps below, treat <SC> as the resolved command prefix.

Examples:

<SC> doctor
<SC> --json template list
<SC> render <project-id> --format pdf

Bootstrap flow (required before doing slide work)

1. Run health check:

<SC> doctor

2. If workspace marker .slideclaw/ is missing, initialize in current directory:

<SC> init . --with-starter-template

3. Re-check:

<SC> doctor

If any required dependency is missing, report clearly and stop before content work.

Inputs to collect from user

Ask only what is required:

• Purpose (required)
• Audience (required)
• Topic (required)
• Duration / slide count (optional)
• Tone (optional)

Limit to 4 questions in one round.

End-to-end workflow

[1] Resolve <SC> and bootstrap workspace
[2] Confirm requirements
[3] Pick template (or create new design)
[4] Create project
[5] Fill requirements.md
[6] Write slides.md
[7] Render HTML for fast validation
[8] Render PDF for final output
[9] Confirm with user, iterate if needed
[10] Mark done and optionally save template
[11] Update profile/user.md

Step 1. Template selection

Always use CLI JSON output:

<SC> --json template list

Rules:

• Do not force one template without user confirmation.
• Present all candidates in one short list.
• Include "create a new design" as an option.

If no template exists, continue with project creation without template and create style in project theme.css.

Step 2. Create project

Always pass explicit kebab-case ID:

<SC> project new "<name>" \
  --id 2026-04-09-topic-name \
  --template <template-id> \
  --title "<title>" \
  --audience "<audience>" \
  --goal "<goal>"

If no template is selected, omit --template.

Step 3. Update requirements.md

Edit:

• Background
• Must-include points
• Open questions

Then share a 3-5 line summary and wait for user confirmation.

Step 4. Write slides.md