CtrlK
BlogDocsLog inGet started
Tessl Logo

iikit-01-specify

Create a feature specification from a natural language description — generates user stories with Given/When/Then scenarios, functional requirements (FR-XXX), success criteria, and a quality checklist. Use when starting a new feature, writing a PRD, defining user stories, capturing acceptance criteria, or documenting requirements for a product idea.

83

1.74x
Quality

92%

Does it follow best practices?

Impact

82%

1.74x

Average score across 14 eval scenarios

SecuritybySnyk

—

The risk profile of this skill

The canonical home for this skill is tessl-labs/intent-integrity-kit

SKILL.md
Quality
Evals
Security

Quality

Content

85%Scale 1-3

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

This is a well-structured, highly actionable skill with clear multi-step workflow, explicit validation checkpoints, and good progressive disclosure through external references. The main weakness is mild verbosity in the bug-fix detection section and some explanatory text that could be tightened. Overall it's a strong skill that provides concrete, executable guidance for a complex multi-step specification process.

DimensionReasoningScore

Conciseness

Generally efficient but includes some unnecessary explanation, particularly in the Bug-Fix Intent Detection section which over-explains the distinction between bug-fix and feature contexts. The guidelines section restates things that are implicit from the template/workflow. However, most content earns its place.

2 / 3

Actionability

Provides fully executable bash/powershell commands, specific file paths, concrete examples for branch naming, clear JSON parsing instructions, and exact commit commands. The workflow is copy-paste ready with platform-specific variants.

3 / 3

Workflow Clarity

Clear numbered sequence (Steps 0-7) with explicit validation checkpoints: Phase Separation Validation (Step 4) with auto-fix and re-validate loop, Quality Checklist generation (Step 5), Semantic Diff on re-run with confirmation before overwriting. Includes feedback loops for clarifications (Step 6) and error recovery patterns.

3 / 3

Progressive Disclosure

Excellent use of one-level-deep references to external files: constitution-loading.md, spec-template.md, phase-separation-rules.md, formatting-guide.md, model-recommendations.md. The main skill stays as an overview/workflow while detailed content lives in referenced files. Navigation is clearly signaled with relative paths.

3 / 3

Total

11

/

12

Passed

Description

100%Scale 1-3

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

This is an excellent skill description that clearly articulates specific deliverables (user stories, functional requirements, success criteria, quality checklist), includes a comprehensive 'Use when...' clause with multiple natural trigger scenarios, and occupies a distinct niche in product/requirements documentation. It uses proper third-person voice and is concise without being vague.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: generates user stories with Given/When/Then scenarios, functional requirements (FR-XXX), success criteria, and a quality checklist. These are precise, well-defined deliverables.

3 / 3

Completeness

Clearly answers both 'what' (create feature specs with user stories, functional requirements, success criteria, quality checklist) and 'when' with an explicit 'Use when...' clause listing five distinct trigger scenarios.

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'feature specification', 'user stories', 'PRD', 'acceptance criteria', 'requirements', 'product idea', 'Given/When/Then'. These cover a wide range of natural phrasings a user might employ.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche — feature specification and requirements documentation — with distinct triggers like 'PRD', 'Given/When/Then', 'FR-XXX', and 'acceptance criteria' that are unlikely to conflict with other skills.

3 / 3

Total

12

/

12

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
JaviMontano/mao-iic
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.