data-driven-testing
DEPRECATED: Use testing-best-practices instead. This skill has been retired.
Install with Tessl CLI
npx tessl i github:NeverSight/skills_feed --skill data-driven-testing60
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 capabilities, use cases, or trigger terms. While deprecation notices serve a purpose, this description fails all core criteria for helping Claude select the right skill.
Suggestions
If the skill should remain available, replace the deprecation notice with a proper description of capabilities and 'Use when...' triggers
If truly deprecated, consider removing the skill entirely rather than keeping a non-functional description that wastes selection space
If keeping as a redirect, add context like 'Previously handled X. Use testing-best-practices instead for Y tasks' to help Claude understand the transition
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states the skill is deprecated and redirects to another skill, providing zero information about capabilities. | 1 / 3 |
Completeness | Fails to answer both 'what does this do' and 'when should Claude use it'. The description only communicates deprecation status with no functional information. | 1 / 3 |
Trigger Term Quality | Contains no natural keywords users would say. 'testing-best-practices' is a skill name reference, not a trigger term. No domain-specific vocabulary is present. | 1 / 3 |
Distinctiveness Conflict Risk | The deprecation notice and redirect to a specific skill name provides some distinctiveness, but without knowing what this skill did, it's unclear what domain it occupied or what conflicts might arise. | 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 efficiently communicates the skill is retired and names its replacement. The 'What changed' section provides useful migration context. However, it lacks a direct link to the replacement skill, which would improve actionability.
Suggestions
Add a direct link to testing-best-practices (e.g., [testing-best-practices](../testing-best-practices/SKILL.md))
Consider whether the 'What changed' section is necessary in the deprecated skill or if it belongs in the new skill's migration notes
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is extremely lean - it communicates deprecation status and points to the replacement skill without any unnecessary explanation or padding. | 3 / 3 |
Actionability | Provides clear direction to use the replacement skill, but lacks a direct link or path to testing-best-practices. The 'What changed' section describes differences but doesn't provide executable guidance. | 2 / 3 |
Workflow Clarity | For a deprecation notice, the workflow is unambiguous: stop using this skill, use the replacement instead. No multi-step process is needed here. | 3 / 3 |
Progressive Disclosure | References the replacement skill but doesn't provide a direct link. The 'What changed' section is helpful context but could be in a collapsed section or separate file for those who need migration details. | 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.
- 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.