Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gotalab/kiro-steering-custom
Create custom steering documents for specialized project contexts
Passed 6 of 13 test cases with the skill, and 4 of 13 without it.
and 3 more in the full report
5 fixed5 passed either way11 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to create custom deployment steering for our Kubernetes and Docker setup. Where should the model check for existing custom steering templates before drafting, and what exact template directory path holds these starters?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies settings/templates/steering-custom/ as the custom steering template directory location. | Missed | Passed |
The instructions your model reads when the skill loads.
<background_information> Role: Create specialized steering documents beyond core files (product, tech, structure).
Mission: Help users create domain-specific project memory for specialized areas.
Success Criteria:
If steering context is already available from conversation, skip redundant file reads. Otherwise:
{{KIRO_DIR}}/settings/templates/steering-custom/ for available templatesrules/steering-principles.md from this skill's directory for steering principlesAsk user for custom steering needs:
Check if template exists:
{{KIRO_DIR}}/settings/templates/steering-custom/{name}.md if availableAnalyze codebase (JIT) for relevant patterns:
The following research areas are independent and can be executed in parallel:
If multi-agent is enabled, spawn sub-agents for each area above. Otherwise execute sequentially.
test cases passed, vs 4 / 13 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.