test

Run unit tests, integration tests, or slow integration tests matching CI. Use to validate changes before submitting a PR.

1.13x

Quality

82%

Does it follow best practices?

Impact

100%

1.13x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

90%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 body is an efficient, highly actionable reference that gives exact commands for every argument with no fluff. It falls just short of top marks on workflow clarity and progressive disclosure, which lack explicit validation checkpoints and external reference structure respectively.

Dimension	Reasoning	Score
Conciseness	The body is lean: commands, tables, and short notes with no padding or explanation of concepts Claude already knows (Maven, JUnit, CI). Every token earns its place.	5 / 5
Actionability	Each argument maps to a copy-paste-ready, fully executable Maven command, and the module-name section provides concrete parameterized commands covering the common cases.	5 / 5
Workflow Clarity	The pick-argument-then-run-command flow is clear and the CI retry note warns about flaky results, but there are no explicit validation checkpoints beyond running tests themselves.	4 / 5
Progressive Disclosure	Content is self-contained with well-organized sections by argument and topic; no bundle files exist, and the inline CI reference table is appropriately placed, though a couple of sections could optionally be split out.	4 / 5
	Total	18 / 20 Passed

Description

75%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 is concise, concrete, and follows the recommended 'what + Use when...' pattern with specific test-type variants. It is strong but stops just short of the top anchor because the actions are variations of one verb and the trigger guidance is general rather than per-variant.

Dimension	Reasoning	Score
Specificity	Names the test domain and three concrete variants ('unit tests, integration tests, or slow integration tests'), but these are all variations of a single 'run tests' action rather than distinct operations, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('Run unit tests, integration tests, or slow integration tests matching CI') and when ('Use to validate changes before submitting a PR'), but the trigger clause could be more specific about when each variant applies.	4 / 5
Trigger Term Quality	Includes natural terms users would say ('unit tests', 'integration tests', 'validate changes', 'PR') with good coverage, though a few common synonyms or phrasings are missing.	4 / 5
Distinctiveness Conflict Risk	The CI-matching test execution niche is mostly distinct with clear triggers, with only minor overlap risk against a generic test-running skill.	4 / 5
	Total	16 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: apache/skywalking
Path: .claude/skills/test/SKILL.md
Commit: 521b2ab

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