Clear description of what this skill does and when to use it. Include trigger keywords and contexts inline, e.g. "Use when user wants to X, Y, or Z."
38
3%
Does it follow best practices?
Impact
98%
1.53xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./template/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 is a boilerplate template/placeholder description that has not been filled in with any actual skill information. It contains no concrete actions, no real trigger terms, no 'when to use' guidance, and nothing to distinguish it from any other skill. It is entirely non-functional as a skill description.
Suggestions
Replace the entire placeholder with a concrete description of what the skill actually does, listing specific actions (e.g., 'Extracts data from CSV files, generates summary statistics, creates visualizations').
Add an explicit 'Use when...' clause with real trigger terms that match how users would naturally phrase their requests (e.g., 'Use when the user asks about CSV parsing, data analysis, or spreadsheet summaries').
Include domain-specific keywords and file types/formats to make the skill clearly distinguishable from other skills in a large collection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | This is a template/placeholder description with no concrete actions whatsoever. It describes no actual capabilities—just instructions for how to write a description. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. The text is entirely a template with no real content for either question. | 1 / 3 |
Trigger Term Quality | Contains no natural keywords a user would say. The placeholder variables 'X, Y, or Z' are not real trigger terms, and 'trigger keywords' is meta-instruction, not an actual keyword. | 1 / 3 |
Distinctiveness Conflict Risk | Completely generic placeholder text that provides zero distinguishing information. It would be indistinguishable from any other skill and could not be meaningfully selected. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a blank skill template, not an actual skill. Every section contains placeholder text and generic instructions about how to fill in the template rather than actionable skill content. It would be useful as a contributor guide but fails entirely as a skill that Claude could use to perform any task.
Suggestions
Replace all placeholder content with actual, specific instructions for a real skill — every code block should be executable with real commands and real expected outputs.
Remove the 'Frontmatter Guide' and 'Creating Your Skill' meta-sections entirely, as these are instructions for skill authors, not skill content for Claude.
Add concrete validation steps and feedback loops to the workflow (e.g., how to verify a command succeeded before proceeding to the next step).
Eliminate explanatory scaffolding like 'List any setup requirements' and 'Description of what this script does' — either provide the actual content or remove the section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This is a template/boilerplate file with placeholder content throughout. It explains meta-instructions like 'List any setup requirements' and 'Description of what this script does' rather than providing actual skill content. The frontmatter guide and 'Creating Your Skill' sections are entirely meta-content that wastes tokens explaining how to write a skill rather than being a skill. | 1 / 3 |
Actionability | Every code block and command is a placeholder with generic values like 'python3 scripts/command.py --option value' and 'Expected output here'. Nothing is executable or copy-paste ready — it's all scaffolding with no real instructions. | 1 / 3 |
Workflow Clarity | While there is a numbered sequence in the 'Creating Your Skill' section, the actual skill workflow has no real steps, no validation checkpoints, and no feedback loops. The troubleshooting section uses placeholder text ('Step 1, Step 2') with no actual guidance. | 1 / 3 |
Progressive Disclosure | The template does demonstrate reasonable structural organization with clear section headers (Quick Start, Usage Examples, Commands, Troubleshooting, References) and references to an examples/ directory. However, it's all scaffolding — the structure exists but contains no real content to disclose progressively. | 2 / 3 |
Total | 5 / 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.
0c048af
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.