agentproto

Walk through authoring a portable WORKFLOW.md manifest plus a defineWorkflow / defineStep entry for any agent runtime. Covers branching, parallelism, suspend/resume, approval gates, and compensation.

Walk through authoring a portable canvakit template — frontmatter identity, variables, sources (tool/static/file/query), imports, designkit binding, validation. Produces a `<name>.canvakit.<ext>` file plus an optional `defineCanvas` entry.

Walk through authoring a portable TOOL.md abstract contract — the agent's view of a single operation's identity, schemas, side-effect profile, and approval class. Implementation lives on a sibling AIP-30 DRIVER.md; this skill optionally chains into the author-driver skill afterwards.

Walk through drafting a new AIP — from picking a number through writing the spec body, generating the resources folder, and submitting for discussion.

Walk through filling the AIP-2 template — required frontmatter, section ordering, MUST/SHOULD/MAY discipline — once you've decided to author a new AIP.

Walk an adapter implementer through importing the `runner` block (engine, image, needs, limits) and the `defineRunner` standard signature into a new AIP manifest format.

Walk through authoring a SECRETS.md inventory — slugs, access grants, audit metadata — for a workspace whose tools and workflows need third-party credentials. Values stay in the vault; the manifest is metadata only.

Walk through authoring a portable DRIVER.md manifest — the abstract supertype that wraps a concrete implementation (CLI binary, HTTP API, MCP server, SDK package, or host builtin) and binds it to one or more abstract TOOL.md contracts.

Walk through authoring a kind:http DRIVER.md — wraps a third-party HTTP API (OpenAI / Stripe / Replicate / GitHub / Anthropic / etc.) as a conformant driver implementing one or more abstract TOOL contracts.

Walk through authoring a kind:mcp DRIVER.md — wraps a Model Context Protocol server (Anthropic-spec) as a conformant driver implementing one or more abstract TOOL contracts.

Walk through authoring a kind:sdk DRIVER.md — wraps an in-process SDK package (npm / pip / cargo / go / workspace-local) as a conformant driver implementing one or more abstract TOOL contracts.

Walk through writing a knowledge.workspace/v1 manifest — either the canonical root for a new wiki or a per-context view that extends a parent manifest — using the defineKnowledgeWorkspace canonical signature.

Walk through writing, linking, and linting curated wiki entries on top of immutable raw sources, using the standard defineEntry / defineSource signatures.

Walk through authoring a portable LESSON.md — one transferable lesson distilled from a completed run — plus the optional defineLesson entry that wires it into a runtime's lesson bank.

Walk through authoring a portable PLAYBOOK.md prompt-overlay fragment plus a definePlaybook entry for any agent runtime. Covers applicability, locked-trait safeguards, the reflective delta contract, and the shadow → active promotion gate.

Walk through authoring a portable agentwork/v1 doctype — project, initiative, or task — with a unified scope vocabulary that keeps containment, applicability, and ownership as three orthogonal axes.

Walk an adapter implementer through importing the four IO blocks (`inputs`, `outputs`, `inputsFiles`, `outputsFiles`) and the `defineIO` standard signature into a new AIP manifest format.

Walk through writing a collection.schema/v1 manifest — either a fresh collection or a child that extends a parent — using the defineCollection canonical signature, then optionally produce conforming collection.item/v1 instances.

Walk through writing a work.workspace/v2 manifest — either the canonical root for a new tracker or a per-context view that extends a parent — using the defineWorkWorkspace canonical signature, with explicit one-way-switch checks before validation.

Walk through writing an agency.workspace/v2 manifest — either the canonical root for a new commercial agency or a per-context view that extends a parent — using the defineAgencyWorkspace canonical signature, with explicit one-way-switch checks across signing, audit, scope, and contract before validation.

Walk through writing a office.workspace/v1 manifest — either the canonical root for a new organisation or a per-context view that extends a parent — using the defineOfficeWorkspace canonical signature, with explicit one-way-switch checks before validation.

Walk through writing an identity.workspace/v1 manifest — either the canonical root for a new identity or a per-context view (per-operator, per-locale, per-persona) that extends a parent — using the defineIdentityWorkspace canonical signature, with explicit one-way-switch checks before validation.

Walk through writing an assembly.workspace/v1 manifest — a multi-agent collective in advisory / voting / peer / hierarchy mode — using the defineAssemblyWorkspace canonical signature, with explicit mode-selection, member-roster authoring, synthesis-rule selection, locked-trait union semantics, and four one-way-switch checks before validation.

Walk through authoring a portable PERSONA.md manifest for a single agent persona — identity, backstory, voice, boundaries, locale, relationships, cross-AIP bindings, and body prose. The persona is the public face of an agent (name, voice, lore, refusals); inner behavioural substance belongs in an AIP-23 identity workspace, not here. This skill IS itself a valid AIP-3 skill — eat the dogfood.

Walk an adapter implementer through importing the `code` and `run` blocks and the `defineCode` standard signature into a new manifest format that needs explicit bundle identity and entry-point declaration.

Walk through authoring a portable INTENT.md manifest plus an optional defineIntent entry — the user-facing operation manifest that routes to one or more tools.

Walk through authoring a portable CLI.md bundle plus the per-subcommand TOOL.md siblings that make up the bundle's invocable surface.

Walk through authoring a portable SKILL.md manifest plus optional defineSkill entry for any agent runtime. Covers identity, capabilities, inputs, install location, and validation. This skill IS itself a valid AIP-3 skill — eat the dogfood.

Walk through authoring a portable DESIGN.md design-token kit with colors, typography, spacing, radius, and motion, plus the registry metadata required to publish to designkit.sh.

Walk through producing a valid agentcompanies/v1 workspace — COMPANY.md plus role and objective doctypes — with cross-references resolved and validated.

Walk through authoring AIP-7 governance files — approvals, append-only audit entries, and policy rules — for any agent runtime.

Walk through writing a governance.workspace/v1 manifest — either the canonical root for a new governance scope or a per-context view that extends a parent manifest — using the defineGovernanceWorkspace canonical signature. Enforces the one-way switches (audit.appendOnly, signing.required) that no descendant view may relax.

Walk through authoring a portable agentagencies/v1 workspace — services, procedures, engagements, agreements, deliverables, invoices — that any conforming runtime can ingest and execute.

Walk through authoring a portable OPERATOR.md manifest plus a defineOperator entry that turns the canonical operator shell into a runnable agent on any conforming runtime.