test-skill

testing tessl skills

Quality

13%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

11%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 SKILL.md body is an unimplemented placeholder: a single header and a TODO with no instructions, examples, workflow, or references. It cannot guide the agent in any way and needs the actual skill instructions written.

Suggestions

Replace the TODO with concrete, executable instructions or code examples that tell the agent exactly what to do.

If the skill is multi-step, add a numbered workflow with explicit validation/checkpoint steps.

Organize content into clear sections and, for larger material, split details into one-level-deep reference files with signaled links.

Dimension	Reasoning	Score
Conciseness	The body is only a header plus a TODO placeholder, so it is short but conveys no usable information; while not verbose, the tokens do not earn their place, placing it noticeably below the midpoint rather than at the lean/efficient score-5 anchor.	2 / 5
Actionability	"TODO: Add instructions for how the agent should execute this skill" provides no concrete code, commands, or steps — it only notes that guidance is missing, matching the score-1 anchor ("Entirely vague or abstract; no concrete code or commands").	1 / 5
Workflow Clarity	There are no steps, sequence, or validation checkpoints — only a TODO marker, matching the score-1 anchor ("Steps missing or incoherent; no sequence").	1 / 5
Progressive Disclosure	Structure is minimal (one header and a TODO) with no sectioning or references to organize content, fitting the score-2 anchor ("Minimal structure"); it is not a 1 because it is not a monolithic wall of text or deeply nested references.	2 / 5
	Total	6 / 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 placeholder status note ("testing tessl skills") rather than a functional skill description: it names a domain but provides no concrete actions, no use-when trigger, and carries high overlap risk. It needs a rewrite stating what the skill does and when Claude should invoke it.

Suggestions

Rewrite the description to state concrete actions in third person, e.g. "<does X, Y, Z>".

Add an explicit 'Use when...' clause with natural trigger phrases users would actually say.

Narrow the domain so the description is distinct from other tessl skills and won't trigger for the wrong one.

Dimension	Reasoning	Score
Specificity	The phrase "testing tessl skills" names a domain (tessl skills) but states zero concrete actions — only a status gerund — matching the score-2 anchor ("Names the domain but actions are minimal or generic"); it is not a 3 because no concrete capability is listed.	2 / 5
Completeness	The description answers neither "what does this do" nor "when should Claude use it" — "testing tessl skills" reads as a development status note, matching the score-1 anchor ("Missing both what and when, or both are extremely vague").	1 / 5
Trigger Term Quality	"testing" is a single generic keyword and there are no natural trigger phrases a user would say to invoke this skill, fitting the score-2 anchor; it is not a 1 because it is not pure technical jargon.	2 / 5
Distinctiveness Conflict Risk	"testing tessl skills" is very broad with high overlap risk against any tessl-related skill, matching the score-2 anchor; it is not a 1 because it does narrow slightly to the tessl domain.	2 / 5
	Total	7 / 20 Passed

Validation

100%

Warnings & errors only

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
Commit: 2a98cc1

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.