skill-slides
- Repo stars 435
- Author updated Live
- Author repo nvim
- Domain
- Design
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @benbrastmckie · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: skill-slides
description: Research talk material synthesis, design-aware planning, and presentation assembly. Invoke for s…
category: design
runtime: no special runtime
---
# skill-slides output preview
## PART A: Task fit
- Use case: Research talk material synthesis, design-aware planning, and presentation assembly. Invoke for slides tasks. Thin wrapper that delegates slides work to the appropriate subagent based on workflow type and output format: runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Context References / Trigger Conditions / Workflow Type Routing” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Research talk material synthesis, design-aware planning, and presentation assembly. Invoke for slides tasks. Thin wrapper that delegates slides work to the appropriate subagent based on workflow type and output format: runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Context References / Trigger Conditions / Workflow Type Routing” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source mentions slash commands such as `/plan`, `/slides`, `/research`, `/implement`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “Context References / Trigger Conditions / Workflow Type Routing”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skill-slides
description: Research talk material synthesis, design-aware planning, and presentation assembly. Invoke for s…
category: design
source: benbrastmckie/nvim
---
# skill-slides
## When to use
- Research talk material synthesis, design-aware planning, and presentation assembly. Invoke for slides tasks. Thin wrap…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Context References / Trigger Conditions / Workflow Type Routing” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skill-slides" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Context References / Trigger Conditions / Workflow Type Routing
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} Slides Skill
Thin wrapper that delegates slides work to the appropriate subagent based on workflow type and output format:
- slides-research-agent: Material synthesis into slide-mapped research reports
- pptx-assembly-agent: PowerPoint generation from research reports
- slidev-assembly-agent: Slidev project generation from research reports
Note: Plan workflow (/plan present:slides) is handled by skill-slide-planning, not this skill.
IMPORTANT: This skill implements the skill-internal postflight pattern. After the subagent returns, this skill handles all postflight operations (status update, artifact linking, git commit) before returning. This eliminates the "continue" prompt issue between skill return and orchestrator.
Context References
Reference (do not load eagerly):
- Path:
.claude/context/formats/return-metadata-file.md- Metadata file schema - Path:
.claude/context/patterns/postflight-control.md- Marker file protocol - Path:
.claude/context/patterns/file-metadata-exchange.md- File I/O helpers - Path:
.claude/context/patterns/jq-escaping-workarounds.md- jq escaping patterns (Issue #1132)
Note: This skill is a thin wrapper with internal postflight. Context is loaded by the delegated agent.
Trigger Conditions
This skill activates when:
/slidescommand with task number input/researchon a task withtask_type: "present:slides"/implementon a task withtask_type: "present:slides"(assemble workflow)- Present extension is available
Workflow Type Routing
This skill routes to the appropriate subagent based on workflow type and output format:
| Workflow Type | Preflight Status | Success Status | TODO.md Markers |
|---|---|---|---|
| slides_research | researching | researched | [RESEARCHING] -> [RESEARCHED] |
| assemble | implementing | completed | [IMPLEMENTING] -> [COMPLETED] |
Note: Assembly agents read design_decisions.theme with a fallback chain:
design_decisions -> research report "Recommended Theme" -> default academic-clean.
Input Parameters
Required Parameters
task_number- Task number (must exist in state.json with task_type="present:slides")session_id- Session ID from orchestrator
Optional Parameters
workflow_type- One of: slides_research, assemble (default: slides_research)
Execution Flow
Stage 1: Input Validation
Validate required inputs:
task_number- Must be provided and exist in state.json- Verify task_type is "present:slides"
# Lookup task
task_data=$(jq -r --argjson num "$task_number" \
'.active_projects[] | select(.project_number == $num)' \
specs/state.json)
# Validate exists
if [ -z "$task_data" ]; then
return error "Task $task_number not found"
fi
# Extract fields
task_type=$(echo "$task_data" | jq -r '.task_type // ""')
status=$(echo "$task_data" | jq -r '.status')
project_name=$(echo "$task_data" | jq -r '.project_name')
description=$(echo "$task_data" | jq -r '.description // ""')
# Validate task_type (supports "present:slides" or legacy "slides")
if [ "$task_type" != "present:slides" ] && [ "$task_type" != "slides" ]; then
return error "Task $task_number is not a slides task (task_type=$task_type)"
fi
Stage 2: Preflight Status Update
Update task status based on workflow type BEFORE invoking subagent.
| Workflow Type | state.json status | TODO.md marker |
|---|---|---|
| slides_research | researching | [RESEARCHING] |
| plan | planning | [PLANNING] |
| assemble | implementing | [IMPLEMENTING] |
# Extract output_format from forcing_data (default: "slidev" for backward compatibility)
output_format=$(echo "$task_data" | jq -r '.forcing_data.output_format // "slidev"')
case "$workflow_type" in
slides_research)
preflight_status="researching"
preflight_marker="[RESEARCHING]"
;;
assemble)
preflight_status="implementing"
preflight_marker="[IMPLEMENTING]"
;;
esac
# Update state.json
if [ -n "$preflight_status" ]; then
jq --arg ts "$(date -u +%Y-%m-%dT%H:%M:%SZ)" \
--arg status "$preflight_status" \
--arg sid "$session_id" \
'(.active_projects[] | select(.project_number == '$task_number')) |= . + {
status: $status,
last_updated: $ts,
session_id: $sid
}' specs/state.json > specs/tmp/state.json && mv specs/tmp/state.json specs/state.json
fi
Stage 3: Create Postflight Marker
padded_num=$(printf "%03d" "$task_number")
mkdir -p "specs/${padded_num}_${project_name}"
cat > "specs/${padded_num}_${project_name}/.postflight-pending" << EOF
{
"session_id": "${session_id}",
"skill": "skill-slides",
"task_number": ${task_number},
"operation": "${workflow_type}",
"reason": "Postflight pending: status update, artifact linking, git commit",
"created": "$(date -u +%Y-%m-%dT%H:%M:%SZ)",
"stop_hook_active": false
}
EOF
Stage 4: Prepare Delegation Context
Resolve the target agent based on workflow_type and output_format:
case "$workflow_type" in
slides_research)
target_agent="slides-research-agent"
;;
assemble)
case "$output_format" in
pptx) target_agent="pptx-assembly-agent" ;;
*) target_agent="slidev-assembly-agent" ;;
esac
;;
esac
Delegation context:
{
"session_id": "sess_{timestamp}_{random}",
"delegation_depth": 1,
"delegation_path": ["orchestrator", "slides", "skill-slides", "{target_agent}"],
"timeout": 3600,
"task_context": {
"task_number": N,
"task_name": "{project_name}",
"description": "{description}",
"task_type": "present:slides"
},
"workflow_type": "slides_research|assemble",
"output_format": "slidev|pptx (extracted from forcing_data, default: slidev)",
"forcing_data": "{from state.json task metadata, includes output_format}",
"metadata_file_path": "specs/{NNN}_{SLUG}/.return-meta.json"
}
Stage 5: Invoke Subagent
CRITICAL: Use the Agent tool to spawn the subagent. Use the target_agent resolved in Stage 4.
Tool: Agent (NOT Skill, NOT Plan)
Parameters:
- subagent_type: "{target_agent}"
- prompt: [Include task_context, delegation_context, workflow_type, forcing_data, metadata_file_path]
- description: "Execute {workflow_type} for task {N}"
Routing table:
| workflow_type | output_format | target_agent |
|---|---|---|
slides_research |
any | slides-research-agent |
assemble |
pptx |
pptx-assembly-agent |
assemble |
slidev (default) |
slidev-assembly-agent |
DO NOT use Skill(...) - this will FAIL. Always use Task.
Stage 5b: Self-Execution Fallback
CRITICAL: If you performed the work above WITHOUT using the Agent tool (i.e., you read files,
wrote artifacts, or updated metadata directly instead of spawning a subagent), you MUST write a
.return-meta.json file now before proceeding to postflight. Use the schema from
return-metadata-file.md with the appropriate status value for this operation.
If you DID use the Agent tool, skip this stage -- the subagent already wrote the metadata.
Postflight (ALWAYS EXECUTE)
The following stages MUST execute after work is complete, whether the work was done by a subagent or inline (Stage 5b). Do NOT skip these stages for any reason.
Stage 6: Read Metadata File
metadata_file="specs/${padded_num}_${project_name}/.return-meta.json"
if [ -f "$metadata_file" ] && jq empty "$metadata_file" 2>/dev/null; then
meta_status=$(jq -r '.status' "$metadata_file")
artifact_path=$(jq -r '.artifacts[0].path // ""' "$metadata_file")
artifact_type=$(jq -r '.artifacts[0].type // ""' "$metadata_file")
artifact_summary=$(jq -r '.artifacts[0].summary // ""' "$metadata_file")
else
echo "Error: Invalid or missing metadata file"
meta_status="failed"
fi
Stage 7: Update Task Status (Postflight)
| Workflow Type | Meta Status | Final state.json | Final TODO.md |
|---|---|---|---|
| slides_research | researched | researched | [RESEARCHED] |
| slides_research | partial | researching | [RESEARCHING] |
| assemble | assembled | completed | [COMPLETED] |
| assemble | partial | implementing | [IMPLEMENTING] |
| any | failed | (keep preflight) | (keep preflight marker) |
Stage 8: Link Artifacts
Add artifact to state.json with summary. Use the two-step jq pattern to avoid Issue #1132.
Update TODO.md: Link artifact per @.claude/context/patterns/artifact-linking-todo.md with field_name=**Summary**, next_field=**Description**.
Stage 9: Git Commit
case "$workflow_type" in
slides_research)
commit_action="complete slides research"
;;
assemble)
# Branch commit message on output_format
if [ "$output_format" = "pptx" ]; then
commit_action="assemble PPTX presentation"
else
commit_action="assemble Slidev presentation"
fi
;;
esac
git add -A
git commit -m "task ${task_number}: ${commit_action}
Session: ${session_id}
Stage 10: Cleanup
rm -f "specs/${padded_num}_${project_name}/.postflight-pending"
rm -f "specs/${padded_num}_${project_name}/.postflight-loop-guard"
rm -f "specs/${padded_num}_${project_name}/.return-meta.json"
Stage 11: Return Brief Summary
Talk Research Success:
Talk research completed for task {N}:
- Synthesized source materials into slide-mapped report
- Talk type: {talk_type}, {slide_count} slides mapped
- Created report at specs/{NNN}_{SLUG}/reports/{MM}_slides-research.md
- Status updated to [RESEARCHED]
- Changes committed with session {session_id}
Assemble Success (Slidev):
Slidev presentation assembled for task {N}:
- Output directory: talks/{N}_{slug}/
- Files created: slides.md, style.css, README.md
- Theme: {theme_name}
- Status updated to [COMPLETED]
- Changes committed with session {session_id}
Assemble Success (PPTX):
PPTX presentation assembled for task {N}:
- Output directory: talks/{N}_{slug}/
- Files created: {slug}.pptx, generate_deck.py
- Theme: {theme_name}
- Status updated to [COMPLETED]
- Changes committed with session {session_id}
Error Handling
Task not found
Talk skill error for task {N}:
- Task not found in state.json
- No status changes made
Wrong language/task_type
Talk skill error for task {N}:
- Task is not a talk task (language={language}, task_type={task_type})
- Use /slides for talk-type tasks
- No status changes made
Metadata file missing
Keep status at preflight level for resume.
Git commit failure
Non-blocking. Log failure but continue.
Return Format
This skill returns a brief text summary (NOT JSON). The JSON metadata is written to the file and processed internally.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review