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.

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill test-retry-config

What are skills?

1.00x

Quality

Does it follow best practices?

Impact

99%

1.00x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./planned-skills/generated/09-test-automation/test-retry-config/SKILL.md

SKILL.md

Review

Evals

Discovery

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 severely underdeveloped, functioning more as a placeholder than a useful skill description. It lacks any concrete actions, meaningful trigger terms, or explicit usage guidance. The repetitive trigger terms and boilerplate category mention provide almost no value for skill selection.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Configures retry attempts for flaky tests, sets timeout values, defines retry strategies for test suites'

Add a proper 'Use when...' clause with natural trigger scenarios, e.g., 'Use when configuring how tests should retry on failure, handling flaky tests, or setting up test resilience'

Include natural keyword variations users would actually say: 'flaky tests', 'retry failed tests', 'test timeout', 'rerun tests', 'test resilience'

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. The 'Triggers on' line is not a proper when clause - it just repeats the skill name.	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 but is insufficient.	2 / 3
	Total	5 / 12 Passed

Implementation

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is a placeholder template with no actual content about test retry configuration. It lacks any executable code, specific framework guidance (Jest, pytest, etc.), or concrete examples. The entire body consists of generic descriptions that could apply to any skill topic.

Suggestions

Add concrete code examples showing retry configuration for at least one framework (e.g., Jest's `jest.retryTimes()` or pytest-rerunfailures)

Include specific configuration snippets for common retry scenarios (flaky tests, network timeouts, CI environments)

Remove generic capability descriptions and replace with actual implementation guidance

Add a quick-start section with copy-paste ready configuration for the most common use case

Dimension	Reasoning	Score
Conciseness	The content is padded with generic boilerplate that explains nothing specific 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 abstractly 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 explaining any actual workflow for configuring test retries.	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

81%

Warnings & errors only

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

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.