tessl-labs/intent-integrity-kit
Closing the intent-to-code chasm - specification-driven development with BDD verification chain
94
Quality
94%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
iikit-00-constitution
skills/iikit-00-constitution/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 excels across all dimensions. It provides specific concrete actions, uses natural trigger terms developers would actually say, includes an explicit 'Use when...' clause with multiple scenarios, and carves out a distinct niche around project governance documentation that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create or update a CONSTITUTION.md', 'defines project governance', 'establishes coding standards, quality gates, TDD policy, review requirements, and non-negotiable development principles with versioned amendment tracking'. | 3 / 3 |
Completeness | Clearly answers both what (create/update CONSTITUTION.md with governance, standards, policies) AND when with explicit 'Use when...' clause listing five specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'project rules', 'coding standards', 'quality gates', 'TDD requirements', 'development principles'. These are terms developers naturally use when setting up project governance. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on CONSTITUTION.md and project governance specifically. The combination of 'CONSTITUTION.md', 'project governance', and 'versioned amendment tracking' creates a distinct identity unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%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 workflow sequencing and appropriate progressive disclosure. The main weakness is minor verbosity in scope definitions and some explanatory text that could be trimmed. Overall, it provides excellent guidance for a complex multi-step constitution creation process.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some redundancy (e.g., explaining what MUST/MUST NOT contain when Claude understands scope constraints). The step-by-step flow is necessary but could be tightened in places like the verbose bash command explanations. | 2 / 3 |
Actionability | Provides fully executable bash commands, specific file paths, concrete validation scripts, and copy-paste ready code blocks. Each step has explicit commands with exact syntax for both Unix and Windows environments. | 3 / 3 |
Workflow Clarity | Clear 13-step sequence with explicit validation checkpoints (steps 6-7), error handling (step 1-2 prerequisites), and feedback loops (re-validate until clean). Includes explicit ERROR conditions and recovery guidance. | 3 / 3 |
Progressive Disclosure | Well-structured overview with clear one-level-deep references to templates and reference files (phase-separation-rules.md, constitution-template.md, model-recommendations.md). Content appropriately split between main skill and supporting files. | 3 / 3 |
Total | 11 / 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.