run-integration-tests

Use when asked to run integration tests.

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/run-integration-tests/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

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

The content is admirably concise and well-scoped, but it offloads essentially all executable guidance to an external README that is not part of the skill bundle and omits any validation step for a test-running workflow. This leaves it actionable only as a pointer rather than as standalone instruction.

Suggestions

Inline the key executable command(s) for running the integration tests so the skill is actionable without reading an external file.

Add an explicit validation/verification checkpoint (e.g., 'run the suite, then confirm all tests pass or report failures') so the workflow clears the batch/verification cap.

If the README contains essential detail, bring it into the skill bundle as a one-level reference with a clearly signaled link.

Dimension	Reasoning	Score
Conciseness	The body is two lean sentences with no padding and no over-explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.	5 / 5
Actionability	The guidance gives a concrete path and tells Claude to read a README, but the actual executable steps are offloaded to an external file that is not part of the skill bundle, fitting 'minimal concrete guidance; high-level hints but missing the specific steps to execute'.	2 / 5
Workflow Clarity	Only a single unsequenced action is given with no validation or verification checkpoint for what is a test-running (verification) operation, and the rubric caps verification/batch workflows without validation at 3.	3 / 5
Progressive Disclosure	The tiny, well-sectioned body is appropriately scoped for an under-50-line skill, but it points to an external README path outside the bundle rather than a clearly signaled one-level-deep bundle reference, leaving minor organization gaps.	4 / 5
	Total	14 / 20 Passed

Description

48%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description provides a clear trigger but very thin capability information, naming only the generic action of running integration tests. It is reasonably distinct but lacks the concrete actions and keyword breadth of stronger examples.

Suggestions

Add 1-2 concrete actions beyond the generic 'run' (e.g., 'execute, parse failures, and report integration test results').

Broaden trigger terms with natural synonyms a user might say (e.g., 'integration tests', 'end-to-end tests', 'e2e suite').

Make the 'what' explicit rather than implied by the 'when' clause alone.

Dimension	Reasoning	Score
Specificity	The description names the domain ('integration tests') but the only action is the generic verb 'run', matching the anchor 'Names the domain but actions are minimal or generic'; it does not reach the 3-anchor's requirement of 1-2 concrete actions.	2 / 5
Completeness	An explicit 'when' trigger is present ('Use when asked to run integration tests') and a thin 'what' is implied, but the what is weak and not comprehensive, so it sits between the vague-what/only-when anchor and the both-clear anchor.	3 / 5
Trigger Term Quality	'integration tests' is a natural phrase a user would say, but coverage is limited to that single phrase with no synonyms or variations, fitting the 'some relevant keywords but missing common variations or synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	'run integration tests' is a fairly specific niche with only minor overlap risk against closely related testing skills, matching 'mostly distinct; minor overlap risk with closely related skills'.	4 / 5
	Total	12 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: flet-dev/flet
Path: .agents/skills/run-integration-tests/SKILL.md
Commit: 8f74fe9

Reviewed: 7 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.