Agent安装
- 作者仓库星标 3,406
- 作者更新于 实时读取
- 作者仓库 claude-octopus
- 领域
- 工程开发
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @nyldn · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- Shell 执行
- 网络行为
- 仅限本地
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: skill-deck
description: Generate slide deck presentations from briefs — use when you need slides, pitch decks, or visual…
category: 工程开发
runtime: 无特殊运行时
---
# skill-deck 输出预览
## PART A: 任务判断
- 适用问题:代码实现、重构、调试或代码审查。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“Prerequisites / Pipeline (4 Steps) / Step 1: Gather Brief”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于代码实现、重构、调试或代码审查,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“Prerequisites / Pipeline (4 Steps) / Step 1: Gather Brief”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、执行终端命令、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件、执行终端命令;主要在本地完成;通常不需要额外 API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 原文出现了 `/octo`、`/plugin` 这类斜杠命令;如果你的 Agent 支持命令触发,优先用命令开场,再补充目标和边界。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件、执行终端命令。
先用一个小任务确认它会围绕“Prerequisites / Pipeline (4 Steps) / Step 1: Gather Brief”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: skill-deck
description: Generate slide deck presentations from briefs — use when you need slides, pitch decks, or visual…
category: 工程开发
source: nyldn/claude-octopus
---
# skill-deck
## 什么时候使用
- 把工程方向的常用动作沉淀成 Agent 可调用的技能 适合处理工程开发场景下的代码实现、调试、重构、测试或代码审查,核心价值是把输入、判断、执行、验证和交付边界固定下来,避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代…
- 面向代码实现、重构、调试或代码审查,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Prerequisites / Pipeline (4 Steps) / Step 1: Gather Brief」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件、执行终端命令;主要在本地完成;通常不需要额外 API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "skill-deck" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Prerequisites / Pipeline (4 Steps) / Step 1: Gather Brief
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件、执行终端命令 | 主要在本地完成
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} Host: Codex CLI — This skill was designed for Claude Code and adapted for Codex. Cross-reference commands use installed skill names in Codex rather than
/octo:*slash commands. Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it. For host tool equivalents, seeskills/blocks/codex-host-adapter.md.
Slide Deck Generator
Generate professional slide decks from briefs with optional research, outline approval, and PPTX export.
Prerequisites
The document-skills plugin MUST be installed for PPTX rendering:
/plugin list | grep document-skills
If not installed, tell the user:
The document-skills plugin is required for PPTX generation.
Install it with: /plugin install document-skills@anthropic-agent-skills
Pipeline (4 Steps)
Step 1: Gather Brief
Parse the user's topic and description. Use AskUserQuestion to clarify:
Question 1 - Audience:
- Executives / Board
- Engineers / Technical
- Investors / Fundraising
- General / Mixed
Question 2 - Slide count target:
- Short (5-10 slides)
- Standard (10-20 slides)
- Extended (20+ slides)
Question 3 - Tone:
- Formal / Business
- Technical / Detailed
- Casual / Conversational
If the user already provided clear context (e.g., "10-slide investor pitch deck about our Series A"), skip questions where the answer is obvious.
Step 2: Research (Optional)
If the topic needs external research or context gathering:
- Use the host subagent tool with
Exploreorgeneral-purposesubagent to gather relevant information - For deeper multi-AI research, suggest: "For comprehensive multi-provider research, run
/octo:discover [topic]first, then/octo:deckto build slides from the results" - If the user provides their own content, notes, or a research file, skip this step entirely
This step is OPTIONAL. Many decks are built from the user's own knowledge or existing documents.
Step 3: Generate Outline
Build a slide-by-slide outline in markdown format. Structure:
## Slide 1: [Title Slide]
- Presentation title
- Subtitle / Date / Author
## Slide 2: [Agenda / Overview]
- Key topics to cover
## Slide 3: [First Content Section]
- Bullet point 1
- Bullet point 2
- Bullet point 3
## Slide N: [Summary / Next Steps]
- Key takeaways
- Call to action
IMPORTANT: Present the outline to the user for approval using AskUserQuestion:
- "Looks good, generate PPTX" — Proceed to Step 4
- "Add more slides" — Expand specific sections
- "Change focus" — Restructure around different themes
- "Start over" — Return to Step 1
This is the wireframe gate — the user MUST approve the outline structure before PPTX generation.
Step 4: Render PPTX
Once the outline is approved:
- Use the
document-skills:pptxskill to convert the approved markdown outline to PowerPoint - Each
##heading becomes a slide - Bullet points under each heading become slide content
- Save the PPTX file to the current working directory with a descriptive filename
Example filename: Series-A-Pitch-Deck-2026-02-14.pptx
Slide Structure Best Practices
Apply these when generating outlines:
- Title slide: Presentation name, subtitle, date, presenter
- Agenda slide: 3-5 key topics (for decks > 7 slides)
- One idea per slide: Keep slides focused
- 5-7 bullets max: Per slide for readability
- Summary slide: Key takeaways at the end
- Next steps / CTA: Final slide with clear actions
By Audience Type
Executives / Board:
- Lead with business impact and metrics
- Use "So what?" framing for every slide
- Include financial implications
- End with decisions needed
Engineers / Technical:
- Include architecture diagrams (describe for slides)
- Show trade-offs and alternatives considered
- Include implementation timelines
- Reference technical specifications
Investors / Fundraising:
- Problem → Solution → Market → Traction → Team → Ask
- Include market size (TAM/SAM/SOM)
- Show growth metrics and projections
- Clear funding ask and use of funds
General / Mixed:
- Balance detail with accessibility
- Define technical terms
- Use analogies and examples
- Include visual descriptions
Integration with Other Skills
This skill works well in combination with:
/octo:discover [topic]— Research first, then build deck from findings/octo:docs— For converting existing markdown to other formats/octo:prd— Generate a PRD, then create a presentation summarizing it/octo:brainstorm— Brainstorm ideas, then structure into a deck
Example Workflows
Quick Deck from Brief
User: "Create a 10-slide deck about our Q1 results"
→ Step 1: Clarify audience (executives)
→ Step 2: Skip (user has the data)
→ Step 3: Generate outline, get approval
→ Step 4: Render PPTX
Research-Backed Deck
User: "Build a presentation about AI trends in healthcare"
→ Step 1: Clarify audience and scope
→ Step 2: Research using Task agents
→ Step 3: Generate outline from research, get approval
→ Step 4: Render PPTX
Deep Research + Deck
User: "I need a comprehensive investor deck about the autonomous vehicles market"
→ Suggest: "/octo:discover autonomous vehicles market" first
→ Then: "/octo:deck" using the research synthesis
Slide deck skill for claude-octopus v8.12.0+
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核