PPT设计
- 作者仓库星标 435
- 作者更新于 实时读取
- 作者仓库 nvim
- 领域
- 设计与多媒体
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @benbrastmckie · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- Shell 执行
- 网络行为
- 仅限本地
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: skill-slides
description: Research talk material synthesis, design-aware planning, and presentation assembly. Invoke for s…
category: 设计与多媒体
runtime: 无特殊运行时
---
# skill-slides 输出预览
## PART A: 任务判断
- 适用问题:视觉内容、演示材料、信息图或设计交付。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“Context References / Trigger Conditions / Workflow Type Routing”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于视觉内容、演示材料、信息图或设计交付,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“Context References / Trigger Conditions / Workflow Type Routing”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、执行终端命令、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件、执行终端命令;主要在本地完成;通常不需要额外 API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 原文出现了 `/plan`、`/slides`、`/research`、`/implement` 这类斜杠命令;如果你的 Agent 支持命令触发,优先用命令开场,再补充目标和边界。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件、执行终端命令。
先用一个小任务确认它会围绕“Context References / Trigger Conditions / Workflow Type Routing”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: skill-slides
description: Research talk material synthesis, design-aware planning, and presentation assembly. Invoke for s…
category: 设计与多媒体
source: benbrastmckie/nvim
---
# skill-slides
## 什么时候使用
- 把设计与视觉方向的常用动作沉淀成 Agent 可调用的技能 适合处理界面、视觉、封面、信息图或演示材料交付,核心价值是把输入、判断、执行、验证和交付边界固定下来,避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代的步骤…
- 面向视觉内容、演示材料、信息图或设计交付,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Context References / Trigger Conditions / Workflow Type Routing」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件、执行终端命令;主要在本地完成;通常不需要额外 API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "skill-slides" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Context References / Trigger Conditions / Workflow Type Routing
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件、执行终端命令 | 主要在本地完成
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} 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.
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核