Cook: A simple CLI for orchestrating Claude Code

sbinnee 32 minutes ago | parent | next [-]

There is a skill installation option. The skill markdown has 180 lines [1].

My take? I like it. It's concise enough for me to try it out. And I love the webpage.

[1] https://github.com/rjcorwin/cook/blob/main/no-code/SKILL.md

xiaolu627 10 minutes ago | parent | prev | next [-]

Thanks for sharing this post about Cook CLI. I like how it uses a recipe-based pattern to define workflows declaratively, making orchestration simpler and cleaner. Great approach to handling execution!

▲

rc_kas an hour ago | parent | prev | next [-]

Can someone explain what this is to my n00b brain. I don't get what claude-cli is missing that this adds in?

▲

sghiassy 14 minutes ago | parent | next [-]

As a prerequisite you’d want to understand the purpose of Ralph Wiggum Loops

But in general this is meta to the CLI agent.

So if you were to use the CLI to perform a review of some code. This tool would allow you to loop the output of the code review 5 times onto itself.

▲

beshrkayali an hour ago | parent | prev | next [-]

IMO the raw Claude CLI is great for one-off interactive sessions, but as soon as you want repeatable multi-step workflows you’re either copy-pasting prompts forever or hacking your own solution manually. That’s exactly the gap these tools fill.

My take on a solution for this is https://ossature.dev — .smd spec markdown files + ossature audit / build that gives you DAG orchestration, SHA-traced increments, and tiny focused contexts.

▲

transitorykris an hour ago | parent | prev [-]

Maybe not adds in, but wraps around. You could accomplish much of this with fairly simply bash scripts.

▲

esperent an hour ago | parent [-]

You could accomplish all of it with claude -p (headless mode).

	▲	transitorykris 40 minutes ago \| parent \| next [-]
		Admittedly I might be missing a flag or two with claude, but how are multiple loops and comparisons of solutions done with just headless mode?
	▲	brcmthrowaway 41 minutes ago \| parent \| prev [-]
		Indeed. Where are people finding time for these sort of projects.

▲

pissedoffadmin 19 minutes ago | parent | prev | next [-]

i wanna pelt rocks at anthropic

▲

rafaamaral an hour ago | parent | prev [-]

Nice approach to the orchestration problem. The recipe-based pattern is clean — define the workflow declaratively, let the CLI handle the execution.

One thing I've been thinking about with tools like this: as you chain more Claude Code calls, the cost compounds fast. A single "cook" run with 5-6 steps could easily burn through $10-15 in API credits if you're not careful about which model handles which step.

Has anyone experimented with routing different recipe steps to different model tiers? E.g., using Haiku for boilerplate generation and Opus only for the steps that actually need deep reasoning? That's where the real savings are in multi-agent orchestration.

▲

Yiin an hour ago | parent [-]

just use 200usd plan, I forgot what limits are.

▲

croes an hour ago | parent [-]

You'll remember it soon

▲

weird-eye-issue an hour ago | parent [-]

Do you often hit the limits recently on the $200 plan? I don't even come close

▲

dionian 36 minutes ago | parent [-]

i used to, its much better now. opus 4.6 has been great on tokens

	▲	weird-eye-issue 25 minutes ago \| parent [-]
		Yes, quite a while back, they used to charge a lot more for the Opus tokens