SDK, MCP and hooks

Skills and actions

The current website catalogue contains 24 first-class public skills and 295 typed actions. Skills express user workflows; actions expose bounded engine operations through the registered schema.

Inspect the action’s workflow, state-change flag, task requirement, tools and worker routes. Use the live schema for invocation; examples on this website do not submit commands.

Tools and workers

The current source projection includes 103 retained tool/dependency assignments and 53 worker operations. These are catalogue counts, not a claim that all are installed or running.

Workers are owned operating-system processes for bounded tool work. They are not AI subagents.

Hooks are a separate track

Supported host events use registered capture stages. User-owned hook enablement is disabled by default. Captured events retain attribution; they do not authorize operations or prove a Plan task completed.

Keep host/client sessions, MCP transport, external tool providers and compute providers distinct. A transport connection is not a project connector grant.

Example: source_register

Purpose: register the authorized source selection. Inputs: the exact selected sources required by the typed contract. Result: attributed registration references. Boundary: registration does not execute prepared source work.