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

yolo

Skill0 starsChanged 52 days agoMITView on GitHub

Use when the user wants one complete Cricket pass on a single task — pitch, build, challenge, prove-it, then senpai and scrub if it actually passed. Not sticky. Not a license to invent scope or auto-fix findings.

11 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 2

    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:

    Run one complete Cricket pass, then walk off.

    line 8
  2. Distinctive:

    Use each child command's required close, then:

    line 42

“Common” is measured: kept by at least 6 in 10 of the 11 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

YOLO

Run one complete Cricket pass, then walk off.

The name is a joke. The gates are not. Do not treat /yolo as "just ship it."

Order

  1. /pitch — state Ask / Smallest plan / Won't do. No edits before that.
  2. Build only that plan.
  3. /challenge — try to break it. Do not patch unless asked.
  4. /prove-it — real behavior, real evidence, exactly one of PASS, FAIL, PARTIAL.
  5. On PASS only: /senpai, then /scrub.
  6. Stop.

/drift and /chirp stay out unless asked.

Stops

  • Ambiguous ask → pitch cannot be stated → wait.
  • Challenge findings → stop. Report them. Do not "go ahead and fix."
  • Prove-it FAIL → stop.
  • Scope starting to grow → ask before inventing.

A PARTIAL is not a PASS. Say what is unverified. Do not continue into senpai/scrub as if it shipped.

Must not

  • Stay on after this pass
  • Become a mode, router, or /goal replacement
  • Skip challenge or prove-it because the name sounds brave
  • Redesign during scrub
  • Quietly work around a failed check

Close

Use each child command's required close, then:

YOLO: COMPLETE | STOPPED at <step> | BLOCKED (why)

Core Rule

YOLO the sequence. Not the judgment.

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.