CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-development

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

74

1.60x
Quality

65%

Does it follow best practices?

Impact

93%

1.60x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/plugin-dev/skills/skill-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 thorough, well-sequenced guide to building plugin skills with concrete commands and templates. It is materially weakened by heavy repetition of the same principles across many sections and by failing to practice the leanness it preaches, leaving large inline blocks that should be split into references.

Suggestions

Collapse the repeated progressive-disclosure and writing-style guidance into a single authoritative section; remove the duplicated restatements in "Common Mistakes", "Best Practices Summary", and "Validation Checklist".

Move the "Common Mistakes to Avoid", "Quick Reference", and "Validation Checklist" blocks into references/ files (e.g. references/checklist.md, references/anti-patterns.md) and link to them from a lean SKILL.md.

Trim the body toward the stated 1,500-2,000 word target so the skill models the lean principle it teaches.

DimensionReasoningScore

Conciseness

The body restates the same principles (progressive disclosure, imperative form, third-person description, trigger phrases) across at least five sections ("About Skills", "Progressive Disclosure in Practice", "Writing Style Requirements", "Common Mistakes", "Best Practices Summary", "Validation Checklist"), creating noticeable redundancy and padding.

2 / 5

Actionability

Provides concrete commands (mkdir -p, touch, cc --plugin-dir), YAML frontmatter templates, directory-tree examples, and a worked 6-step process with named reference files; minor gaps remain in executable verification tooling.

4 / 5

Workflow Clarity

The numbered Skill Creation Process (Steps 1-6) is clearly sequenced with an explicit validation/test step (8-point checklist) and an iteration feedback loop, satisfying most checkpoints with only minor gaps.

4 / 5

Progressive Disclosure

Structure exists with headers and one real reference file (references/skill-creator-original.md), but the body itself is far longer than the 1,500-2,000 word target it preaches and inlines checklists, quick-reference, and common-mistakes content that the skill's own guidance says belongs in references/.

3 / 5

Total

13

/

20

Passed

Description

75%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 explicit trigger guidance and many natural user phrases. Its main weakness is that the stated capability (guidance/best practices) is more abstract than the concrete functional verbs in top-anchor examples.

Suggestions

Lead with a concrete capability clause before the triggers, e.g. "Guides creation and editing of SKILL.md files and bundled resources for Claude Code plugins."

Add a few more natural trigger synonyms such as "edit a skill", "refactor a skill", or "fix a skill description".

Tighten the trailing "needs guidance on skill structure, progressive disclosure, or skill development best practices" into crisper concrete actions.

DimensionReasoningScore

Specificity

Lists several concrete trigger scenarios ("create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content") plus structural topics, though the underlying capability (guidance/best practices) is stated more abstractly than the 5 anchor's functional verbs.

4 / 5

Completeness

Explicitly provides both a "when" ("This skill should be used when the user wants to...") with concrete triggers and a "what" (guidance on skill structure, progressive disclosure, best practices); the "what" is somewhat generic relative to the 5 anchor's concrete action verbs.

4 / 5

Trigger Term Quality

Natural phrases users would say ("create a skill", "write a new skill", "improve skill description") are present and relevant, with good coverage but a few common variations (e.g. "edit a skill") missing.

4 / 5

Distinctiveness Conflict Risk

Scoped to Claude Code plugins with distinct skill-development triggers, but "create a skill"/"write a new skill" overlap with a generic skill-creator skill, giving minor conflict risk.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (638 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 26 missing, 2 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository
anthropics/claude-plugins-official
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.