using-grove SKILL.md skillA

using-grove from bearlike/grove is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add bearlike/grove/using-grove@git:20260930.45159a6

Pins git:20260930.45159a6 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: bearlike/grove
Path: src/grove/skills/using-grove/SKILL.md
Versions recorded: 7
Latest version: git:20260930.45159a6, committed Sep 30, 2026
First version recorded: Aug 3, 2026
Size: 21,010 bytes
Repository stars: 8
License: MIT

Use when orchestrating Grove workspaces from outside, including creating or supervising host or container agents, steering a fleet, using Grove CLI or MCP tools, or having agents write to each other through the mailbox. Also use when splitting work across workspaces, reviewing a diff from several angles, managing ticket links, or checking who needs attention. For a worker reporting from inside a workspace use working-in-grove. For setup use configuring-grove.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Using Grove

[Grove](https://github.com/bearlike/Grove) runs a fleet of coding agents that
live outside your context rather than sub-agents inside it. Each workspace is a
whole separate agent process with its own runtime, its own context window and
its own git worktree, addressable from outside. You create, steer, watch, pause,
resume, respawn and kill them.

Reach for Grove when you want parallel workspaces that outlive a single turn.
For quick in-session parallelism across a few scoped sub-tasks, plain sub-agents
are lighter and fit better.

Grove earns its keep on work too big, too parallel or too cross cutting for one
agent in one context.

- **Decompose and parallelize.** Split by component and spin up one workspace
  per slice. Each gets a clean worktree, so they never touch each other's files.
- **Triage at scale.** Forty Sentry issues or a whole backlog, one workspace per
  issue or per cluster. Each agent investigates independently and you review
  results rather than noise.
- **Work one ticket from several angles at once.** Implementation, tests and
  docs run in parallel in separate environments instead of one after another.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add bearlike/grove/using-grove@sha256:93def194e7af1518

The line at the top of this page pins the label git:20260930.45159a6, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_y6avuqfxe5m574gn.svg)](https://markdownregistry.com/a/art_y6avuqfxe5m574gn)

4 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 7 versions of this file, between Aug 3, 2026 and Sep 30, 2026, about one every 10 days.

version	committed	commit	size	audit
git:20260930.45159a6 latest	2026-09-30	45159a6	21,010 B	A	view · diff
git:20260923.1a5058d	2026-09-23	1a5058d	20,792 B	A	view · diff
git:20260921.13d222a	2026-09-21	13d222a	20,351 B	A	view · diff
git:20260908.bbb0fcb	2026-09-08	bbb0fcb	20,991 B	A	view · diff
git:20260821.3dfe12f	2026-08-21	3dfe12f	18,474 B	A	view · diff
git:20260812.6377c5a	2026-08-12	6377c5a	18,424 B	A	view · diff
git:20260803.49581e6	2026-08-03	49581e6	17,432 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (21010 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

bearlike/grove · 8 stars · license MIT · pushed 2026-10-02 · branch current

API

GET https://markdownregistry.com/api/v1/artifacts/art_y6avuqfxe5m574gn
GET https://markdownregistry.com/api/v1/resolve?ref=bearlike/grove/using-grove
GET https://markdownregistry.com/api/v1/blob/93def194e7af1518fb741cf741a6e00c1c0d817931b8858a1c7d25ff663d7771

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.