tessl-labs/intent-integrity-kit
Closing the intent-to-code chasm - specification-driven development with BDD verification chain
Overall
score
96%
Does it follow best practices?
Validation for skill structure
iikit-07-analyze
skills/iikit-07-analyze/SKILL.md
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes natural trigger terms users would actually say, explicitly addresses both what and when, and carves out a distinct niche around cross-artifact consistency validation. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'checks that every spec requirement traces to tasks', 'plan tech stack matches task file paths', and 'constitution principles are satisfied across all artifacts'. These are precise, verifiable operations. | 3 / 3 |
Completeness | Clearly answers both what (validate cross-artifact consistency with three specific checks) AND when (explicit 'Use when...' clause listing four trigger scenarios: consistency check, requirements traceability, detecting conflicts, auditing alignment). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'consistency check', 'requirements traceability', 'conflicts between design docs', 'auditing alignment', 'spec requirement', 'tech stack'. Good coverage of domain-specific but user-accessible terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche focused on cross-artifact validation and requirements traceability. The combination of 'spec requirements', 'task file paths', 'constitution principles', and 'design docs' creates a distinct trigger profile unlikely to conflict with general document or code skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%This is a well-crafted skill with excellent actionability and workflow clarity. The multi-step analysis process is clearly sequenced with validation gates, specific detection criteria, and concrete output formats. Minor verbosity in operating principles and repeated platform-specific command patterns slightly reduce token efficiency, but overall the skill provides comprehensive, executable guidance.
Suggestions
Consolidate Windows/bash command pairs into a single pattern reference or table at the top to reduce repetition throughout the document
Remove or significantly trim the 'Operating Principles' section as it restates behaviors Claude already exhibits (minimal tokens, no hallucination, prioritization)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly efficient but includes some redundancy (e.g., repeated Windows/bash command pairs throughout, verbose section headers). Some sections like 'Operating Principles' restate concepts Claude already knows about being minimal and not hallucinating. | 2 / 3 |
Actionability | Highly actionable with specific executable commands, exact file paths, concrete detection categories with precise criteria, and copy-paste ready bash/PowerShell scripts. The scoring formula and JSON schema are explicit and implementable. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with clear sequencing (prerequisites → load → build models → detect → report → persist). Includes explicit validation checkpoints (checklist gate, re-run prerequisites after selection) and feedback loops (CRITICAL issues block progression, remediation offered). | 3 / 3 |
Progressive Disclosure | Well-structured with clear references to external files (constitution-loading.md, conversation-guide.md, checklist-gate.md, phase-separation-rules.md, model-recommendations.md) that are one level deep and clearly signaled. Main content stays focused on the workflow. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.