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-08-taskstoissues
skills/iikit-08-taskstoissues/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 follows best practices. It uses third person voice, specifies concrete actions (converting tasks, adding labels/dependencies), and includes an explicit 'Use when...' clause with multiple natural trigger scenarios. The description clearly distinguishes itself by focusing on the specific tasks.md to GitHub Issues workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Convert tasks from tasks.md into GitHub Issues', 'with labels and dependencies', 'exporting work items', 'setting up project boards', 'assigning tasks to team members'. | 3 / 3 |
Completeness | Clearly answers both what ('Convert tasks from tasks.md into GitHub Issues with labels and dependencies') AND when ('Use when exporting work items to GitHub, setting up project boards, or assigning tasks to team members'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'tasks.md', 'GitHub Issues', 'labels', 'dependencies', 'project boards', 'assigning tasks', 'team members', 'exporting work items'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche with distinct triggers - specifically targets tasks.md to GitHub Issues conversion, unlikely to conflict with general task management or generic GitHub skills due to the specific workflow described. | 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 a high-quality skill that efficiently guides Claude through a complex multi-step workflow for converting tasks to GitHub issues. It excels at providing concrete, executable commands with both Unix and Windows variants, includes proper validation checkpoints, and handles error cases explicitly. The structure is clean with appropriate progressive disclosure to external references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, assuming Claude's competence with GitHub, git, and shell commands. No unnecessary explanations of basic concepts; every section serves a clear purpose. | 3 / 3 |
Actionability | Provides fully executable bash/PowerShell commands, specific title formats, concrete examples like `gh issue create`, and clear templates. Copy-paste ready with both Unix and Windows variants. | 3 / 3 |
Workflow Clarity | Clear numbered sequence with explicit validation checkpoints (GitHub remote validation, prerequisites check, verify subagent returns). Error handling table provides explicit recovery paths for partial failures. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections. References external files appropriately (conversation-guide.md, issue-body-template.md) at one level deep with clear signaling. Content is appropriately split between overview and referenced materials. | 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.