Startup Pitch Deck

Generates structured startup pitch decks to outline business ideas, market fit, financials, and growth strategies for presentations or funding proposals.

Security Scan

This skill is an instruction-only, unfinished template for creating a startup pitch-deck generator; it requests no credentials, installs, or special system access and presents no obvious security inconsistencies, but it is non-functional as-is.

Purpose & Capability

Name and description claim a pitch-deck generator. The skill requires no binaries, env vars, or installs — that is consistent for an instruction-only skill, but the provided SKILL.md is a template with TODOs rather than working runtime instructions, so the skill as-published does not actually implement the described capability.

Instruction Scope

SKILL.md contains only authoring guidance and placeholders (TODOs). It does not contain runtime instructions that would read files, access credentials, or call external endpoints. Because it's vague and incomplete, it currently grants no explicit runtime behavior — but also provides no safe, concrete procedure for the agent to follow.

Install Mechanism

No install spec is present (instruction-only), which is the lowest-risk pattern and appropriate given the absence of code or external dependencies.

Credentials

The skill declares no required environment variables, credentials, or config paths. There is nothing requesting broad or unrelated secrets, so environment/credential access is proportionate (minimal).

Persistence & Privilege

Flags: always=false, user-invocable=true, model-invocation enabled (default). Nothing requests permanent presence or cross-skill/system config changes. Autonomous invocation is allowed by platform default but not combined with other red flags.

Assessment

This package is essentially a template, not a working skill. It poses no clear security risk because it requests no installs, binaries, or secrets, but it also won't perform the promised functionality until the SKILL.md is completed (or code/resources are added). If you want to use it: (1) ask the publisher for the completed SKILL.md or implementation files; (2) review any added runtime instructions, install specs, or required env vars before enabling the skill; and (3) prefer skills that declare a homepage/source and concrete instructions so you can verify intended behavior. If you do enable it now, there is minimal security risk, but also minimal utility.

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.