Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Package a finished piece of work (spec, prototype, implementation notes) into a single document that gets reviewers to understanding and approval fast.
Install Pitch Packager
$ npx skills add Neeeophytee/finding-unknowns-skills --skill pitch-packager -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills pitch-packager --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pitch-packager .claude/skills/pitch-packager && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pitch-packager" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/pitch-packager into .claude/skills/pitch-packager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pitch-packager", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/pitch-packagerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Neeeophytee/finding-unknowns-skills --skill pitch-packager -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills pitch-packager --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/pitch-packager .agents/skills/pitch-packager && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pitch-packager" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/pitch-packager into .agents/skills/pitch-packager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pitch-packager", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Neeeophytee/finding-unknowns-skills --skill pitch-packager -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills pitch-packager --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/pitch-packager .cursor/skills/pitch-packager && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pitch-packager" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/pitch-packager into .cursor/skills/pitch-packager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pitch-packager", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Neeeophytee/finding-unknowns-skills.git --path skills/pitch-packager--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Neeeophytee/finding-unknowns-skills --skill pitch-packager -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills pitch-packager --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/pitch-packager .gemini/skills/pitch-packager && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pitch-packager" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/pitch-packager into .gemini/skills/pitch-packager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pitch-packager", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Neeeophytee/finding-unknowns-skills pitch-packagerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Neeeophytee/finding-unknowns-skills --skill pitch-packager -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/pitch-packager .github/skills/pitch-packager && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pitch-packager" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/pitch-packager into .github/skills/pitch-packager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pitch-packager", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Neeeophytee/finding-unknowns-skills --skill pitch-packager -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills pitch-packager --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/pitch-packager .opencode/skills/pitch-packager && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pitch-packager" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/pitch-packager into .opencode/skills/pitch-packager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pitch-packager", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pitch-packager- GitHub stars
- 343
- Token cost
- ~493 tokens
- SKILL.md length
- 270 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
Package a finished piece of work (spec, prototype, implementation notes) into a single document that gets reviewers to understanding and approval fast.
- Works in 4 steps: Collect the artifacts: the spec or plan,… → Structure the document in reading order… → Keep it one page. Link out to the spec,… → …
- The user needs buy-in
- SKILL.md covers Steps and Guardrails
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Pitch Packager is an agent skill from Neeeophytee/finding-unknowns-skills. 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.
Its SKILL.md is about 490 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. The repository describes itself as: 14 installable skills for Claude Code, OpenAI Codex, and Hermes: find unknowns, clarify requirements, manage context, test assumptions, and verify bug fixes with regression… The licence is MIT.
When your agent uses it
- The user needs buy-in
- A shareable summary of what was built and why
Example prompts
- “/pitch-packager”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Collect the artifacts: the spec or plan, the prototype or demo, the implementation notes, and the diff. Ask for a demo recording or…
- Structure the document in reading order for a skeptic
- 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.
What it can do on your machine
Read from SKILL.md and the folder at commit ca5696a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Pitch Packager loads about 493 tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 270 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Neeeophytee/finding-unknowns-skills at commit ca5696a, republished under its MIT licence (© Neeeophytee). 270 words, ~493 tokens.
Download SKILL.mdSave it as
.claude/skills/pitch-packager/SKILL.md (or your agent's skills folder).- name
- pitch-packager
- description
- 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.
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.
© Neeeophytee, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/pitch-packager of Neeeophytee/finding-unknowns-skills.
Open the folder on GitHubat commit ca5696a
Compare with similar skills
Pitch Packager next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pitch Packager this skillNeeeophytee/finding-unknowns-skills | 343 | — | ~493 | Automated safety check: Pass | MIT | |
| Vercel Composition Patternssupabase/supabase | 111k | 58 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
More from Neeeophytee/finding-unknowns-skills
All 14 skills in this repoAgent Interface Design
Neeeophytee/finding-unknowns-skills
Design tools, scripts, and CLIs that an agent will call, so the interface teaches its own use instead of a wall of prose and examples.
Assumption Test
Neeeophytee/finding-unknowns-skills
Test a consequential technical assumption with a small, falsifiable experiment before committing to an approach.
Blindspot Pass
Neeeophytee/finding-unknowns-skills
Surface the user's unknown unknowns before work starts. An agent skill from Neeeophytee/finding-unknowns-skills.
Brainstorm Prototypes
Neeeophytee/finding-unknowns-skills
Generate several genuinely different throwaway variations (designs, approaches, drafts) for the user to react to.
Change Quiz
Neeeophytee/finding-unknowns-skills
After a working session, produce a report on what changed plus a quiz the user must pass before merging.
Context Audit
Neeeophytee/finding-unknowns-skills
Audit the instructions an agent already carries — CLAUDE.md, AGENTS.md, skills, tool descriptions — for contradictions, over-constraint, and duplication, then propose a cut list.
Related
Categories
Questions about Pitch Packager
What does Pitch Packager do?
Package a finished piece of work (spec, prototype, implementation notes) into a single document that gets reviewers to understanding and approval fast. Pitch Packager is an agent skill from Neeeophytee/finding-unknowns-skills. Package a finished piece of work (spec, prototype, implementation notes) into a single document that gets reviewers to understanding and approval fast.
When should I use Pitch Packager?
Pitch Packager fits situations like: the user needs buy-in; A shareable summary of what was built and why.
How do I install Pitch Packager in Claude Code?
Run `npx skills add Neeeophytee/finding-unknowns-skills --skill pitch-packager -a claude-code`. Or copy the skill folder (skills/pitch-packager in Neeeophytee/finding-unknowns-skills) into .claude/skills/pitch-packager in your project. Claude Code loads it when a task matches its description.
How do I install Pitch Packager in Codex?
Run `npx skills add Neeeophytee/finding-unknowns-skills --skill pitch-packager -a codex`. Or copy the skill folder (skills/pitch-packager in Neeeophytee/finding-unknowns-skills) into .agents/skills/pitch-packager in your project. Codex loads it when a task matches its description.
Can I use Pitch Packager in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Neeeophytee/finding-unknowns-skills --skill pitch-packager -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pitch-packager, .gemini/skills/pitch-packager, .github/skills/pitch-packager and .opencode/skills/pitch-packager in your project.
What does Pitch Packager need to run?
SKILL.md names no scripts, command-line tools or credentials: Pitch Packager is instructions for the agent only.
Does Pitch Packager access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Pitch Packager safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Pitch Packager use?
Pitch Packager is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Pitch Packager use?
About 493 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Pitch Packager?
Skills that share tags, products or a category with Pitch Packager: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pitch Packager?
Neeeophytee (a GitHub user) maintains it in Neeeophytee/finding-unknowns-skills, which has 343 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 28, 2026.
Source: Neeeophytee/finding-unknowns-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.