your-skill-name
Replace with a clear description of what this skill does and when Claude should use it.
43
11%
Does it follow best practices?
Impact
100%
1.01xAverage 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 not an actual skill description — it is the default placeholder/template text instructing the author to replace it with a real description. It provides zero useful information about capabilities, triggers, or use cases, making it completely non-functional for skill selection.
Suggestions
Replace the placeholder text entirely with a description of the skill's concrete 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 say when they need this skill (e.g., 'Use when the user asks about CSV files, data analysis, or spreadsheet summaries').
Include domain-specific keywords and file types/extensions to make the skill clearly distinguishable from other skills in the collection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | This is a placeholder template text with no concrete actions described whatsoever. It contains zero information about what the skill actually does. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. The text is a meta-instruction telling someone to write a description, not an actual description. | 1 / 3 |
Trigger Term Quality | There are no natural keywords or trigger terms present. The text is entirely a placeholder instruction, not an actual description. | 1 / 3 |
Distinctiveness Conflict Risk | A placeholder description is maximally generic and provides no distinguishing information. It could match or conflict with any skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a skeleton/template skill with no substantive content — every section contains placeholder text rather than actual instructions. It demonstrates a reasonable structural outline (numbered steps, output section, references) but fails to provide any actionable, concrete, or executable guidance. As-is, it would not help Claude perform any specific task.
Suggestions
Replace all placeholder text ('Step One — What to do first') with concrete, specific instructions including actual commands, code snippets, or detailed procedural guidance relevant to the skill's purpose.
Add explicit validation/verification steps, especially if the skill involves security assessment or destructive operations (e.g., 'Verify finding by reproducing the vulnerability with: [specific command]').
Provide at least one concrete example of expected output, such as a sample finding with actual file:line references, evidence, impact description, and remediation steps rather than just referencing a template.
Either include the referenced bundle files (plays/, templates/) or inline the essential content so the skill is self-contained and actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief and doesn't over-explain concepts Claude already knows, but it's entirely placeholder/template text with generic labels like 'Step One — What to do first' and 'Brief description referencing the full procedure,' which adds no real informational value. | 2 / 3 |
Actionability | The content is entirely abstract and placeholder-based with no concrete code, commands, specific examples, or executable guidance. Every step is a vague description ('What to do first,' 'What to do next') rather than an actual instruction. | 1 / 3 |
Workflow Clarity | While there is a numbered sequence, the steps are completely generic placeholders with no real content, no validation checkpoints, and no feedback loops. The workflow provides no meaningful guidance for any actual task. | 1 / 3 |
Progressive Disclosure | The skill references external files (plays/tierN-category/your-play.md, templates/finding.md, templates/report.md) suggesting a structured approach, but no bundle files are provided to verify these references exist, and the references themselves are placeholder paths rather than real navigation aids. | 2 / 3 |
Total | 6 / 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
- OWASP/secure-agent-playbook
- Commit
79fea6b
- 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.