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.

79

Quality

100%

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

100%

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, instruction-only skill: concise, actionable, with a sequenced workflow containing an explicit validation checkpoint and clean one-level references that all resolve to real files. It earns top marks on every dimension.

DimensionReasoningScore

Conciseness

The body is lean throughout — short goal, core rules, and a numbered workflow with no padding or explanations of concepts Claude already knows. Not a 2 because there is no unnecessary elaboration to tighten.

3 / 3

Actionability

Concrete numbered steps ('inspect the target skill directory', 'verify which agents... actually exist') plus executable bash snippets in integrity-checks.md give copy-paste-ready guidance rather than vague direction.

3 / 3

Workflow Clarity

The six-step default workflow is clearly sequenced and step 6 ('Run integrity checks before closing') provides an explicit validation checkpoint before the skill closes.

3 / 3

Progressive Disclosure

SKILL.md stays a lean overview and points to three real one-level-deep references (checklist.md, integrity-checks.md, skill-creator-original.md), all verified to exist in ./references/, with no nesting.

3 / 3

Total

12

/

12

Passed

Description

100%

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 strong across all dimensions: concrete actions, natural trigger phrasing, an explicit use-when clause, and a clearly distinct niche. No vague fluff or over-claims are present.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'create a new skill, repair an existing skill, improve trigger descriptions, reorganize skill structure, or make a Claude skill more reusable and internally consistent' — matching the top anchor.

3 / 3

Completeness

The explicit 'This skill should be used when the user asks to...' clause answers both what it does and when to trigger it, hitting the top anchor.

3 / 3

Trigger Term Quality

Phrases like 'create a new skill', 'repair an existing skill', 'improve trigger descriptions', and 'reorganize skill structure' are exactly what a user would naturally say, giving broad coverage.

3 / 3

Distinctiveness Conflict Risk

The skill-authoring niche is clearly bounded by its triggers and would not reasonably fire for unrelated skills.

3 / 3

Total

12

/

12

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.