Menu
Help run or install a local recipe runtime without assuming the full Farmslot framework
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Drive another model through a tmux pane with guardrails. Use when Codex should orchestrate Claude, Codex, Grok, Cursor, or another agent inside an existing tmux session, verify pane state before sending input, and keep a feedback loop around observed pane output.
Build a validation recipe from PR intent, ticket ACs, or investigation findings
Author or review a Farmslot backlog spec (.backlog/specs/**) — run deterministic spec-lint, check AC↔scope traceability and code refs, then file via backlog.create with the spec attached and verify the round-trip. For agents filing work the farm will later dispatch.
Review validation recipes and evidence quality without project-specific assumptions
Communicate complex agent output as compact, reviewable Farmslot operator packets with artifact anchors and safe action requests
Succinct release-needed signal and manual release-cut workflow for Farmslot workspaces (Command Center, gateway, protocol, companion, npm packages). Run release-status first; curate Unreleased bullets; cut with reviewed proposal.
| name | recipe-harness |
| description | Help run or install a local recipe runtime without assuming the full Farmslot framework |
| compatibility | Claude, Codex, Cursor, and Markdown skill runners with shell access |
| metadata | {"package":"@farmslot/skills","related_package":"@farmslot/recipe-harness"} |
| allowed-tools | Read Bash(rg:*) Bash(node:*) Bash(npm:*) Bash(yarn:*) Bash(pnpm:*) Bash(farmslot-recipe:*) |
Use the local recipe runtime when one exists, or recommend the smallest install path when it does not.
@farmslot/recipe-harness or an app-specific harness package.farmslot-recipe run --list and farmslot-recipe run <id> --describe, then inspect declared actions only if no recipe fits. Prefer project discovery commands; otherwise read only the relevant manifest entries and examples.Return the command run, exit status, artifacts written, and any next install step.