too-long-skill
This skill has more than 500 lines which should fail validation.
16
Quality
0%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/fixtures/too-long-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 fundamentally broken - it appears to be a test case or placeholder that describes a validation constraint rather than an actual skill capability. It provides zero information about what the skill does, when to use it, or any relevant trigger terms. This would be completely unusable for skill selection.
Suggestions
Replace the entire description with actual capability information: what specific actions does this skill perform?
Add a 'Use when...' clause with concrete trigger scenarios and natural keywords users would say
Define a clear domain or niche to distinguish this skill from others in a skill library
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only references a validation constraint ('more than 500 lines which should fail validation') rather than describing any capabilities. | 1 / 3 |
Completeness | Fails to answer both 'what does this do' and 'when should Claude use it'. The description is entirely about the skill file itself rather than its purpose or use cases. | 1 / 3 |
Trigger Term Quality | No natural keywords that users would say when needing this skill. Terms like 'validation' and '500 lines' are technical/meta references, not user-facing trigger terms. | 1 / 3 |
Distinctiveness Conflict Risk | The description provides no distinguishing characteristics. It describes nothing about the skill's domain or function, making it impossible to differentiate from any other skill. | 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 entirely non-functional, consisting solely of 495 lines of identical filler text with no actual instructions, examples, or guidance. It fails every quality dimension as it provides zero value while consuming maximum tokens. This appears to be a test file designed to fail validation for exceeding line limits.
Suggestions
Replace all filler content with actual skill instructions that teach Claude how to perform a specific task
Add concrete, executable code examples or specific commands that Claude can follow
Structure the content with clear sections (Quick start, Usage, Examples) and keep it under 500 lines by using progressive disclosure to reference detailed content in separate files
Define a clear workflow with numbered steps if the skill involves a multi-step process
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler text with no useful information. Every line is redundant padding that wastes tokens without providing any actionable guidance. | 1 / 3 |
Actionability | There is no concrete guidance, code, commands, or instructions. The content describes nothing and instructs nothing—it's purely placeholder text. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content contains no sequence of actions, validation checkpoints, or any procedural guidance whatsoever. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of repetitive filler text with no structure, sections, or references to other files. There is no organization or navigation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
56%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (504 lines); consider splitting into references/ and linking | Warning |
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 9 / 16 Passed | |
- Repository
- pproenca/dot-skills
- Commit
43f0b81
- 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.