Skills
The workflows — mms-recipe-cook, mms-recipe-pr-qa-review and the rest.
They call mm-harness; they are not a dependency of it.
Which repo is which
Six things sit behind a recipe run, and it is not obvious from the outside which one you install, which one you contribute to, and which one is just a dependency. This is the dependency map — not a pitch.
calls ↓
mm-harness
Launch, typed actions, graph execution, artifacts. Installed from npm as
@deeeed/metamask-harness; the MetaMask-specific layer lives here.
depends on ↓
runs recipes from ↓
farmslot packages
The recipe protocol and the execution engine, as pinned by mm-harness.
recipe-harness depends on protocol.
@farmslot/protocol0.18.0@farmslot/recipe-harness0.14.0@farmslot/agent-runtime0.7.0@farmslot/handoff0.3.1@farmslot/expo-recipe0.7.1
Recipe libraries
One per team, pointed at with RECIPE_LIBRARY_PATH, resolved ahead of the small
bundled MetaMask library. Perps is the worked example.
drives ↓
Product repos
The real builds a recipe drives. Each also installs the skills — every one of the three has a
skills script running metamask-skills sync.
promoted learnings, via @farmslot/handoff ↓
Learnings inbox
Scrubbed learning packages staged from finished runs, for later review. A terminal mark stages locally; sharing centrally is a separate, explicit step.
github.com/MetaMask/experimental-distributed-learnings private
Standing disclosure
The farmslot control plane is experimental and sole-maintained. What is adopted here is the spec and the engine — the npm packages above — not the control plane. Weigh that before depending on anything beyond them.