reinstalling-grove SKILL.md skillC

reinstalling-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/reinstalling-grove@git:20260930.45159a6

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

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

Use when a user wants to reinstall, update, or upgrade Grove after pulling new code, or when they report seeing the OLD UI / stale behavior after an update ("I still see the old dashboard", "the redesign isn't showing", "I reinstalled but nothing changed"). Covers the editable uv-tool install model, the independently-updated surfaces (package/CLI/TUI, daemon, webapp, plus the opt-in grove-mcp server in either its stdio or networked transport), the reinstall-vs-restart decision, a required…

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

# Reinstalling & updating Grove

[Grove](https://github.com/bearlike/Grove) ships as one Python package whose
surfaces update through **different mechanisms** — three core ones (CLI/TUI,
daemon, webapp) plus the opt-in `grove-mcp` server, whose
staleness rules differ by transport. Most "I updated but
still see the old version" reports come from updating one surface and forgetting
another, or from a process/browser still holding the old code. This skill makes
the update deterministic and gives you a decision tree for the stale-UI case.

The golden rule, and the thing to repeat to the user: **new code on disk does
not change anything already running.** A live process loaded its modules at
startup; a long-lived service keeps running the old build until restarted; a
browser serves a cached page. Updating Grove is therefore never "just pull" — it
is pull, then refresh each surface that needs it.

## 1. The surfaces and how each updates

| Surface | What it is | How it picks up new code |
|---|---|---|
| **Package — CLI + TUI** | the `grove` command and its Textual UI | a fresh `grove` invocation (editable install) OR a `uv tool install --reinstall` when deps changed |
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add bearlike/grove/reinstalling-grove@sha256:5f123a42ca819d52

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

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

Versions

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

version	committed	commit	size	audit
git:20260930.45159a6 latest	2026-09-30	45159a6	17,682 B	C	view · diff
git:20260908.bbb0fcb	2026-09-08	bbb0fcb	16,802 B	C	view · diff
git:20260803.49581e6	2026-08-03	49581e6	15,826 B	C	view

Audit of the latest version

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

fail: No prompt-injection phrasing (matched: Do not tell the user)
fail: No link to a raw IP address (matched: http://127.0.0.1:7421)
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (17682 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 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 script tag

Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.

Source

GitHub

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

API

GET https://markdownregistry.com/api/v1/artifacts/art_myorlsiyoar5ppep
GET https://markdownregistry.com/api/v1/resolve?ref=bearlike/grove/reinstalling-grove
GET https://markdownregistry.com/api/v1/blob/5f123a42ca819d52de8b83db8a2c4ae2eaf2d49b3751bbbea726187c7330e3dd

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.