CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-skill

testing tessl skills

Quality

34%

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

Quality

Content

18%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 empty template stub: a title plus a TODO placeholder with no instructions, code, steps, or structure. The skill as written cannot guide an agent to do anything.

Suggestions

Replace the TODO with the actual execution steps for the skill (e.g., exact commands or code the agent should run), which is the primary gap for actionability.

If the skill involves multi-step or batch/destructive operations, sequence the steps and include explicit validation checkpoints (validate → fix → retry).

Organize the body into clear sections (e.g. a quick-start section plus 'See X.md' pointers) so any detail content is progressively disclosed rather than left as a placeholder.

DimensionReasoningScore

Conciseness

The body is only two lines with no padding, but the single sentence is a placeholder that earns no place in context; it is neither verbose nor genuinely lean-and-useful, sitting at the midpoint.

3 / 5

Actionability

"TODO: Add instructions for how the agent should execute this skill" provides no concrete code, commands, or steps — it only marks that guidance is missing, matching the 'entirely vague' anchor.

1 / 5

Workflow Clarity

No steps or sequence of any kind are present; the body contains only an unfulfilled TODO marker, so there is no workflow to follow or validate.

1 / 5

Progressive Disclosure

Structure is minimal — a single heading and one TODO line with no organized sections and no references, and the under-50-line exception does not apply because there are no well-organized sections to navigate.

2 / 5

Total

7

/

20

Passed

Description

16%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 two-word placeholder that fails to state concrete capabilities or any usage trigger. It cannot reliably route a user to this skill and conflicts broadly with testing-related skills.

Suggestions

State concrete actions in third person, e.g. "Runs unit and integration tests for Tessl skills and reports failures" — this would lift specificity from the generic 'testing' verb.

Add an explicit trigger clause such as "Use when the user mentions Tessl, asks to validate or test a skill, or says 'run skill tests'."

Include natural trigger synonyms (e.g. "tessl", "skill validation", "skill tests") so the description matches how users actually phrase the request.

DimensionReasoningScore

Specificity

"testing tessl skills" names a domain but offers only the generic action "testing" with no concrete capabilities, matching the 'Processes PDF files'-level anchor rather than any anchor that lists actions.

2 / 5

Completeness

There is no 'Use when...' trigger clause (capping completeness at 3 by guideline), and even the 'what' is extremely vague — neither what nor when is meaningfully answered.

1 / 5

Trigger Term Quality

The only keywords are "testing" and "tessl" — one or two generic/specific terms with no natural phrases a user would say when needing this skill.

2 / 5

Distinctiveness Conflict Risk

"testing skills" is very broad and would overlap with any testing-related skill; only the niche term "tessl" provides slight narrowing, so overlap risk is high.

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

ericjohnolson/tessl-test

Path

tiles/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.