CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

90%

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

92%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.

An efficient, well-sequenced process skill: lean imperative steps, concrete lint commands and path resolution, explicit validation gates, and failure-routing feedback loops. The only minor weakness is that the memory-related steps ('search memory', 'store decisions in memory') are not backed by a concrete mechanism.

DimensionReasoningScore

Conciseness

The body is lean, imperative, and free of padding or explanations of concepts Claude already knows; even the densest step (option comparison criteria, signal ownership) is substantive guidance where every token earns its place.

5 / 5

Actionability

Provides concrete executable commands ('npx ai-devkit@latest lint --feature <name>', '.ai-devkit.json paths.docs falling back to docs/ai'), a specific red-flag screening list, and explicit comparison criteria; the 'search memory' and 'store decisions in memory' steps lack a concrete mechanism, leaving minor gaps.

4 / 5

Workflow Clarity

Thirteen numbered steps in coherent order with explicit validation checkpoints (lint before work, cross-check requirements coverage, 'Do not approve or transition past design while material open questions remain') and error-recovery routing ('If requirements gaps are found, return to dev-requirements').

5 / 5

Progressive Disclosure

A single-file skill under 50 lines with no bundle files, organized into two clearly scoped sections ('Phase Contract', 'Review Design'); per the simple-skill guideline this structure fully satisfies progressive disclosure.

5 / 5

Total

19

/

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 strong description with a clear niche, several concrete capabilities, and an explicit 'Use when' trigger clause. Trigger-term coverage could add common synonyms (e.g., 'design review'), but conflict risk within its dev-lifecycle family is low.

DimensionReasoningScore

Specificity

Names the domain ('reviewing feature design against requirements') and lists several concrete actions ('validate architecture', 'review design docs', 'resolve design trade-offs'), matching the several-specific-actions anchor; coverage of the full phase's activities is incomplete, so it falls short of comprehensive.

4 / 5

Completeness

Explicitly answers both 'what' (design-phase review of feature design against requirements) and 'when' via a concrete 'Use when the user wants to validate architecture, review design docs, resolve design trade-offs, or run dev-lifecycle phase 3' trigger clause, matching the top anchor.

5 / 5

Trigger Term Quality

'validate architecture', 'review design docs', and 'design trade-offs' are natural phrases users would say, but common synonyms like 'design review' or 'architecture review' are missing, placing it just below comprehensive keyword coverage.

4 / 5

Distinctiveness Conflict Risk

Scoped to 'AI DevKit' and 'dev-lifecycle phase 3' with design-specific triggers, creating a clear niche; minor overlap risk remains with sibling lifecycle skills like dev-requirements or dev-implementation.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

codeaholicguy/ai-devkit

Path

skills/dev-design/SKILL.md

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.