Closing the intent-to-code chasm - specification-driven development with BDD verification chain
95
Does it follow best practices?
Validation for skill structure
iikit-core
skills/iikit-core/SKILL.md
Discovery
100%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 a well-crafted skill description that clearly articulates specific capabilities for IIKit project management and includes comprehensive trigger guidance. The description uses third person voice correctly, provides concrete actions, and the 'Use when...' clause covers multiple natural user scenarios. The IIKit-specific terminology makes it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Initialize an IIKit project', 'check feature progress', 'select the active feature', and 'display the workflow command reference'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (initialize project, check progress, select feature, display commands) AND when with explicit 'Use when...' clause covering multiple trigger scenarios (starting project, running init, checking status, switching features, looking up commands). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'starting a new project', 'running init', 'checking status', 'switching between features', 'available commands', 'phases'. Good coverage of variations including both technical ('init') and natural language ('starting a new project'). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'IIKit' as a specific tool/framework name, combined with domain-specific terms like 'feature progress', 'active feature', and 'workflow command reference'. Unlikely to conflict with generic project or command skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that demonstrates strong technical writing. It efficiently documents a complex multi-subcommand workflow with clear execution flows, explicit validation steps, and appropriate progressive disclosure to external references. The content respects Claude's intelligence while providing precise, actionable guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and structured lists to convey information without explaining concepts Claude already knows. No unnecessary padding or verbose explanations of basic concepts like git or bash. | 3 / 3 |
Actionability | Provides fully executable bash commands with exact paths, JSON output parsing instructions, and specific decision trees. Commands are copy-paste ready with Windows alternatives included. | 3 / 3 |
Workflow Clarity | Multi-step init process has clear numbered steps with explicit validation checkpoints (Step 5 validates PREMISE.md, Step 0 detects environment before proceeding). Auto-skip conditions and gates are clearly specified with feedback loops for validation failures. | 3 / 3 |
Progressive Disclosure | Well-organized with clear overview structure. References to external files (templates, references) are one level deep and clearly signaled with relative paths. Complex procedures like PRD seeding are appropriately delegated to separate reference files. | 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.