tuist Takt Action
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.
Critical Rules
- Never write an action manifest from scratch. Always run
takt generate action <name> <capability>first, then edit the generated JSON. - Never use an action to smuggle implementation that belongs in a capability handler.
- Always validate after edits with
takt validate action <name-or-path> --format toon. - If execution behavior matters, inspect the plan with
takt run action <name> --format toon.
Quick Reference
| 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 |
Responsibilities
- bind a capability reference
- provide default inputs
- bind secret sources
- attach labels and ownership metadata
Review Flow
- If creating a new action, scaffold it first with
takt generate action <name> <capability>. - Read the relevant file under
actions/. - Run
takt schema action --format toon. - Run
takt validate action <name-or-path> --format toon. - Confirm the action is configuration, not implementation.
Rules
- Workflows call actions, not capabilities.
- Actions should hold project-specific configuration, not distributable code.
- Secret bindings should stay declarative.
- Prefer existing capabilities over inventing a new one just to fit a single action.
Current Command
Use takt generate action <name> <capability> to scaffold an action manifest,
then edit the generated JSON.
Smells
- actions embedding large script bodies
- actions duplicating package logic
- actions bypassing capability permissions