Name: grove-setup
Rating: 72.8 (1 reviews)
Author: mongodb

grove-setup

Set up a local Grove environment for running code example tests. Use when the user asks to "set up Grove", "configure the test suite", "get started with Grove", "set up my environment", "I need to run Grove tests", or is working with Grove for the first time and needs prerequisites configured. Checks for required tools, installs dependencies, guides .env file setup, verifies MongoDB connectivity, and checks sample data availability.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The body is highly actionable with clear sequencing and validation, but it is a long monolithic file that could benefit from splitting per-language and handoff detail into referenced files, and some prose blocks could be tightened for token efficiency.

Suggestions

Move the per-language prerequisite/dependency/smoke-test tables and the Step 0 extension-handoff schema into referenced files (e.g. references/handoff.md, references/suites.md) and link to them from SKILL.md to improve progressive disclosure.

Tighten the Step 0 handoff prose and the supportsEnvInjection explanation — consolidate the multi-paragraph branch logic into a compact table or bullet list to reduce token cost.

Consider condensing the duplicated language-suite tables (Steps 1, 2, 4, 7) into a single cross-referenced table since they repeat the same six suites with overlapping paths.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and operational with no basic-concept padding, but at ~370 lines it includes verbose prose blocks (notably the Step 0 handoff explanation and the supportsEnvInjection discussion) that could be tightened, matching the mostly-efficient-but-could-be-tightened score-2 anchor rather than every-token-earns-its-place.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands per suite with exact directory paths, version-check commands, and smoke-test commands, matching the executable-and-complete score-3 anchor rather than the pseudocode score-2 example.	3 / 3
Workflow Clarity	Steps 0–8 are clearly sequenced with explicit validation checkpoints ("Do not proceed past this step until the user confirms", Step 5 connectivity verify, Step 7 smoke test) and feedback loops for error recovery ("If connection fails → Diagnose"), matching the explicit-validation score-3 anchor.	3 / 3
Progressive Disclosure	No bundle files exist and the ~370-line body keeps everything inline — per-language tables and the detailed handoff section could be split into reference files — so it matches the some-structure-but-content-should-be-separate score-2 anchor rather than a well-signaled multi-file score-3.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 strong across all dimensions: it states concrete capabilities, lists multiple natural trigger phrases, explicitly covers both what and when, and occupies a clearly distinct Grove-setup niche. No changes needed.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Checks for required tools, installs dependencies, guides .env file setup, verifies MongoDB connectivity, and checks sample data availability" — matching the multi-action score-3 anchor rather than the partial coverage of score 2.	3 / 3
Completeness	Clearly answers both what (set up a local Grove environment plus the enumerated checks) and when via an explicit "Use when..." clause with multiple triggers, matching the both-what-and-when score-3 anchor instead of the implied-when score 2.	3 / 3
Trigger Term Quality	Includes natural phrasings a user would actually say ("set up Grove", "configure the test suite", "get started with Grove", "set up my environment", "I need to run Grove tests"), giving good coverage of natural variations rather than just some relevant keywords.	3 / 3
Distinctiveness Conflict Risk	The Grove-specific niche and setup-only triggers ("set up Grove", "get started with Grove") make it unlikely to fire for unrelated skills, matching the clear-niche score-3 anchor rather than the overlapping score-2 example.	3 / 3
	Total	12 / 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: mongodb/docs
Commit: e765459

Reviewed: about 22 hours 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.