run-integration-tests

Use when asked to run integration tests.

Quality

61%

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

72%

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

The body is admirably concise and uses a clean one-level reference to a README, but it stops short of giving an executable command or any verification step for the test run. It is efficient and well-structured yet only partially actionable.

Suggestions

Add the concrete command used to run the suite (e.g. the pytest or package-specific invocation) so Claude can act without first reading the README.

Include a brief verification step, such as checking the exit status or parsing the test report for failures, since running tests is a batch operation.

Confirm the referenced README path exists in the bundle or repo so the one-level reference does not dead-end.

Dimension	Reasoning	Score
Conciseness	The body is two lean lines with no fluff and no explanation of concepts Claude already knows; every token earns its place. This matches the 'lean and efficient; assumes Claude's competence' anchor.	3 / 3
Actionability	It provides concrete file paths (the integration_tests directory and README) but no executable command to actually run the tests, deferring the real instruction to the README. This matches the 'some concrete guidance but incomplete; missing key details' anchor rather than the fully-executable anchor 3.	2 / 3
Workflow Clarity	As a simple single-task skill it is clear and well-organized, but running a test suite is a batch operation with no verification of pass/fail results, which caps workflow clarity at 2 per the scoring notes. It is above 1 because the steps are present and ordered, but lacks the validation checkpoint needed for 3.	2 / 3
Progressive Disclosure	The SKILL.md is a thin overview pointing one level deep to a clearly-signaled README ('Read ... for further instructions'), with no nested references and under 50 lines. This matches the 'clear overview with well-signaled one-level-deep references' anchor.	3 / 3
	Total	10 / 12 Passed

Description

50%

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 is terse and provides an explicit, natural trigger, but it does not enumerate concrete capabilities and leans almost entirely on the trigger clause for both what and when. It is functional but thin, scoring at the midpoint across all dimensions.

Suggestions

Add a short capability clause before the trigger, e.g. 'Runs the Flet Python integration test suite and reports results. Use when asked to run integration tests.'

Include natural trigger variations such as 'integration testing' or 'run the test suite' to improve trigger-term coverage.

Distinguish the skill from generic test runners by naming the specific package or framework it targets.

Dimension	Reasoning	Score
Specificity	The description names a domain ('integration tests') and one concrete action ('run'), matching the 'names domain and some actions' anchor. It is not a 1 because 'run' is a concrete action verb rather than abstract language, and not a 3 because it enumerates no multiple specific capabilities.	2 / 3
Completeness	It explicitly answers 'when' via the 'Use when asked to run integration tests' clause, but the 'what' is only implied by restating the trigger rather than described as a clear capability list. It is above 1 because an explicit trigger is present, but below 3 because the what is not clearly and separately articulated.	2 / 3
Trigger Term Quality	'run integration tests' is a natural phrase a user would say, but it is the only trigger phrase and omits common variations such as 'test suite' or 'integration testing'. This matches the 'some relevant keywords but missing common variations' anchor rather than the full-coverage anchor 3.	2 / 3
Distinctiveness Conflict Risk	'integration tests' is a reasonably specific niche, but the bare 'run tests' framing could overlap with general or unit test-running skills. This fits the 'somewhat specific but could still overlap' anchor rather than the clearly-distinct anchor 3.	2 / 3
	Total	8 / 12 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: db0df8e

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