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.