agentleFS
Sign inStart free
paulnsorensenpaulnsorensen/easy-cheese/skills/ultracook/SKILL.md

ultracook

Skill19 starsChanged 28 days agoMITView on GitHub

Retired — /ultracook no longer exists as a standalone skill. Any /ultracook invocation resolves to /cook, which now owns the single implementation pathway (including the fan-out mechanics this skill used to run). Use /cook instead.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If you are here because muscle memory typed /ultracook, run /cook with the same arguments.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

/ultracook (retired)

/ultracook is retired as a top-level skill. Its mechanics — decompose, wave-fan curds, harvest, wire, post-merge review, plate — now live inside /cook's single pathway, dispatched via /cook --auto, each phase still running as a fresh, isolated sub-agent context blind to the prior phase's reasoning. See ../cook/SKILL.md's ## Fan pathway section.

Redirect

Any /ultracook <spec> [flags] invocation resolves to /cook <spec> [flags]. Carry --open-pr, --resume <slug>, and --auto forward verbatim — their semantics are unchanged, just hosted inside /cook now.

What did not move

  • skills/ultracook/references/ remains as compatibility material for /cook's fan pathway; executable runtime now ships only through the cook archive (skills/cook/scripts/cook.pyz), and no ultracook archive is published.
  • The manifest path stays .cheese/ultracook/<slug>/manifest.yaml for continuity — the identity of the skill that reads/writes it changed, not the path; its shape is references/manifest-schema.json, and each curd's dispatch prompt is references/curd-prompt.md, both read by /cook's fan pathway.
  • src/easy_cheese/shared/fanout/mode.py remains a decomposer/fanout internal — /cook's fan pathway calls it directly rather than through this retired skill.
  • The retained scripts/references still do source-code I/O under /cook's ownership — that follows code-intelligence-routing.md same as everywhere else.

If you are here because muscle memory typed /ultracook, run /cook with the same arguments.

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.

Check your setup, free