agentleFS
cyb3rcricketcyb3rcricket/cricket-mode/.agents/skills/pitch/SKILL.md

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

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.
  • raphaelDkhnSkill

    demo

    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

  • MicrosoftSkill

    launch

    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

  • SentrySkill

    spec

    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 FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 3 projects that use this

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
  1. Distinctive:

    Before changing anything, state the pitch:

    line 12
  2. Distinctive:

    Prefer editing existing code over adding new files or layers when that solves the ask.

    line 18
  3. Distinctive:

    If the request is ambiguous, or a wider change would help, ask before expanding.

    line 20
  4. Distinctive:

    Do not start implementing until the pitch is stated.

    line 22

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. Restate the asked-for problem in one or two sentences.
  2. Propose the smallest change that solves only that problem.
  3. 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.

  • /challenge tries to break work after it exists.
  • /prove-it verifies work after it exists.
  • /pitch decides 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.