pitch-packager
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.
npx skills add Neeeophytee/finding-unknowns-skills --skill pitch-packager --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 1. 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. 2. 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. 3. Keep it one page. Link out to the spec, notes, and diff rather than inlining them. 4. Matc
- Steps
- Guardrails
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 it?
Run `npx skills add Neeeophytee/finding-unknowns-skills --skill pitch-packager --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Neeeophytee/finding-unknowns-skills, a repository with 298 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.