CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

kiro-spec-status

Show specification status and progress

Quality

65%

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-spec-status/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 body is an efficient, well-sequenced, read-only status workflow with concrete file paths, parsing rules, and fallback handling. Its main weaknesses are minor redundancy between the success criteria and report sections, and a few analysis steps (revalidation watchlist, boundary context) that describe intent without specifying how to execute it.

DimensionReasoningScore

Conciseness

The body is lean, all directive bullets with no concept explanations, but the success-criteria block ("Identify next actions and blockers", "Surface boundary readiness...") duplicates the Step 3 report contents and could be trimmed.

4 / 5

Actionability

Concrete file paths ({{KIRO_DIR}}/specs/$1/spec.json), exact parsing rules ("- [x]" vs "- [ ]"), and verbatim fallback messages make the guidance mostly executable; gaps like "Identify downstream specs... that may need revalidation" lack a concrete method.

4 / 5

Workflow Clarity

A clear three-step sequence (load context, analyze, report) with conditional "if it exists" reads and error-scenario fallbacks; minor gaps remain, such as how completion percentages are computed and what spec.json fields hold phase status.

4 / 5

Progressive Disclosure

A self-contained single-purpose skill with well-organized sections (background, execution steps, safety & fallback) and no bundle files to reference; it slightly exceeds the under-50-line simple-skill threshold and uses XML-style tags rather than plain markdown headers.

4 / 5

Total

16

/

20

Passed

Description

37%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 states a clear 'what' but is terse to a fault: no trigger guidance, no concrete capability enumeration, and only generic keywords. Users asking about spec progress would be unlikely to match this description naturally.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about spec status, progress, what phase a spec is in, or what to do next on a spec."

Enumerate concrete capabilities so the 'what' is comprehensive: current phase, completion percentages, completed/remaining task counts, boundary context, revalidation watchlist, next actions, and blockers.

Include natural synonyms such as "spec" alongside "specification" and mention report-related trigger phrases users would actually say.

DimensionReasoningScore

Specificity

"Show specification status and progress" names the domain but relies on a single generic action ("show"), matching the 'Processes PDF files' anchor rather than the 1-2 concrete actions of anchor 3.

2 / 5

Completeness

The 'what' is clear (show status and progress of specifications) but there is no 'when' clause or equivalent trigger guidance at all, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

The only keywords are "specification", "status", and "progress" — the latter two generic — and natural phrases users would actually say ("spec status", "check spec progress", "how far along") are missing, as is the common "spec" variation.

2 / 5

Distinctiveness Conflict Risk

"specification" gives it a niche, but "status and progress" is generic and would overlap with sibling spec-workflow skills (e.g. a spec-tasks or spec-validate skill in the same toolset).

3 / 5

Total

10

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

gotalab/cc-sdd

Path

tools/cc-sdd/templates/agents/codex-skills/skills/kiro-spec-status/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.