Startup Pitch Deck
Overview
[TODO: 1-2 sentences explaining what this skill enables]
Structuring This Skill
[TODO: Choose the structure that best fits this skill's purpose. Common patterns:
1. Workflow-Based (best for sequential processes)
- - Works well when there are clear step-by-step procedures
- Example: DOCX skill with "Workflow Decision Tree" -> "Reading" -> "Creating" -> "Editing"
- Structure: ## Overview -> ## Workflow Decision Tree -> ## Step 1 -> ## Step 2...
2. Task-Based (best for tool collections)
- - Works well when the skill offers different operations/capabilities
- Example: PDF skill with "Quick Start" -> "Merge PDFs" -> "Split PDFs" -> "Extract Text"
- Structure: ## Overview -> ## Quick Start -> ## Task Category 1 -> ## Task Category 2...
3. Reference/Guidelines (best for standards or specifications)
- - Works well for brand guidelines, coding standards, or requirements
- Example: Brand styling with "Brand Guidelines" -> "Colors" -> "Typography" -> "Features"
- Structure: ## Overview -> ## Guidelines -> ## Specifications -> ## Usage...
4. Capabilities-Based (best for integrated systems)
- - Works well when the skill provides multiple interrelated features
- Example: Product Management with "Core Capabilities" -> numbered capability list
- Structure: ## Overview -> ## Core Capabilities -> ### 1. Feature -> ### 2. Feature...
Patterns can be mixed and matched as needed. Most skills combine patterns (e.g., start with task-based, add workflow for complex operations).
Delete this entire "Structuring This Skill" section when done - it's just guidance.]
[TODO: Replace with the first main section based on chosen structure]
[TODO: Add content here. See examples in existing skills:
- - Code samples for technical skills
- Decision trees for complex workflows
- Concrete examples with realistic user requests
- References to scripts/templates/references as needed]
Resources (optional)
Create only the resource directories this skill actually needs. Delete this section if no resources are required.
scripts/
Executable code (Python/Bash/etc.) that can be run directly to perform specific operations.
Examples from other skills:
- - PDF skill:
fill_fillable_fields.py, extract_form_field_info.py - utilities for PDF manipulation - DOCX skill:
document.py, utilities.py - Python modules for document processing
Appropriate for: Python scripts, shell scripts, or any executable code that performs automation, data processing, or specific operations.
Note: Scripts may be executed without loading into context, but can still be read by Codex for patching or environment adjustments.
references/
Documentation and reference material intended to be loaded into context to inform Codex's process and thinking.
Examples from other skills:
- - Product management:
communication.md, context_building.md - detailed workflow guides - BigQuery: API reference documentation and query examples
- Finance: Schema documentation, company policies
Appropriate for: In-depth documentation, API references, database schemas, comprehensive guides, or any detailed information that Codex should reference while working.
assets/
Files not intended to be loaded into context, but rather used within the output Codex produces.
Examples from other skills:
- - Brand styling: PowerPoint template files (.pptx), logo files
- Frontend builder: HTML/React boilerplate project directories
- Typography: Font files (.ttf, .woff2)
Appropriate for: Templates, boilerplate code, document templates, images, icons, fonts, or any files meant to be copied or used in the final output.
Not every skill requires all three types of resources.初创企业路演PPT
概述
[TODO: 用1-2句话说明该技能的功能]
构建该技能
[TODO: 选择最适合该技能目的的结构。常见模式：
1. 基于工作流（最适合顺序流程）
- - 适用于有明确步骤的程序
- 示例：DOCX技能采用工作流决策树->读取->创建->编辑
- 结构：## 概述 -> ## 工作流决策树 -> ## 步骤1 -> ## 步骤2...
2. 基于任务（最适合工具集合）
- - 适用于提供不同操作/功能的技能
- 示例：PDF技能采用快速入门->合并PDF->拆分PDF->提取文本
- 结构：## 概述 -> ## 快速入门 -> ## 任务类别1 -> ## 任务类别2...
3. 参考/指南（最适合标准或规范）
- - 适用于品牌指南、编码标准或需求文档
- 示例：品牌样式采用品牌指南->颜色->排版->功能
- 结构：## 概述 -> ## 指南 -> ## 规范 -> ## 使用...
4. 基于能力（最适合集成系统）
- - 适用于提供多个相互关联功能的技能
- 示例：产品管理采用核心能力->编号能力列表
- 结构：## 概述 -> ## 核心能力 -> ### 1. 功能 -> ### 2. 功能...
模式可根据需要混合搭配。大多数技能会组合多种模式（例如，从基于任务开始，为复杂操作添加工作流）。
完成后删除整个构建该技能部分——这仅为指导内容。]
[TODO：根据所选结构替换为第一个主要部分]
[TODO：在此处添加内容。参考现有技能中的示例：
- - 技术技能的代码示例
- 复杂工作流的决策树
- 包含真实用户请求的具体示例
- 根据需要引用脚本/模板/参考资料]
资源（可选）
仅创建该技能实际需要的资源目录。如果不需要资源，请删除此部分。
scripts/
可直接运行执行特定操作的可执行代码（Python/Bash等）。
其他技能中的示例：
- - PDF技能：fillfillablefields.py、extractformfield_info.py——用于PDF操作的实用工具
- DOCX技能：document.py、utilities.py——用于文档处理的Python模块
适用场景： Python脚本、Shell脚本或任何执行自动化、数据处理或特定操作的可执行代码。
注意： 脚本可能在不加载到上下文的情况下执行，但Codex仍可读取以进行修补或环境调整。
references/
旨在加载到上下文中以指导Codex流程和思维的文档和参考资料。
其他技能中的示例：
- - 产品管理：communication.md、context_building.md——详细工作流指南
- BigQuery：API参考文档和查询示例
- 财务：架构文档、公司政策
适用场景： 深度文档、API参考、数据库架构、综合指南或Codex在工作时应参考的任何详细信息。
assets/
不打算加载到上下文中，而是在Codex生成的输出中使用的文件。
其他技能中的示例：
- - 品牌样式：PowerPoint模板文件（.pptx）、Logo文件
- 前端构建器：HTML/React样板项目目录
- 排版：字体文件（.ttf、.woff2）
适用场景： 模板、样板代码、文档模板、图片、图标、字体或任何旨在复制或用于最终输出的文件。
并非每个技能都需要所有三种类型的资源。
