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 zero information about capabilities, triggers, or use cases, making it essentially useless for skill selection. If the skill is truly retired, it should ideally be removed rather than left with a non-functional description.
Suggestions
If the skill must remain, add a brief summary of what it originally covered so Claude can understand the redirect context (e.g., 'DEPRECATED: Previously handled unit test generation and test coverage analysis. Use testing-best-practices instead.').
Include trigger terms from the original domain so Claude can properly route to the replacement skill (e.g., 'Use when: users mention unit tests, test writing, or test coverage — redirect to testing-best-practices').
Consider removing the skill entirely if it is retired, rather than keeping a non-functional description that wastes a slot in skill selection.
| 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'. The description is purely 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-facing trigger term. | 1 / 3 |
Distinctiveness Conflict Risk | The deprecation notice is somewhat distinctive in that it explicitly redirects to another skill, which reduces conflict risk. However, without any domain information, it's unclear what domain this overlaps with. | 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 its purpose. Its main weakness is the lack of a direct link or file path to the replacement skill, which would make the transition more seamless. The 'What changed' summary is a nice touch for users familiar with the old skill.
Suggestions
Add a direct link or file path to the replacement skill, e.g., 'See [testing-best-practices](../testing-best-practices/SKILL.md)'
Consider adding a one-line example of how to invoke or reference the replacement skill in practice
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is extremely lean—it states the deprecation, names the replacement, and briefly lists 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 executable guidance of its own. | 2 / 3 |
Workflow Clarity | For a deprecation notice (a single-purpose, simple skill), the workflow is unambiguous: stop using this skill, use the named replacement. No multi-step process or validation is needed. | 3 / 3 |
Progressive Disclosure | It names the replacement skill but doesn't provide a direct link or path to it. A clear hyperlink or file reference to `testing-best-practices` 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
e437c3c
- 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.