kiro-steering

Manage {{KIRO_DIR}}/steering/ as persistent project knowledge

Quality

51%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tools/cc-sdd/templates/agents/antigravity-skills/skills/kiro-steering/SKILL.md

Quality

Content

61%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 content is well-structured and actionable with clear bootstrap/sync workflows, but suffers from thematic repetition, a disrupted Bootstrap numbered list, and a missing referenced bundle file (rules/steering-principles.md). Tightening redundancy and fixing the list structure would raise workflow clarity and conciseness.

Suggestions

State the "patterns not catalogs" principle once (e.g. in the Granularity Principle section) and remove its repetition in Mission, Bootstrap Focus, and Notes to improve conciseness.

Restructure the Bootstrap flow so the Parallel Research sub-list does not collide with the outer 1-6 numbering (e.g. make "Analyze codebase" a parent step with lettered sub-steps), and add an explicit validation/review checkpoint before generating files.

Either include the referenced rules/steering-principles.md bundle file or remove the reference to it, and link it explicitly (e.g. [steering-principles.md](rules/steering-principles.md)) so progressive disclosure navigation is clear.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and well-structured, but the "patterns not catalogs" message is repeated across Mission, Bootstrap Focus, the Granularity Principle, and Notes, which is tightening-eligible padding; this fits "mostly efficient but includes some unnecessary explanation" and stops short of 4 because the redundancy could be removed.	3 / 5
Actionability	Concrete numbered steps, specific load paths (templates, steering/*.md), explicit scenario detection rules, and a named toolset (Glob/Read/Grep/Bash) give mostly executable guidance with minor abstraction gaps ("Extract patterns (not lists)"); it is not 5 because some guidance like "Analyze codebase (JIT)" stays high-level without concrete commands.	4 / 5
Workflow Clarity	Bootstrap and Sync flows are sequenced with a user-review checkpoint, but the Bootstrap numbered list is disrupted by the nested "#### Parallel Research" subsection with its own 1-2-3 list, making the outer 1-6 sequence incoherent, and there is no explicit validation that generated steering is correct; this matches "steps listed but validation gaps; checkpoints missing or implicit."	3 / 5
Progressive Disclosure	The body is organized into clear one-level sections (Scenario Detection, Bootstrap, Sync, Granularity, Tool guidance, Output, Examples, Safety, Notes) with signaled external references to templates and steering-principles.md; it is not 5 because the referenced skill-bundle file rules/steering-principles.md is not present in the bundle and navigation to it is a bare path rather than a link.	4 / 5
	Total	14 / 20 Passed

Description

41%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 identifies a specific niche but relies on a single generic verb and omits any explicit trigger guidance, capping completeness. Adding concrete actions (bootstrap, sync, drift detection) and a "Use when..." clause would materially improve it.

Suggestions

Add concrete actions, e.g. "Bootstrap, sync, and detect drift in {{KIRO_DIR}}/steering/ files as persistent project knowledge."

Append an explicit trigger clause: "Use when setting up steering docs for a new project or keeping steering files aligned with codebase changes."

Include natural synonyms users might say (e.g. "steering docs", "project memory", "steering files") to improve trigger term quality.

Dimension	Reasoning	Score
Specificity	The description names the domain ("steering/" as "persistent project knowledge") but the only action is the generic verb "Manage", matching the anchor where the domain is named but actions are minimal or generic; it does not reach 3 because no concrete actions like "bootstrap", "sync", or "detect drift" are stated.	2 / 5
Completeness	It gives a clear "what" (manage steering/ as persistent project knowledge) but entirely lacks a "when"/"Use when..." clause, so per the cap guidance a missing explicit trigger clause holds completeness at 3 rather than 4.	3 / 5
Trigger Term Quality	The only candidate keyword is "steering", which is product-specific jargon rather than a natural phrase users say, and there are no synonyms or variations; this matches the anchor of one or two generic keywords missing the natural phrases users say, and falls short of 3 which expects relevant everyday keywords.	2 / 5
Distinctiveness Conflict Risk	The {{KIRO_DIR}}/steering/ niche is fairly distinct and unlikely to fire for unrelated skills, matching "mostly distinct; minor overlap risk"; it does not reach 5 because the generic verb "Manage" and absence of concrete triggers leave some overlap risk with general project-knowledge skills.	4 / 5
	Total	11 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: gotalab/cc-sdd
Path: tools/cc-sdd/templates/agents/antigravity-skills/skills/kiro-steering/SKILL.md
Commit: e2a0c67

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.