CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

kiro-steering-custom

Create custom steering documents for specialized project contexts

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tools/cc-sdd/templates/agents/codex-skills/skills/kiro-steering-custom/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body delivers concrete, well-structured guidance with specific paths, templates, and examples, but it is weakened by a dangling reference to a nonexistent rules/steering-principles.md file, redundant framing sections, and validation steps that are relegated to a fallback section instead of the workflow. Tightening the padding and adding an explicit verify step would lift it materially.

Suggestions

Fix the dangling reference: either bundle rules/steering-principles.md (e.g., under references/) or rely solely on the inlined principles summary and remove the four repeated pointers to it.

Add an explicit validation step to the workflow (e.g., "Verify the generated file: 100-200 lines, one domain only, no duplication of core steering, no secrets") before reporting completion.

Trim the <background_information> Role/Mission/Success Criteria block and the duplicated granularity guidance (stated in both the workflow and Steering Principles sections) to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly efficient bullet-style guidance, but the <background_information> block (Role/Mission/Success Criteria) is padding, the 100-200-line target and "patterns not lists" are stated twice, and "rules/steering-principles.md" is referenced four-plus times. It could be tightened without losing clarity, matching 'mostly efficient but includes some unnecessary explanation'.

3 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: exact paths ("{{KIRO_DIR}}/settings/templates/steering-custom/{name}.md", "{{KIRO_DIR}}/steering/{name}.md"), seven named templates, a 100-200 line target, tool mappings, a copy-ready output template, and worked examples. Minor gap: no sample snippet of a generated steering document.

4 / 5

Workflow Clarity

A clear numbered 5-step sequence exists (ask user, check template, analyze codebase with parallel research, generate, create file), but validation checkpoints are missing from the flow — the only checks ("Ensure doesn't duplicate core steering content", "Review and customize") live in the Safety & Fallback and output sections rather than as explicit workflow steps. This matches 'steps listed but validation gaps'.

3 / 5

Progressive Disclosure

The body has decent section structure and sensibly inlines the key steering principles, but it repeatedly points to "rules/steering-principles.md" from this skill's directory, and no bundle files (references/, scripts/, assets/) actually exist — a dangling reference an agent would fail to load. This fits 'some structure but could be better organized; references present but not clearly signaled'.

3 / 5

Total

13

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and names a clear domain with one concrete action, but it omits any 'when to use' trigger guidance, which caps its usefulness for skill routing. Adding a 'Use when...' clause with natural trigger terms would substantially improve completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to create steering/convention documents for topics beyond core files (e.g., API standards, testing, security)."

Include natural synonyms users would say — "conventions", "standards", "guidelines", "project memory" — alongside "steering documents".

Mention the concrete sub-actions performed (analyze codebase patterns, load a template, generate the file) to raise specificity.

DimensionReasoningScore

Specificity

"Create custom steering documents for specialized project contexts" names the domain clearly and one concrete action (create), matching the 'names domain and 1-2 concrete actions' anchor. It is not a 4 because it lists no additional actions (no analyze, document, or customize verbs) leaving coverage incomplete.

3 / 5

Completeness

The 'what' is clear (create custom steering documents), but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not a 2 because the 'what' is concrete rather than vague.

3 / 5

Trigger Term Quality

"steering documents", "custom", and "specialized project contexts" are relevant keywords a Kiro user might say, but the description misses common variations such as "conventions", "standards", "guidelines", or "project memory" that the body itself uses. It fits 'some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

"custom" and "specialized project contexts" distinguish it from core steering-file skills, leaving only minor overlap risk with a closely related steering skill. Not a 5 because the description offers no distinct trigger phrases to fully separate it from siblings.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

gotalab/cc-sdd

Path

tools/cc-sdd/templates/agents/codex-skills/skills/kiro-steering-custom/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.