test-retry-config
Test Retry Config - Auto-activating skill for Test Automation. Triggers on: test retry config, test retry config Part of the Test Automation skill category.
36
3%
Does it follow best practices?
Impact
99%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/09-test-automation/test-retry-config/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 essentially a placeholder that repeats the skill name without providing any meaningful information about what the skill does or when it should be used. It lacks concrete actions, natural trigger terms, and explicit usage guidance, making it nearly impossible for Claude to correctly select this skill from a pool of alternatives.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures test retry policies, sets retry counts, defines backoff strategies, and handles flaky test management in CI/CD pipelines.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about retrying failed tests, configuring retry logic, handling flaky tests, setting retry counts, or managing test rerun strategies.'
Include relevant file types, frameworks, or tools (e.g., Jest, pytest, JUnit retry configuration) to improve distinctiveness and trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. 'Test Retry Config' is repeated as both the name and trigger term, with no explanation of what the skill actually does (e.g., configure retry counts, set backoff strategies, modify test configuration files). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is essentially just restating the skill name as a trigger. There is no meaningful explanation of either what or when. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'test retry config' repeated twice. There are no natural language variations a user might say, such as 'flaky test', 'retry failed tests', 'rerun tests', 'test retries', or 'retry strategy'. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'test retry config' is somewhat specific to a niche area (configuring test retries), which provides some distinctiveness. However, the lack of concrete detail means it could overlap with broader test automation or test configuration skills. | 2 / 3 |
Total | 5 / 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 is essentially a placeholder with no substantive content. It contains no executable code, no concrete configuration examples (e.g., Jest retry config, pytest-rerunfailures setup), and no actionable workflow. Every section is generic boilerplate that could apply to any skill topic.
Suggestions
Add concrete, executable code examples for configuring test retries in specific frameworks (e.g., Jest's `jest.retryTimes()`, pytest-rerunfailures `--reruns` flag, Cypress retry configuration).
Include a clear workflow: 1) identify flaky test, 2) add retry config, 3) validate retry behavior, 4) review retry logs to confirm the root cause is addressed.
Remove generic filler sections ('Purpose', 'Capabilities', 'Example Triggers') and replace with actionable content—specific configuration snippets, common pitfalls, and when retries are appropriate vs. when to fix the underlying flakiness.
Add references to related detailed files or documentation for advanced retry strategies (e.g., exponential backoff, conditional retries, per-test vs. global retry config).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler text that provides no actionable information. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vague platitudes that waste tokens without teaching Claude anything it doesn't already know. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no specific commands, no configuration snippets, no framework-specific retry patterns. The skill describes what it could do rather than instructing Claude how to do it. | 1 / 3 |
Workflow Clarity | No steps, no sequence, no validation checkpoints are provided. The skill merely states it 'provides step-by-step guidance' without actually containing any steps for configuring test retries. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic sections with no references to detailed files, no links to examples, and no meaningful structure that aids navigation or discovery. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%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 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3076d78
- 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.