CtrlK
BlogDocsLog inGet started
Tessl Logo

adding-a-skill

extending yourself with a new reusable skill by interviewing the user

55

Quality

61%

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 ./.claude/skills/adding-a-new-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a well-structured, actionable instruction-only skill with a clear interview-then-assemble workflow and no unnecessary external references. Minor gains are possible in conciseness and a touch more concrete templating.

Suggestions

Trim the explanatory rationale in the Subagent considerations block to the bare decision criteria.

Consider adding a compact completed SKILL.md example to push actionability toward fully copy-paste-ready.

Add a brief completion checklist restating the final steps (save, verify path, present link) to strengthen workflow checkpoints.

DimensionReasoningScore

Conciseness

Instruction-dense and lean with only minor over-explanation (the Subagent considerations rationale), fitting the score-4 anchor of efficient content with trimmable excess.

4 / 5

Actionability

Provides concrete, executable guidance: exact file path, a precise section template, and explicit questions to ask; absence of code is appropriate for an instruction-only skill and not penalized.

4 / 5

Workflow Clarity

A clear 3-step sequence with an implicit multi-round questioning loop; explicit validation checkpoints are not applicable to an interactive interview, so no destructive/batch cap applies.

4 / 5

Progressive Disclosure

No bundle files are needed; the content is self-contained and well-organized with numbered steps and a subsection, just over the 50-line simple-skill threshold for a full 5.

4 / 5

Total

16

/

20

Passed

Description

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

The description conveys a clear purpose and distinct niche but lacks an explicit "Use when..." trigger clause and uses second-person voice, limiting its completeness and specificity. It is functional but below the strongest examples.

Suggestions

Rewrite in third person, e.g. "Guides the user through creating a new reusable skill by interviewing them about its purpose and structure."

Add an explicit trigger clause: "Use when the user wants to add, create, or build a new skill."

Include a couple of concrete actions or synonyms (create/build) to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain and one concrete method ("interviewing the user"), matching the score-3 anchor, but "extending yourself" uses second-person reflexive voice, which the rubric penalizes by reducing specificity by 1.

2 / 5

Completeness

The "what" is clear (extend with a reusable skill via interviewing), but "when" is only weakly implied with no explicit "Use when..." clause, which the rubric caps at 3.

3 / 5

Trigger Term Quality

"skill" / adding a skill are natural trigger terms, but common variations like "create" or "build a skill" are missing, fitting the score-3 anchor.

3 / 5

Distinctiveness Conflict Risk

Skill creation is a distinct niche with minimal conflict risk, only minor overlap with other meta-skills, matching the score-4 anchor.

4 / 5

Total

12

/

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
stellar/stellar-core
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.