CtrlK
BlogDocsLog inGet started
Tessl Logo

example-skill

This skill should be used when the user asks to "demonstrate skills", "show skill format", "create a skill template", or discusses skill development patterns. Provides a reference template for creating Claude Code plugin skills.

59

Quality

69%

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

Fix and improve this skill with Tessl

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

Quality

Content

53%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 reasonably well-organized instructional template that explains skill structure and frontmatter clearly, but it spends tokens restating concepts Claude already knows and offers abstract guidance rather than concrete, executable steps. Workflow clarity is adequate for a simple single-purpose skill but lacks validation checkpoints.

Suggestions

Trim sections that restate general knowledge Claude already has (e.g., the overview paragraph defining what skills/commands/agents are) to improve conciseness.

Replace abstract best-practice bullets with concrete, copy-paste-ready examples such as a full minimal SKILL.md skeleton a user could drop in.

Add a short verification step (e.g., how to confirm a new skill activates for an expected query) to give the workflow a concrete checkpoint.

DimensionReasoningScore

Conciseness

The body explains concepts Claude already knows ("Skills are model-invoked capabilities...", frontmatter field meanings, generic best practices) and is somewhat padded; it is mostly efficient but includes unnecessary explanation that could be tightened.

3 / 5

Actionability

It offers some concrete guidance (file tree structures, a yaml description template) but the core instruction is abstract prose with no executable steps or complete commands, leaving key execution details missing.

3 / 5

Workflow Clarity

Sections are listed in a rough sequence (structure, frontmatter, descriptions, best practices) but there is no multi-step workflow with validation checkpoints; the skill is a single-purpose instructional template, so sequence is present but checkpoints are absent.

3 / 5

Progressive Disclosure

Good organization with clear section headers and a small, focused body; the skill describes optional supporting subdirectories (references/, examples/, scripts/) but provides no actual bundle files, so structure is appropriate with only minor signaling gaps.

4 / 5

Total

13

/

20

Passed

Description

85%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 that clearly states both what the skill does and when to use it, anchored in concrete trigger phrases. Minor keyword/synonym coverage gaps keep trigger term quality and specificity just below perfect.

DimensionReasoningScore

Specificity

Names concrete actions ("demonstrate skills", "show skill format", "create a skill template") plus a concrete artifact ("reference template"), giving several specific actions with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers what ("Provides a reference template for creating Claude Code plugin skills") and when ("should be used when the user asks to..."), with concrete trigger phrases for both.

5 / 5

Trigger Term Quality

Includes natural user-facing phrases ("demonstrate skills", "show skill format", "create a skill template") and the keyword "skill development patterns", but misses common synonyms like "write a skill" or file extension cues.

4 / 5

Distinctiveness Conflict Risk

The trigger is a narrow, clearly defined niche (plugin skill creation/format demonstration) with specific phrases, posing minimal overlap risk with other skills.

5 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

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.