CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-skill

testing tessl skills

Quality

44%

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 ./.tessl/tiles/lightfactory/test-skill/skills/test-skill/SKILL.md

The canonical home for this skill is test-skill in ericjohnolson/tessl-test

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 an unfilled template: a heading plus a TODO placeholder. While trivially concise and free of structural problems, it provides no executable guidance and no workflow whatsoever — the skill cannot be executed from this content.

Suggestions

Replace the TODO line with the actual execution instructions: the concrete steps, commands, or code the agent should run when this skill fires.

If the skill involves multi-step or batch operations (e.g. running skill tests), sequence the steps explicitly and include validation checkpoints with a fix-and-retry loop.

Keep the body lean — since there are no bundle files, keep all guidance in well-organized sections directly in SKILL.md, or split detailed material into clearly signaled one-level-deep reference files.

DimensionReasoningScore

Conciseness

The body is a single TODO placeholder line with zero verbosity, padding, or over-explanation — nothing to trim, so "lean and efficient; every token earns its place" is the best fit. The emptiness is penalized under actionability, not here.

5 / 5

Actionability

"TODO: Add instructions for how the agent should execute this skill." is a scaffold placeholder with no concrete guidance, code, or commands — it describes the absence of instructions rather than instructing, matching anchor 1.

1 / 5

Workflow Clarity

No steps, sequence, or validation checkpoints exist at all; the entire body is a TODO note, matching "Steps missing or incoherent; no sequence".

1 / 5

Progressive Disclosure

No bundle files exist and nothing is inlined or nested, so there are no structural violations — but the single TODO line is not "well-organized sections" either, placing it between anchors 4 and 5, best fit 4.

4 / 5

Total

11

/

20

Passed

Description

20%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 of three words: it names a domain but gives no concrete actions, no 'Use when' trigger guidance, and no natural trigger terms. It would rarely fire correctly and does not communicate what the skill actually does.

Suggestions

Replace "testing tessl skills" with a concrete action statement in third person, e.g. "Runs and validates tessl skill definitions, checking structure and output correctness."

Add an explicit trigger clause, e.g. "Use when the user mentions tessl, wants to test or validate a skill, or asks to check skill definitions."

Include natural trigger keywords and synonyms (tessl, skill testing, skill validation, SKILL.md) so the skill is discoverable and distinguishable from general testing skills.

DimensionReasoningScore

Specificity

"testing tessl skills" names a domain (tessl skills) but the only action is the generic "testing" — no concrete actions are listed, matching the anchor "Names the domain but actions are minimal or generic".

2 / 5

Completeness

"testing tessl skills" provides an extremely vague 'what' and no 'when' guidance at all, matching "Missing both what and when, or both are extremely vague" — even the 'what' is unclear.

1 / 5

Trigger Term Quality

"tessl" is technical jargon and "testing"/"skills" are generic keywords; no natural phrases a user would actually say are present, matching "One or two generic keywords; missing the natural phrases users say".

2 / 5

Distinctiveness Conflict Risk

The niche term "tessl" gives some distinctiveness, but "testing skills" is broad enough to overlap with any test-related skill, matching "Somewhat specific but could still overlap with similar skills".

3 / 5

Total

8

/

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

ericjohnolson/tessl-test

Path

.tessl/tiles/lightfactory/test-skill/skills/test-skill/SKILL.md

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.