A tiny skill used by the skill isolation example.
16
0%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./examples/skillisolation/skills/demo-skill/SKILL.mdQuality
Discovery
0%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 is essentially a placeholder or meta-reference with no functional content. It fails on every dimension: it describes no concrete actions, includes no user-facing trigger terms, answers neither 'what' nor 'when', and provides no distinguishing characteristics that would help Claude select it appropriately.
Suggestions
Replace the meta-reference with a concrete description of what the skill actually does, listing specific actions (e.g., 'Performs X, generates Y, processes Z').
Add an explicit 'Use when...' clause with natural trigger terms that describe scenarios where this skill should be selected.
Include domain-specific keywords that users would naturally use when requesting this skill's functionality.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'A tiny skill used by the skill isolation example' is entirely abstract and says nothing about what the skill actually does. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. The description only references its role as a test artifact, providing no functional information. | 1 / 3 |
Trigger Term Quality | There are no natural keywords a user would say. 'Skill isolation example' is internal/meta terminology, not something a user would naturally request. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it provides no distinguishing characteristics. It could be confused with any other skill since it describes no specific domain or capability. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is not a functional skill — it is a test sentinel designed to detect skill state leaks across agents. It contains zero actionable content, no code, no workflow, and no structure. It fails every dimension of the rubric.
Suggestions
If this is intended as a real skill, add concrete instructions or executable code for the task it should teach.
Add a clear workflow with at least one actionable step Claude can follow.
If this is purely a test fixture, it should not be evaluated as a skill — consider excluding it from quality assessments.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content provides no actionable information whatsoever. It is essentially a test fixture/sentinel value rather than a real skill, so every token is wasted from a skill-teaching perspective. | 1 / 3 |
Actionability | There are no concrete instructions, code, commands, or guidance of any kind. The content describes its own purpose as a leak-detection mechanism rather than instructing Claude on how to perform a task. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process are described. There is nothing for Claude to follow or execute. | 1 / 3 |
Progressive Disclosure | No structure, sections, or references exist. The content is two sentences with no organization or navigation to supporting materials. | 1 / 3 |
Total | 4 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
9f4b734
Table of Contents
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.