CtrlK
BlogDocsLog inGet started
Tessl Logo

valid-skill

A minimal, fully spec-conformant fixture skill used to exercise the happy path.

34

Quality

29%

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 ./cli/platform/emit/__fixtures__/repo/.agents/skills/valid-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

41%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 maximally lean but essentially content-free: it conveys no actionable guidance, no workflow, and no real capability information. It is appropriate only as a minimal test fixture, not as a functional skill body.

Suggestions

Add at least one concrete, executable instruction or code example so the body is actionable.

If the skill performs a multi-step or risky operation, include a sequenced workflow with a validation checkpoint.

Replace the placeholder line with guidance that tells Claude what to actually do when this skill is invoked.

DimensionReasoningScore

Conciseness

The body is a single heading and one short line with no padding or over-explanation; every token is lean and assumes Claude's competence.

5 / 5

Actionability

The body provides no concrete code, commands, or steps; "a small skill body used for testing" only describes rather than instructs.

1 / 5

Workflow Clarity

There is no sequence of steps and no single unambiguous action to perform, so no workflow or validation checkpoints exist.

1 / 5

Progressive Disclosure

For a sub-50-line fixture with no need for external references, the single heading provides reasonable organization, though it stops short of the well-organized multi-section structure that would warrant a 5.

4 / 5

Total

11

/

20

Passed

Description

17%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.

This description reads as a meta-comment about the skill being a test fixture rather than a statement of capability and trigger conditions. It lacks concrete actions, natural trigger terms, and any "when to use" guidance.

Suggestions

Replace the fixture framing with the actual capability the skill performs (e.g., concrete verbs and objects).

Add an explicit "Use when..." clause naming the user-facing situations or phrases that should trigger this skill.

Include natural trigger keywords and file extensions a user would actually say, not internal testing jargon.

DimensionReasoningScore

Specificity

The description names a domain ("fixture skill used to exercise the happy path") but lists no concrete capability actions; it describes what kind of skill it is rather than what it does.

2 / 5

Completeness

It offers only a vague "what" (a test fixture) and entirely lacks any "Use when..." trigger guidance, which caps completeness well below the explicit-trigger anchor.

2 / 5

Trigger Term Quality

Terms like "fixture skill", "spec-conformant", and "happy path" are technical jargon a user would never say when needing this skill; no natural trigger keywords are present.

1 / 5

Distinctiveness Conflict Risk

The phrasing is very broad and capability-free, so it would overlap with almost any other skill description rather than carving out a distinct niche.

2 / 5

Total

7

/

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
first-fluke/oh-my-agent
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.