CtrlK
BlogDocsLog inGet started
Tessl Logo

valid-skill

A valid skill for testing purposes.

24

Quality

15%

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 ./packages/coding-agent/test/fixtures/skills/valid-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

30%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 stub: a single heading and one declarative sentence with no executable guidance, workflow, or substantive content. It is token-efficient only because it contains almost nothing of practical use.

Suggestions

Add concrete, executable guidance (commands or code) for the skill's actual task so the body instructs rather than merely describes.

Provide a short, sequenced workflow with any validation checkpoints if the task is multi-step or risky.

Either expand the body with well-organized sections covering the core task, or add one-level-deep reference files (e.g., references/ADVANCED.md) clearly signaled from the overview.

DimensionReasoningScore

Conciseness

The two-line body is extremely lean with no padding and no over-explanation of known concepts, but it stops short of being useful rather than every token earning its place.

4 / 5

Actionability

The body only asserts that the skill 'follows the Agent Skills standard' with no code, commands, or concrete steps — it describes rather than instructs.

1 / 5

Workflow Clarity

No steps or sequence are present at all; the body provides a compliance claim with no process to follow.

1 / 5

Progressive Disclosure

For a simple under-50-line skill needing no external references, a clear section header plus one sentence is minimal but not a monolithic wall or nested-reference trap; it has some structure though little content to organize.

3 / 5

Total

9

/

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-style meta sentence that conveys no actual capability, trigger, or distinguishable niche. It fails every dimension because it describes the skill's existence rather than what it does or when to invoke it.

Suggestions

Replace 'A valid skill for testing purposes' with a concrete statement of what the skill does, naming the domain and 1-2 specific actions (e.g., 'Extracts text and tables from PDF files, fills forms, merges documents').

Add an explicit 'Use when...' clause listing natural trigger phrases and file extensions a user would mention.

Use third-person active voice tied to a distinct functional area so the skill is unlikely to collide with others.

DimensionReasoningScore

Specificity

"A valid skill for testing purposes" names no domain and no concrete actions, relying on pure abstract meta-language about the skill itself rather than any capability.

1 / 5

Completeness

Neither the 'what' (no capability described) nor the 'when' (no trigger guidance) is answered; the sentence is self-referential.

1 / 5

Trigger Term Quality

There are no natural keywords a user would actually say; the description is meta-commentary about the skill, not a phrase tied to any task.

1 / 5

Distinctiveness Conflict Risk

Entirely generic with no functional niche, so it would conflict with virtually any other skill description.

1 / 5

Total

4

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
can1357/oh-my-pi
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.