grove-run

Run Grove tests and diagnose failures. Use when the user asks to "run the tests", "run my test", "debug this test failure", "why is this test failing", "check if tests pass", or wants to execute and troubleshoot code example tests.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

88%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.

A highly actionable, well-sequenced run-and-debug workflow with concrete commands and validation feedback loops throughout. The main improvement opportunity is progressive disclosure: the per-language command catalog and failure taxonomy are large enough to justify pulling into reference files.

Suggestions

Move the per-language command catalogs (Step 3) into per-language reference files (e.g. references/commands-javascript.md) and keep SKILL.md as an overview with one-level-deep links, to improve progressive_disclosure.

Extract the failure taxonomy (Step 4 categories) into a references/diagnosing-failures.md and summarize the categories inline, reducing SKILL.md length.

Trim the Step 0 handoff schema and verbose example messages into a references/extension-handoff.md, retaining only the essential version/shape checks inline.

Dimension	Reasoning	Score
Conciseness	The body is dense and information-rich — exact commands, flags, and env caveats — with little concept re-explanation, though some edge-case prose and the long handoff schema could be trimmed or moved to a reference.	4 / 5
Actionability	Per-language commands are copy-paste ready with concrete name-pattern examples (e.g. `npm test -- -t '{describe or it text}'`, `-run TestExampleOperations/YourName`, `mvn -Dtest=...#testYourExample`), and failure categories map to specific fixes.	5 / 5
Workflow Clarity	Steps 0–6 are clearly sequenced with explicit feedback loops (re-run to confirm fixes, handoff version/shape checks) and guards on destructive actions (no auto-updating expected output files without asking).	5 / 5
Progressive Disclosure	Headers and sectioning are good, but no bundle files exist (references/scripts/assets all absent) and ~340 lines of per-language commands and failure taxonomy are inlined rather than split into one-level-deep reference files.	4 / 5
	Total	18 / 20 Passed

Description

91%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.

A strong, third-person description that pairs a concrete capability statement with five realistic trigger phrases, cleanly answering both what and when. Its only weakness is that sibling-skill disambiguation is deferred to the body rather than the description itself.

Dimension	Reasoning	Score
Specificity	"Run Grove tests and diagnose failures" names two concrete actions in a specific domain (Grove, code example tests), with only minor gaps in coverage of what diagnosis entails.	4 / 5
Completeness	It explicitly answers both what ("Run Grove tests and diagnose failures") and when ("Use when the user asks to..." with concrete trigger phrases).	5 / 5
Trigger Term Quality	Five natural user phrases are quoted — "run the tests", "run my test", "debug this test failure", "why is this test failing", "check if tests pass" — giving comprehensive coverage including synonyms.	5 / 5
Distinctiveness Conflict Risk	The Grove test-run/debug niche is distinct with clear triggers, but the description alone carries minor overlap risk with sibling grove-* skills whose disambiguation lives in the body rather than the description.	4 / 5
	Total	18 / 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: mongodb/docs
Path: .claude/skills/grove-run/SKILL.md
Commit: d9cb237

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