pitch
Skill0 starsChanged 51 days agoMITView on GitHub
Use when about to write or expand code, to clamp the change to the smallest edit that solves only the stated problem and ask before inventing helpers, abstractions, or extra scope.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- n1kben/agentstheir own version, first seen Nov 16, 2026
- serhiileniv/skillstheir own version, first seen Nov 8, 2026
- serhiileniv/ccstheir own version, first seen Nov 8, 2026
- eggs-gd/career-spacetheir own version, first seen Nov 8, 2026
- aya-taleb/biz-ready-skillstheir own version, first seen Nov 1, 2026
- bengialb/pitch-skilltheir own version, first seen Oct 25, 2026
Used with
Projects with it also use demo, launch and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
raphaelDkhnSkilldemo
Plan bottom-up artifacts that test the core hypothesis — landing pages, painted-door tests, click-through prototypes, product screenshots, spec docs, copy. Not production code. Refuses to proceed without a live hypothesis.md. Defines the engagement metric that would confirm or refute the hypothesis. Separates coding from validation signal. Use when asked to "build a demo", "landing page", "prototype this", "painted door test", "MVP spec", "demo my idea", "how do I test this". Proactively invoke this skill (do NOT answer directly) when the user has a hypothesis and wants to run a bottom-up test. Use after /hypothesis. For actual production code, redirect to gstack. (worldbuilder)
Also in 3 projects that use this
MicrosoftSkilllaunch
Launch and automate VS Code Insiders with the Copilot Chat extension using @playwright/cli via Chrome DevTools Protocol. Use when you need to interact with the VS Code UI, automate the chat panel, test the extension UI, or take screenshots. Triggers include 'automate VS Code', 'interact with chat', 'test the UI', 'take a screenshot', 'launch with debugging'.
Also in 3 projects that use this
SentrySkillspec
Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.
Also in 3 projects that use this
Hugging FaceSkillimplement
Make tests pass. Invoke after /write-tests produces failing tests.
Also in 3 projects that use this
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- lglucas/ai-dev-operating-system★ 12same name
- eggs-gd/career-space★ 4same name
- FakharEAli/book-skills★ 3same name
- aya-taleb/biz-ready-skills★ 1same name
- madeehahassan/plsbuild-os★ 1same name
- ORBWEVA/founder-pitch★ 1same name
- T4LEL/Claude-Arsenal★ 1same name
- vertile-ai/skills★ 1same name
- bengialb/pitch-skill★ 0same name
- mfraunhofer/claude-skills★ 0same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Before changing anything, state the pitch:
- Distinctive: line 18
Prefer editing existing code over adding new files or layers when that solves the ask.
- Distinctive: line 20
If the request is ambiguous, or a wider change would help, ask before expanding.
- Distinctive: line 22
Do not start implementing until the pitch is stated.
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Pitch
Constrain the approach before you write or expand code.
Solve only the problem that was asked. The smallest change that does that job is the whole plan.
Before changing anything, state the pitch:
- Restate the asked-for problem in one or two sentences.
- Propose the smallest change that solves only that problem.
- List what you will not do.
Prefer editing existing code over adding new files or layers when that solves the ask.
If the request is ambiguous, or a wider change would help, ask before expanding. Do not silently widen scope.
Do not start implementing until the pitch is stated. After it is stated, proceed with that plan unless the user redirects.
This is the pre-flight clamp. It is not a review of work already done.
/challengetries to break work after it exists./prove-itverifies work after it exists./pitchdecides the smallest change before the code exists.
Core Rule
Solve only what was asked. Ask before inventing.
State this before coding:
Ask: the problem in one or two sentences.
Smallest plan: the minimal change.
Won't do: explicit non-goals, including invented helpers, drive-by cleanups, new abstractions, unrelated refactors, and speculative edge-case machinery.
Then implement that plan unless the user stops you.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

