CtrlK
BlogDocsLog inGet started
Tessl Logo

plugin-craft

Design and restructure Claude Code plugins. Use when applying the five restructure principles, adding agents, or packaging a plugin. It does not write a kit SKILL.md (that's `skill-craft`).

66

Quality

80%

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

77%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 exemplary progressive-disclosure and workflow-structured lifecycle skill with explicit validation loops and concrete commands. Its main weakness is conciseness: the body runs past its self-imposed 200-line budget with some redundant motivational prose.

Suggestions

Trim the body to ≤200 lines by cutting motivational prose (e.g., "Internalize these before you write a single line", "This skill itself follows the model it teaches") and consolidating the three dora mentions into one canonical block referenced from the checklist and phase gates.

Since the 5 principles are fully expanded in references/restructure-best-practices.md, consider shrinking the inline numbered list to a one-line summary plus the load call rather than restating all five.

Move the doraval gate's step-by-step commands into a short references file (or the installed doraval skill) and keep only the exit-code contract inline to reduce repeated token cost.

DimensionReasoningScore

Conciseness

Mostly efficient thanks to load-blockquote delegation, but the 210-line body exceeds its own 200-line cap and carries mild motivational padding ("Internalize these before you write a single line", "This skill itself follows the model it teaches").

3 / 5

Actionability

Concrete commands ("claude --plugin-dir", "dora review <path> --format json", "npx @hacksmith/doraval"), a real directory tree, and four numbered workflows give mostly executable guidance, with copy-paste specifics like the frontmatter template deferred to references.

4 / 5

Workflow Clarity

Multi-step processes are clearly sequenced with phase gates, a quality checklist, and an explicit dora validation feedback loop (review → fix → re-review until exit 0) with error-recovery guidance.

5 / 5

Progressive Disclosure

The body is a lean overview that signals one-level-deep references via consistent "> For ... load references/xxx.md" blockquotes; all five referenced files exist and are self-contained terminal documents, giving easy navigation.

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 strong, third-person description with an explicit Use-when clause and concrete triggers covering the full plugin lifecycle. Minor room to add synonyms and disambiguate more sibling craft skills.

DimensionReasoningScore

Specificity

Lists several concrete actions across the plugin lifecycle — "Design and restructure", "applying the five restructure principles", "adding agents", "packaging a plugin" — with only minor gaps in granularity.

4 / 5

Completeness

Explicitly answers both what ("Design and restructure Claude Code plugins") and when ("Use when applying the five restructure principles, adding agents, or packaging a plugin") with three concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases a user would say appear ("restructure", "adding agents", "packaging a plugin"), but common synonyms like "build"/"create"/"refactor a plugin" and file extensions are not covered.

4 / 5

Distinctiveness Conflict Risk

Clear plugin niche reinforced by an explicit boundary ("It does not write a kit SKILL.md (that's `skill-craft`)"), though overlap with sibling kit skills like sdk-craft/mcp-server-craft is not disambiguated.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Repository
saif-shines/devex-kit
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.