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.
Overall
score
23%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill test-retry-configActivation
7%This description is severely underdeveloped, functioning more as a label than a useful skill description. It lacks any concrete actions, meaningful trigger terms, or guidance on when to use it. The repeated trigger term and boilerplate category mention provide almost no value for skill selection.
Suggestions
Add specific concrete actions like 'Configure test retry attempts, set failure thresholds, handle flaky test detection, and manage timeout settings for test suites'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions flaky tests, test retries, rerunning failed tests, or configuring test timeout behavior'
Add natural keyword variations users would actually say: 'flaky tests', 'retry failed', 'test timeout', 'rerun tests', 'test stability'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only 'Auto-activating skill for Test Automation' which is vague and abstract. No specific capabilities like 'configure retry attempts', 'set timeout values', or 'handle flaky tests' are mentioned. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming a category, and has no explicit 'Use when...' clause or equivalent guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'test retry config' repeated twice, which is redundant and overly specific jargon. Missing natural variations users might say like 'flaky test', 'retry failed tests', 'test timeout', or 'rerun tests'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Test Retry Config' is somewhat specific to a niche area, the lack of concrete details means it could overlap with general test automation or configuration skills. The category mention provides some distinction. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%This skill is a hollow template with no actual content about test retry configuration. It describes what a skill should do in generic terms but provides zero actionable guidance, no code examples, no framework-specific configuration, and no concrete steps. The content would be identical if you replaced 'test retry config' with any other topic.
Suggestions
Add concrete code examples showing retry configuration for specific frameworks (e.g., Jest's `jest.retryTimes()`, pytest-rerunfailures, or Playwright's `retries` option)
Include a clear workflow: 1) Identify flaky tests, 2) Configure retry settings, 3) Set appropriate retry counts, 4) Add logging/reporting for retried tests
Remove generic boilerplate sections ('Capabilities', 'Example Triggers') and replace with actual configuration snippets and best practices
Add specific guidance on when retries are appropriate vs. when tests should be fixed, including anti-patterns to avoid
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about test retry configuration. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does in abstract terms but never shows how to actually configure test retries in any framework. | 1 / 3 |
Workflow Clarity | No steps, sequences, or processes are defined. The content only lists vague capabilities without any workflow for implementing test retry configuration. | 1 / 3 |
Progressive Disclosure | The content has some structure with clear sections, but there are no references to detailed materials, examples, or configuration files. The organization exists but leads nowhere useful. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.