forge
Clone forge-starter
Humansprovide judgment
Agentsprovide leverage
One doorthe same CLI, typed or driven by a skill

Agents are teammates

technical Buildertypes the verbnon-technical Buildersays what they wantforge CLI52 verbs · one HTTP clientClaude Code + the starter's skills◆ skill → ./forge <verb> · the same CLIthe runtimevalidate · permission · policyexecute · auditPOST /capabilities/:slugsame requestsame requestResourceEventsDifferent expertise. One identity: Builder. One door.
Both lanes end in the same request. The skill knows each capability's schema, plane, Resource and Events, so a non-technical Builder never sees a flag.
Who is acting

The CLI runs inside your project's control-plane container and asserts its actor over loopback. A skill inherits exactly that boundary because it runs ./forge in your project — no separate agent credential, no connector, nothing to expose.

What a skill knows

For each capability: the exact ./forge verb and flags, the one-line JSON it prints, the status values to branch on, and the Resource and Events it leaves. It reports back in those, never in logs.