kata-setup
SkillAI & modelsUse when the user asks to install Kata, set up Kata CLI, connect Kata to an agent harness, or check initial Kata configuration.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the kata-setup skill
What this skill tells your AI
The instructions your AI receives, as published by gannonh/kata-symphony in apps/cli/skills/kata-setup/SKILL.md and read by ahel’s review.
Operating Brief
When this skill is invoked, help the user make Kata usable in the current harness and repository.
If the skill is already installed, use the local wrapper for setup and health checks. Explain only the concrete next fix when setup is blocked.
This skill does not initialize project state. It only verifies that the runtime, skill installation, and backend configuration are ready for the requested Kata workflow.
Success Criteria
- The user knows whether Kata is ready in this harness.
- Runtime health has been checked with
node ./scripts/kata-call.mjs health.checkwhen the wrapper is available. - Any blocking setup issue is stated with the exact next action.
- No project, milestone, slice, task, or artifact state is created.
Do Not
- Do not create or modify project artifacts.
- Do not continue into planning or execution if setup is blocked.
- Do not inspect helper scripts unless the helper command itself fails.
- Do not invent backend-specific setup steps outside the CLI contract.
Process
- Read
references/workflow.mdbefore taking action. Execute that workflow end-to-end. - Preserve every workflow gate: required checks, user confirmations, durable writes, status updates, and next-step routing.
- Before any backend IO, read
references/runtime-contract.mdand use only the operations listed there. - When the workflow tells you to create or read an artifact, use
references/artifact-contract.mdand the named template files. - If setup or backend readiness is uncertain, read
references/setup.mdbefore proceeding. - Read optional references only when the workflow calls for them or the current step needs them.
Resource Loading
Must read:
- Workflow:
references/workflow.md - Runtime IO contract:
references/runtime-contract.md
Read when needed:
- Setup and health checks:
references/setup.md - Alignment depth:
references/alignment.md - CLI command patterns:
references/cli-runtime.md - Artifact conventions:
references/artifact-contract.md - CLI helper:
scripts/kata-call.mjs - Artifact input helper:
scripts/kata-artifact-input.mjs
Execution Rules
- If setup or backend state is uncertain, start with
references/setup.md. - Choose alignment depth using
references/alignment.mdinside this workflow. - Follow
references/workflow.mdas the behavioral source for this skill. - Use only operations listed in
references/runtime-contract.mdfor backend IO. - Keep backend specifics in @kata-sh/cli adapters, never in skill logic.
Signals
- GitHub stars
- 63
- Forks
- 6
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
kata-setup- Source
- github.com/gannonh/kata-symphony