CtrlK
BlogDocsLog inGet started
Tessl Logo

dev-design

AI DevKit · Design phase guidance for reviewing feature design against requirements. Use when the user wants to validate architecture, review design docs, resolve design trade-offs, or run dev-lifecycle phase 3.

67

Quality

81%

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

78%Weight 40%Scale 1-5

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

A tight, well-structured instruction skill with concrete commands, an approval checkpoint, and clean sectioning. It lacks an explicit lint-failure feedback loop, which is the main gap keeping workflow clarity and actionability at 4.

Suggestions

Add an explicit feedback loop after the lint step, e.g. "If lint fails, fix the reported issues and re-run lint before proceeding."

Tighten the densest checklist items (e.g. the red-flags list in Review Design step 6) so each red flag reads as a single scannable cue.

Make the lint-validation tie-in in Review Design step 1 explicit about what to do on failure, not just that lint should run.

DimensionReasoningScore

Conciseness

The body is lean and imperative with no padding of concepts Claude already knows; a few dense checklist items could be tightened slightly, keeping it just below 5.

4 / 5

Actionability

Concrete commands ("npx ai-devkit@latest lint", "--feature <name>") and specific path-resolution steps (".ai-devkit.json paths.docs", fallback "docs/ai") are present, alongside actionable red-flag checklists, with only minor gaps.

4 / 5

Workflow Clarity

Two clearly numbered sequences (Phase Contract 1-8, Review Design 1-13) with a lint validation checkpoint and an approval gate; an explicit validate-fix-retry feedback loop is absent, capping it at 4.

4 / 5

Progressive Disclosure

Under 50 lines with no external references needed, and well-organized into clear sections (Phase Contract, Review Design, Next), which qualifies for 5 under the simple-skill exception.

5 / 5

Total

17

/

20

Passed

Description

83%Weight 40%Scale 1-5

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 well-constructed description that explicitly answers both what and when with concrete trigger phrases. Specificity and trigger coverage are strong but stop just short of comprehensive due to slightly abstract actions and jargon.

DimensionReasoningScore

Specificity

Lists several concrete actions — "validate architecture, review design docs, resolve design trade-offs, run dev-lifecycle phase 3" — but the actions are review-flavored and somewhat abstract, so minor coverage gaps keep it below 5.

4 / 5

Completeness

Clearly states what ("Design phase guidance for reviewing feature design against requirements") and an explicit "Use when..." clause with concrete trigger phrases, matching the 5 anchor.

5 / 5

Trigger Term Quality

Natural phrases like "validate architecture", "review design docs", and "resolve design trade-offs" are present, but "dev-lifecycle phase 3" is jargon and synonym/extension coverage is missing.

4 / 5

Distinctiveness Conflict Risk

The "AI DevKit · Design phase" niche and phase-3 anchoring make it mostly distinct, though generic design-review triggers could overlap with closely related skills.

4 / 5

Total

17

/

20

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.