collaborating-on-diagrams skillA
collaborating-on-diagrams is agent-read markdown (skill) from bearlike/grove: Use when working with an existing .drawio diagram through Grove collaboration. Triggers on opening, reading, editing, updating, stopping, or recovering a diagram in a Grove workspace. Covers revisioned managed writes, XML-preserving edits, collaboration state, conflicts, read-only stop, and container/editor limits..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Collaborating on diagrams Use Grove's diagram tools for a human-and-agent edit of one existing `.drawio` file in a workspace. The file remains the source of truth. Grove does not create new diagrams, commit changes, publish diagrams, or share them publicly. This skill is for managed collaboration, not ordinary source editing. Before a managed session exists, use your normal editor or shell. Once it is active, use the diagram tools for every read and write to that file. ## Start with the existing file Open an existing workspace-relative `.drawio` path. Do not pass an absolute path, a parent traversal, a symlink, or another file type. ```text grove_open_diagram(workspace_id="WORKSPACE_ID", path="architecture.drawio") ``` The open result contains the current XML and its revision. It creates a collaboration identity for the workspace and is idempotent only for the same active path. Its `diagram.session_id` is the identity for later updates and its `diagram.mode` is `active`. Opening another path while one is active is a conflict: finish the first session with `grove_stop_diagram`, then open the other file. Read the document through Grove before proposing an edit: ```text …
Read the whole file at its exact version.
How to install
mdr add bearlike/grove/collaborating-on-diagrams@git:20260908.bbb0fcbmdr add bearlike/grove/collaborating-on-diagrams@sha256:d9f787434b16264cPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_i6s5slanugdt4c6e)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8494 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
bearlike/grove · 7 stars · license MIT · pushed 2026-09-23 · branch current
API
GET https://markdownregistry.com/api/v1/artifacts/art_i6s5slanugdt4c6e GET https://markdownregistry.com/api/v1/resolve?ref=bearlike/grove/collaborating-on-diagrams GET https://markdownregistry.com/api/v1/blob/d9f787434b16264c29a83b90402f62dc6b35472f5986bf426638fd761bcfc816
Your agent 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.