CtrlK
BlogDocsLog inGet started
Tessl Logo

kiro-spec-init

Initialize a new specification with detailed project description

52

Quality

58%

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/antigravity-skills/skills/kiro-spec-init/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 a well-organized, concise, and highly actionable instruction set with clear sequencing and sensible error fallbacks. Its main weakness is the underspecified feature-name generation step.

DimensionReasoningScore

Conciseness

The body is lean and free of concept over-explanation, with only minor trimmable phrasing (e.g., 'Ask as many questions as needed; do not fill in gaps with your own assumptions'), landing between anchors 4 and 5 at 4.

4 / 5

Actionability

Guidance is concrete and executable: exact template paths, explicit placeholder replacements, and specific file writes; the only gap is the unspecified feature-name generation algorithm, keeping it at anchor 4 rather than 5.

4 / 5

Workflow Clarity

Execution steps are a clearly numbered 1-5 sequence with conditional checkpoints (brief exists, uniqueness conflict) and a Safety & Fallback section for error recovery; this is not a destructive/batch operation so the cap does not apply, fitting anchor 4.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, needs no external references, and is organized into clear sections (Core Task, Execution Steps, Constraints, Output, Safety), meeting the simple-skill exception for anchor 5.

5 / 5

Total

17

/

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 single purpose but is thin: it lacks trigger phrases, a "Use when" clause, and any second concrete action. It is serviceable but generic within its skill family.

Suggestions

Add a "Use when..." clause naming natural trigger phrases (e.g., 'Use when starting a new spec, initializing a feature spec, or after /kiro-discovery').

Include one more concrete action beyond 'Initialize' (e.g., 'generate a feature name and scaffold spec.json + requirements.md from templates').

Use the natural term 'spec' alongside 'specification' so it matches how users actually phrase the request.

DimensionReasoningScore

Specificity

The description names the domain ("specification") but only offers a single minimal/generic action ("Initialize"), matching anchor 2 rather than anchor 3 which requires 1-2 concrete actions.

2 / 5

Completeness

There is a clear "what" ("Initialize a new specification with detailed project description") but no "when" guidance at all, so the missing-trigger cap locks it at anchor 3.

3 / 5

Trigger Term Quality

It uses the formal terms "specification" and "project description" but lacks the natural phrases users would say (e.g., "spec", "create a spec") and includes no "Use when" trigger, fitting anchor 2.

2 / 5

Distinctiveness Conflict Risk

"Initialize a new specification" is a somewhat specific niche but still overlaps with the broader kiro-spec-* family (requirements, tasks, design), matching anchor 3.

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
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.