grove-migrate

Migrate existing untested code into the Grove test suite. Use when the user asks to "migrate this code", "convert to Grove", "make this testable", "move this example to the test suite", "add tests for this existing code", "migrate the code on this page", or wants to convert documentation code examples that currently live outside of Grove into properly tested, snippeted examples. Supports both page-level migration (scan an RST page for all code) and snippet-level migration (convert a single code block).

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

A thorough, highly actionable migration workflow with strong validation feedback loops and well-structured progressive disclosure into real reference files. The only weakness is mild verbosity from cross-step repetition that could be consolidated.

Suggestions

Consolidate the partial-file-inclusion (:start-after:/:end-before:) guidance so it lives in one place (Step 7 or Edge Cases) rather than being restated, to reduce token cost.

Centralize the sample-data teardown rule ('do NOT drop sample databases') once and reference it, instead of repeating it in Steps 6, 8, and 10.

Consider moving the large Step 12 report-template/example tables into a reference file to keep the main body leaner while preserving the copy-paste templates.

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly free of concept-explanation padding, but its length and repetition (partial-file inclusion appears in both Step 7 and Edge Cases; drop-database cautions recur across Steps 6/8/10) mean it could be tightened without losing clarity.	2 / 3
Actionability	Provides concrete, copy-paste-ready guidance throughout: specific Bluehawk tags (:remove:/:replace:/:uncomment:), decision tables, a full reviewer subagent prompt template, and example report/discrepancy tables.	3 / 3
Workflow Clarity	Steps 0-12 are explicitly sequenced with validation checkpoints — Step 11 runs the test twice for idempotency, runs the snip command, and includes a bounded fix-retry feedback loop (max 3 attempts) before stopping.	3 / 3
Progressive Disclosure	Overview body cleanly offloads detail to three real one-level-deep reference files (references/page-scanning.md, references/data-adaptation.md, references/extension-handoff.md, all present) with well-signaled 'Read the reference file X for the full...' navigation.	3 / 3
	Total	11 / 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.

A high-quality description: concrete actions, abundant natural trigger phrases, explicit what-and-when guidance, and clear differentiation from sibling skills. No notable weaknesses.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Migrate existing untested code into the Grove test suite' plus 'page-level migration (scan an RST page for all code)' and 'snippet-level migration (convert a single code block)' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what (migrate untested code into the Grove test suite, supporting page-level and snippet-level modes) and when via a clear 'Use when...' clause with concrete triggers.	3 / 3
Trigger Term Quality	Strong coverage of natural phrasings a user would actually say: 'migrate this code', 'convert to Grove', 'make this testable', 'move this example to the test suite', 'add tests for this existing code', 'migrate the code on this page'.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (Grove test-suite migration) with distinct triggers and an explicit 'Do NOT use when' list redirecting to sibling skills, making false triggers unlikely.	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 23 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.