data-driven-testing
DEPRECATED: Use testing-best-practices instead. This skill has been retired.
63
42%
Does it follow best practices?
Impact
99%
1.30xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xbigboss/claude-code/data-driven-testing/SKILL.mdQuality
Discovery
7%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 a deprecation notice rather than a functional skill description. It provides no information about what the skill does, when to use it, or any trigger terms. While the intent to redirect to a replacement skill is clear, the description fails on all functional evaluation criteria.
Suggestions
If the skill is truly deprecated, consider removing it entirely rather than keeping a stub description that provides no useful routing information.
If the skill must remain, include the domain and trigger terms from the replacement skill so Claude can properly redirect, e.g., 'DEPRECATED: Use testing-best-practices instead. Previously handled test writing, unit tests, and test coverage. Use testing-best-practices for all testing-related tasks.'
Add a 'Use when...' clause that explicitly tells Claude to redirect to the replacement skill when users mention relevant trigger terms.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions or capabilities whatsoever. It only states the skill is deprecated and points to another skill. | 1 / 3 |
Completeness | It answers neither 'what does this do' nor 'when should Claude use it'. It only provides a deprecation notice with no functional information. | 1 / 3 |
Trigger Term Quality | There are no natural keywords a user would say when needing a skill. 'Testing-best-practices' is a skill name reference, not a user trigger term. | 1 / 3 |
Distinctiveness Conflict Risk | The deprecation notice and redirect to a specific skill name provides some distinctiveness in that it explicitly says NOT to use this skill, which reduces conflict risk somewhat. However, it doesn't clarify what domain it covers, so it could still cause confusion. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured deprecation notice that is concise and clear about what replaced it and why. Its main weakness is the lack of a direct link or path to the replacement skill, which slightly reduces actionability and progressive disclosure. Overall it serves its purpose effectively as a retired skill stub.
Suggestions
Add a direct relative link to the replacement skill file, e.g., `See [testing-best-practices](../testing-best-practices/SKILL.md)`.
Consider adding a one-line migration note if users might have references to the old skill's JSON schema format.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is extremely lean—it communicates the deprecation, the replacement skill, and a concise summary of what changed. No unnecessary explanation or padding. | 3 / 3 |
Actionability | It clearly directs the user to use `testing-best-practices` instead, which is actionable, but provides no link or path to the replacement skill and no concrete commands or code. For a deprecation notice this is adequate but not fully actionable. | 2 / 3 |
Workflow Clarity | This is a single-purpose deprecation notice with one unambiguous action: stop using this skill and use the named replacement. No multi-step workflow is needed, and the single action is clear. | 3 / 3 |
Progressive Disclosure | The skill references `testing-best-practices` but does not provide a link or path to it. For a deprecation stub this is mostly fine, but a direct reference (e.g., a relative link) would improve navigation. | 2 / 3 |
Total | 10 / 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
- NeverSight/skills_feed
- Commit
aa009ea
- 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.