Skip to content
Contact
Marketing

Pitch Deck

shawnpang

Build a pitch narrative linking customer pain, product proof, distribution, economics, and the financing decision.

SKILL.md

---
name: knoveya-pitch-deck
description: "Build a pitch narrative linking customer pain, product proof, distribution, economics, and the financing decision. Use for matching marketing work."
---

# Pitch Deck

## Scope

Apply this guidance when the requested task matches the description. Honor the user's chosen outcome, repository rules, and existing authorization.

## Workflow

Build a pitch narrative linking customer pain, product proof, distribution, economics, and the financing decision.

Before acting, inspect the relevant artifact and ask only for information that materially changes the result. Use existing tools and conventions; do not install dependencies, publish, send messages, deploy, or mutate external data unless the user has authorized that operation.

## Acceptance check

Unsupported traction or market numbers are marked for verification.

## Example task

Explain a narrow initial segment before describing market expansion.

## Report

State what changed, the evidence checked, and what remains unverified. Do not claim a successful operation or completed test without observing it.
View all

How to use

Copy the full block, including its frontmatter, into a new folder named knoveya-pitch-deck as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-pitch-deck/SKILL.md; check the current documentation for another agent's supported location. Do not overwrite an existing skill.

This is an independent Knoveya skill. No files are installed by this website.

Example

Explain a narrow initial segment before describing market expansion.

Verify

Unsupported traction or market numbers are marked for verification.

Test the skill on a small, authorized example. File validation alone does not prove that an agent will make good decisions.

Limits

The skill supplies instructions, not tool access or expertise guarantees. Inspect generated work and preserve the user's approval boundaries.