template-skill
Replace with description of the skill and when Claude should use it.
27
0%
Does it follow best practices?
Impact
91%
0.94xAverage score across 2 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./claude/skills/template-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 is an unfilled template/placeholder description that provides zero useful information about the skill's capabilities or when it should be used. It would be completely non-functional for skill selection, as Claude would have no basis to choose this skill for any task.
Suggestions
Replace the entire placeholder text with a concrete description of what the skill does, listing specific actions (e.g., 'Extracts data from CSV files, generates summary statistics, creates visualizations').
Add an explicit 'Use when...' clause with natural trigger terms that users would actually say when they need this skill.
Include domain-specific keywords and file types/formats to make the skill clearly distinguishable from other available skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | This is a placeholder/template description with no concrete actions described. 'Replace with description of the skill' provides zero information about what the skill does. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. The placeholder text mentions both concepts but provides no actual content for either. | 1 / 3 |
Trigger Term Quality | Contains no natural keywords whatsoever. The text is entirely boilerplate template language with no domain-specific or user-facing trigger terms. | 1 / 3 |
Distinctiveness Conflict Risk | A generic placeholder description is maximally conflicting — it provides no distinguishing information that would differentiate this skill from any other. | 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 skill content is effectively empty, containing only a placeholder heading with no actual instructions, examples, or guidance. It provides zero value as a skill file and would need to be written from scratch.
Suggestions
Add actual skill instructions with concrete, executable code examples or specific actionable guidance for the task this skill is meant to address.
Define a clear workflow with sequenced steps and validation checkpoints if the skill involves multi-step processes.
Include a brief quick-start section and, if the skill is complex, link to supplementary reference files for advanced topics.
Replace the placeholder description in the YAML frontmatter with a meaningful description of when and how Claude should use this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill content is essentially empty — it contains only a placeholder heading ('# Insert instructions below') with no actual instructions, guidance, or content. There is nothing useful provided. | 1 / 3 |
Actionability | There is no concrete, executable guidance whatsoever. The content is a blank placeholder with no code, commands, examples, or instructions. | 1 / 3 |
Workflow Clarity | No workflow, steps, or processes are defined. The content is entirely empty beyond a placeholder heading. | 1 / 3 |
Progressive Disclosure | There is no structure, no references, and no organization — just a single placeholder line with no content to disclose progressively. | 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.
- Repository
- einverne/dotfiles
- Commit
b1b2fe0
- 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.