CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-guide

Explain how to create, organize, and maintain skills in .agents/skills when the user asks about skills.

Quality

83%

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 exemplary lean, well-structured instruction skill with a clear sequence and an explicit validation checklist — no padding anywhere. The single notable gap is that it tells Claude to provide a starter template and checklist without including a concrete example of either.

Suggestions

Include the actual minimal SKILL.md starter template inline (frontmatter with name/description plus a skeleton body) so step 3 is copy-paste ready instead of leaving the template to be invented.

Add a one-line example of a good vs. bad frontmatter description pair to make the validation checklist in step 5 concrete when judging 'clear trigger description'.

DimensionReasoningScore

Conciseness

The ~25-line body contains zero padding and no explanations of concepts Claude already knows; it directs Claude to explain structure to the user rather than re-teaching basics itself. Every line is an instruction, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

The guidance is concrete and enumerable (required files, required frontmatter fields, the three intake questions, and a specific four-item checklist), fitting 'mostly executable guidance with minor gaps'. It is not a 5 because step 3 says "Provide a minimal starter template" without supplying one — the key artifact must be invented rather than copied.

4 / 5

Workflow Clarity

A clear numbered 5-step sequence culminates in an explicit validation checklist ("tested with at least one real prompt"). This is a simple, non-destructive skill, so the simple-skill exception applies and the unambiguous sequence with an explicit validation step matches the top anchor.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and the numbered sections are well organized. Per the rubric's simple-skill note, well-organized sections alone merit the top score here.

5 / 5

Total

19

/

20

Passed

Description

67%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 solid description that answers both what and when in third person with a specific niche, but trigger coverage is thin. Broadening the trigger to natural user phrasings like 'create', 'write', 'update', or 'troubleshoot a skill' would raise both trigger quality and completeness.

Suggestions

Add natural trigger variations users would actually say, e.g. "Use when the user asks to create, write, update, or troubleshoot a skill" instead of the single generic phrase "when the user asks about skills".

Make the 'when' clause more concrete by naming the artifacts involved, e.g. mentioning SKILL.md files or the .agents/skills directory in the trigger portion so it matches the anchor-5 completeness example with multiple concrete trigger phrases.

Consider mentioning validation or maintenance scenarios (e.g., reviewing or fixing an existing skill) to broaden specificity coverage beyond create/organize/maintain.

DimensionReasoningScore

Specificity

"Explain how to create, organize, and maintain skills in .agents/skills" lists three concrete actions in a specific domain, matching the anchor for several specific actions with minor gaps; it is not comprehensive (omits updating, debugging, or validating existing skills). Third-person voice is used correctly.

4 / 5

Completeness

Both 'what' ("Explain how to create, organize, and maintain skills in .agents/skills") and 'when' ("when the user asks about skills") are explicitly present, but the 'when' rests on a single generic trigger phrase rather than multiple concrete trigger phrases required for a 5.

4 / 5

Trigger Term Quality

The only natural keyword is "skills" in the phrase "when the user asks about skills"; common user variations like "make a skill", "write a skill", or "add a skill" are missing. This matches the anchor for some relevant keywords but missing common variations, not the level-4 anchor requiring good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

Skill authoring under .agents/skills is a clear niche with distinct triggers, but there is minor overlap risk with adjacent meta topics such as agent configuration or CLAUDE.md setup, fitting the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

15

/

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

JoseMD12/finance-hub

Path

.agents/skills/skill-guide/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.