configuring-grove SKILL.md skillA

configuring-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/configuring-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/configuring-grove/SKILL.md
Versions recorded: 5
Latest version: git:20260930.45159a6, committed Sep 30, 2026
First version recorded: Aug 3, 2026
Size: 30,330 bytes
Repository stars: 8
License: MIT

Use when configuring Grove for a user or project, including agent rosters, init scripts, containers, private credentials, daemon or MCP setup, or the native-versus-terminal launch of a Claude Code or Codex agent. Also use when resolving config layers, validating a config schema, or explaining why a workspace starts with unexpected runtime behavior. For fleet operation use using-grove. For an agent inside a workspace use working-in-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

# Configuring Grove

[Grove](https://github.com/bearlike/Grove) is a software factory for coding
agents. Each Grove workspace is one git worktree plus one tmux session running
an agent, scoped to the repository it is launched from. This skill helps
you configure Grove correctly for a user, both at the host/user level and per
project.

Your job: find out what the user wants, decide which config layer it belongs in,
write valid JSON, and **verify it against the version of Grove they actually have
installed**. Do not guess. Grove validates strictly and rejects unknown keys, so
a wrong field is a hard error, not a silent no-op.

## What people use this for

Common requests, and how to handle them:

- **"Set this repo up so every workspace is ready to code."** Configure a project
  `init_script` (committed in `<repo>/.grove/config.json`) that installs
  dependencies and prepares the tree, for example `uv sync`, `npm ci`, or
  `make bootstrap`. It runs in its own tmux window before the agent starts.
- **"Handle my secrets properly."** Never put secret values in the committed
  project config; it is meant to be shared. Reference environment variables
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add bearlike/grove/configuring-grove@sha256:e75d7b7600a83c17

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_wonrfm3mu6zrtplj.svg)](https://markdownregistry.com/a/art_wonrfm3mu6zrtplj)

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

Versions

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

version	committed	commit	size	audit
git:20260930.45159a6 latest	2026-09-30	45159a6	30,330 B	A	view · diff
git:20260921.13d222a	2026-09-21	13d222a	30,343 B	A	view · diff
git:20260908.bbb0fcb	2026-09-08	bbb0fcb	30,402 B	A	view · diff
git:20260821.3dfe12f	2026-08-21	3dfe12f	27,930 B	A	view · diff
git:20260803.49581e6	2026-08-03	49581e6	27,572 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 (30330 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_wonrfm3mu6zrtplj
GET https://markdownregistry.com/api/v1/resolve?ref=bearlike/grove/configuring-grove
GET https://markdownregistry.com/api/v1/blob/e75d7b7600a83c17b1f36d8bc3dd84262332c40d4d480baa8fb923ee30e8afc9

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.