CtrlK
BlogDocsLog inGet started
Tessl Logo

test-skill

Test skill

18

Quality

5%

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 ./tests/Fixtures/skills/test-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

11%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 content-free placeholder ('# Test') with no actionable guidance, workflow, or navigation. It cannot function as a skill body despite being token-light.

Suggestions

Add a brief overview of what the skill does and concrete executable guidance (code or commands) to address actionability.

If the skill involves multi-step or risky operations, sequence the steps with explicit validation checkpoints to address workflow_clarity.

Either link to references/example.md from the body or inline a concise getting-started section so the bundle is discoverable, addressing progressive_disclosure.

DimensionReasoningScore

Conciseness

The body '# Test' is not padded or verbose, so it is not a 1, but the lone heading earns no place and provides no useful overview, leaving it below the lean-and-efficient anchor of 3.

2 / 5

Actionability

There is no concrete code, command, or instruction — only a heading — matching the 'Entirely vague or abstract; no concrete code or commands' anchor.

1 / 5

Workflow Clarity

No steps or sequence are present at all, matching the 'Steps missing or incoherent; no sequence' anchor.

1 / 5

Progressive Disclosure

A bundle file references/example.md exists but is never referenced or signaled from the body, and the body has only minimal structure, matching the 'Minimal structure; references are buried' anchor rather than the no-structure 1.

2 / 5

Total

6

/

20

Passed

Description

0%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 placeholder with no concrete capability, trigger terms, usage guidance, or distinctiveness. It fails every dimension and is not a usable skill description.

Suggestions

State the concrete actions the skill performs (e.g., 'Extracts text from PDF files, fills forms') to address specificity.

Add a 'Use when...' clause with natural trigger phrases users would actually say to address completeness and trigger_term_quality.

Narrow the domain so the description is distinguishable from other skills and unlikely to trigger for the wrong one.

DimensionReasoningScore

Specificity

The description 'Test skill' names no domain and no concrete actions; it is pure abstract placeholder language matching the 'Entirely vague; no concrete actions' anchor, and cannot rise to 2 which requires naming a domain.

1 / 5

Completeness

It answers neither 'what does this do' nor 'when should Claude use it'; both are missing and extremely vague, matching anchor 1, and the missing 'Use when...' guidance caps completeness per the rubric.

1 / 5

Trigger Term Quality

No natural keywords or phrases a user would say appear — only the generic word 'Test', matching the 'No natural keywords' anchor and well below the 'one or two generic keywords' bar of 2.

1 / 5

Distinctiveness Conflict Risk

'Test skill' is entirely generic and would overlap with virtually any skill, matching the 'Entirely generic; would conflict with virtually any skill' anchor.

1 / 5

Total

4

/

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

description_field

'description' is very short (10 chars), consider making it more detailed

Warning

Total

15

/

16

Passed

Repository
laravel/boost
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.