// Design or review Takt actions. Use when working on project-local configured uses of capabilities, including defaults, secret bindings, labels, and ownership metadata.
Design or review a Takt package manifest. Use when working on capabilities, the package Node version, handlers, schemas, or registry-facing package structure.
Interactive getting-started walkthrough for new Takt users. Guides through inspecting the package, understanding the core nouns, scaffolding a first action or workflow, and validating the result. Triggers on "getting started", "new to takt", "first time", "walkthrough", "onboarding", "quickstart", "how do I start", "what do I do first", "learn takt", or whenever the user needs the package, capability, action, and workflow model explained before deeper work.
Design or review Takt workflows. Use when working on orchestration, dependencies, and step wiring across actions.
| name | takt-action |
| description | Design or review Takt actions. Use when working on project-local configured uses of capabilities, including defaults, secret bindings, labels, and ownership metadata. |
Actions are project-local configured uses of capabilities.
This skill is a routing guide. Treat takt schema action --format toon and the action manifest as the source of truth.
takt generate action <name> <capability> first, then edit the generated JSON.takt validate action <name-or-path> --format toon.takt run action <name> --format toon.| Task | Command |
|---|---|
| Get action schema | takt schema action --format toon |
| Generate action | takt generate action <name> <capability> |
| Validate action | takt validate action <name-or-path> --format toon |
| Plan action run | takt run action <name> --format toon |
takt generate action <name> <capability>.actions/.takt schema action --format toon.takt validate action <name-or-path> --format toon.Use takt generate action <name> <capability> to scaffold an action manifest,
then edit the generated JSON.