CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-development

This skill should be used when the user asks to create a new skill, repair an existing skill, improve trigger descriptions, reorganize skill structure, or make a Claude skill more reusable and internally consistent.

68

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

78%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-organized, lean instruction skill with a clear sequenced workflow, an integrity-check checkpoint, and real one-level-deep references. It is action-oriented without over-explaining concepts Claude already knows.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (e.g., "Keep one skill = one durable job"), but a few phrasings like "Use the local inventory as the authority. Do not write guidance against an imagined plugin layout." could be tightened further.

4 / 5

Actionability

Concrete, specific guidance throughout — a six-step default workflow and named repair patterns — with mostly executable direction; it is instruction-only (no code), which is appropriate here, though a few steps remain high-level hints.

4 / 5

Workflow Clarity

The default workflow is a clearly numbered sequence with an explicit integrity-check checkpoint (step 6, "Run integrity checks before closing") and repair-pattern branches; minor validation gaps keep it just below a 5.

4 / 5

Progressive Disclosure

Clear overview structure with a one-level-deep References section pointing to three real bundled files (checklist.md, integrity-checks.md, skill-creator-original.md, all verified present), keeping detail out of the main file.

5 / 5

Total

17

/

20

Passed

Description

87%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 is a strong, third-person trigger statement that pairs a concrete action list with an explicit "use when" clause. It is distinct and unlikely to conflict with other skills, with only minor room to broaden trigger synonyms.

DimensionReasoningScore

Specificity

Lists several concrete actions — "create a new skill", "repair an existing skill", "improve trigger descriptions", "reorganize skill structure" — though "make a Claude skill more reusable and internally consistent" is somewhat abstract, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what (create/repair/improve/reorganize skills) and when ("This skill should be used when the user asks to...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ("create a new skill", "repair an existing skill", "improve trigger descriptions", "reorganize skill structure"); good coverage but a few common variations like "fix a skill" or "update a skill" are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche — skill authoring and repair — with distinct triggers unlikely to fire for unrelated skills; minimal conflict risk.

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.

Validation15 / 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
Galaxy-Dawn/claude-scholar
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.