NeeeophyteeInstall Pitch Packager
Pick your agent. Every command is ready to paste.
npx skills add Neeeophytee/finding-unknowns-skills --skill pitch-packagerThe open skills CLI detects your agents (Claude Code, Cursor, Codex and 70+ more) and installs to the right folder. Add -g to install globally.
01
Install it
Run the command above, or upload the folder in Claude.
02
Ask naturally
Describe the task. Your agent loads pitch-packager when the request matches its description.
03
Name it if needed
If it does not trigger, say “use the pitch-packager skill”. In Codex, type $pitch-packager.
Pitch packager
Reviewers start with the same unknowns the builder started with, plus one more: whether the builder accounted for the failure points an expert would probe. A good pitch doc kills both in one read.
Steps
- Collect the artifacts: the spec or plan, the prototype or demo, the implementation notes, and the diff. Ask for a demo recording or screenshots if any user-facing behavior changed — lead with that.
- Structure the document in reading order for a skeptic:
- The demo — what it looks like working, first. A GIF or screenshot beats prose.
- The problem and the bet — two paragraphs max: what this solves and the approach chosen over the alternatives.
- What an expert would ask — the 3-5 hard questions a reviewer in this domain would raise (edge cases, scale, failure modes, migration), each answered honestly, including "not handled, here's why that's acceptable for now."
- Deviations from plan — lifted straight from implementation-notes, because surprises found in review cost trust.
- What's NOT in this change — scope fences, so the review doesn't sprawl.
- Keep it one page. Link out to the spec, notes, and diff rather than inlining them.
- Match the medium to the venue: a Slack-pasteable doc, a PR description, or a standalone HTML page — ask which if unclear.
Guardrails
- Never oversell: a pitch that hides a known weakness converts one approval into a permanent credibility loss.
- The "what an expert would ask" section is the heart. If it's easy to write, the questions aren't hard enough.
- If the work isn't actually ready, the honest pitch is a status update, and saying so is part of this skill.
Tips for Pitch Packager
- • Start a fresh session after installing so your agent picks up the new skill.
- • It is part of a pack with 14 skills. Install only the ones you need with --skill to keep triggers precise.
- • If two skills overlap, mention the one you want by name.
Questions about Pitch Packager
What does the Pitch Packager skill do?
Package a finished piece of work (spec, prototype, implementation notes) into a single document that gets reviewers to understanding and approval fast. Use when the user needs buy-in, a review, or a shareable summary of what was built and why.
How do I install Pitch Packager?
Run "npx skills add Neeeophytee/finding-unknowns-skills --skill pitch-packager" in your project. The skills CLI installs it for Claude Code, Cursor, Codex and 70+ other agents. In Claude on the web, upload the skill folder as a ZIP under Customize > Skills.
Does Pitch Packager work in Cursor and Codex?
Yes. Pitch Packager uses the open SKILL.md format, so it works in Claude Code, Claude, Cursor, OpenAI Codex, Gemini CLI, GitHub Copilot and other agents that support agent skills.
Is Pitch Packager free?
Pitch Packager is open source on GitHub under the MIT license. It is free to install; check the license before commercial use.
Who made Pitch Packager?
Pitch Packager is published by Neeeophytee in the Neeeophytee/finding-unknowns-skills repository, together with 13 other skills.
