CtrlK
BlogDocsLog inGet started
Tessl Logo

dev-implementation

AI DevKit · Implementation phase guidance for executing feature plans and checking implementation against design. Use when the user wants to implement planned tasks, update implementation docs, verify code matches design, or run dev-lifecycle phases 5 and 7.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

A lean, well-structured instruction-only skill with concrete commands, explicit validation checkpoints, and clear phase sequencing. It assumes Claude's competence and avoids unnecessary explanation while remaining fully actionable.

DimensionReasoningScore

Conciseness

Dense, action-oriented numbered steps with no concept explanations Claude already knows and no padding; every line is an instruction that earns its place.

3 / 3

Actionability

Provides executable commands ('npx ai-devkit@latest lint --feature <name>'), concrete file paths, explicit task statuses, and specific tracing events; per the instruction-only scoring note, actionable concrete guidance earns the top score.

3 / 3

Workflow Clarity

Clear numbered sequences for each phase with an explicit lint validation gate and error-recovery routing ('If major deviations exist, return to dev-design... or Execute Plan'); this is not a destructive/batch/XML/db context, so no feedback-loop cap applies.

3 / 3

Progressive Disclosure

A self-contained, under-50-line skill with well-organized sections (Phase Contract, Execute Plan, Check Implementation) and no need for external references; per the simple_skills note this earns the top score.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%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.

A concise, third-person description with concrete actions and an explicit 'Use when' trigger clause that clearly answers both what and when. It is well-scoped to the AI DevKit implementation phase and unlikely to trigger for unrelated work.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'executing feature plans', 'checking implementation against design', 'update implementation docs', 'verify code matches design' — matching the score-3 anchor rather than the partial score-2.

3 / 3

Completeness

An explicit 'Use when...' clause answers both what (implementation phase guidance) and when (implement tasks, update docs, verify, run phases 5/7), matching the score-3 anchor.

3 / 3

Trigger Term Quality

Natural user phrasings like 'implement planned tasks', 'update implementation docs', and 'verify code matches design' give good coverage, even though 'dev-lifecycle phases 5 and 7' is jargon.

3 / 3

Distinctiveness Conflict Risk

Scoped to a specific tool and lifecycle phase with explicit phase numbers, giving a clear niche; minor sibling overlap with dev-review on 'verify code matches design' is mitigated by the implementation/execute framing.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
codeaholicguy/ai-devkit
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.