CtrlK
BlogDocsLog inGet started
Tessl Logo

test-skill

Test

29

Quality

22%

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 ./test/fixtures/marketplace/good/plugins/test-plugin/skills/test-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

45%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 content is a minimal placeholder ('# Test\n\nBody.') with a heading and one word; it is lean with no wasted tokens but provides zero actionable guidance, no workflow, and no substantive structure. It scores moderately on conciseness and progressive disclosure (no padding or nested refs) but at the floor on actionability and workflow clarity because it instructs nothing.

Suggestions

Add concrete, executable guidance (code examples or specific commands) so the skill tells Claude exactly what to do, addressing the score-1 actionability.

Provide at least a clear single-step workflow or sequence so the intended action is unambiguous, addressing the score-1 workflow clarity.

Expand the body with real content sections so it functions as an overview rather than an empty placeholder.

DimensionReasoningScore

Conciseness

The body ('# Test\n\nBody.') is extremely lean with no padding and no over-explanation of concepts Claude knows, sitting above the score-3 anchor; it does not reach 5 because a 5 requires lean AND substantive content, whereas this is lean but vacuous.

4 / 5

Actionability

'Body.' provides no concrete code, commands, or even high-level hints, matching the score-1 anchor for entirely vague, abstract content with no executable guidance; score 2 requires at least minimal concrete guidance, which is absent.

1 / 5

Workflow Clarity

There are no steps, no sequence, and no validation, matching the score-1 anchor; the simple-skill exception does not apply because 'Body.' names no action, so the single action is entirely ambiguous rather than unambiguous.

1 / 5

Progressive Disclosure

With no bundle files and only a single heading, the body has no nested references, no monolithic wall, and no misplaced inline content, sitting above score 3; it does not reach 5 because a 5 requires a clear overview with navigable references, and there is no content to organize or navigate.

4 / 5

Total

10

/

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 single-word placeholder ('Test') that conveys no capability, no trigger context, and no distinctiveness, scoring the minimum across all four dimensions. It cannot be evaluated as a real skill description and needs to be entirely rewritten with concrete actions and a 'Use when...' trigger clause.

Suggestions

Replace 'Test' with a third-person description of concrete actions the skill performs (e.g., 'Extracts text from PDF files, fills forms, merges documents').

Add an explicit 'Use when...' trigger clause naming natural keywords users would say (e.g., 'Use when working with PDF files, forms, or document extraction').

Name the specific domain and file types to reduce overlap with other skills and improve distinctiveness.

DimensionReasoningScore

Specificity

The description is the single word 'Test', which names no domain and describes no concrete actions, matching the score-1 anchor for entirely vague, pure abstract language even more minimally than 'Helps with documents'.

1 / 5

Completeness

'Test' answers neither what the skill does nor when to use it, matching the score-1 anchor for missing both 'what' and 'when'; it falls well below the missing-'Use when...' cap of 3.

1 / 5

Trigger Term Quality

'Test' contains zero natural keywords that a user would say when needing this skill, matching the score-1 anchor for no natural keywords; score 2 requires at least one or two generic keywords, which are absent.

1 / 5

Distinctiveness Conflict Risk

'Test' is an entirely generic placeholder naming no domain, so it would conflict with virtually any skill, matching the score-1 anchor; score 2 implies some broad domain is named.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

description_field

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

Warning

Total

15

/

16

Passed

Repository
saif-shines/doraval
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.