synergy-tracker SKILL.md skillA
synergy-tracker from voxpelli/claude-beads is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add voxpelli/claude-beads/synergy-tracker@git:20260604.119543aPins git:20260604.119543a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- voxpelli/claude-beads
- Path
skills/synergy-tracker/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260604.119543a, committed Jun 4, 2026
- First version recorded
- May 8, 2026
- Size
- 48,798 bytes
- Repository stars
- 3
- License
- MIT
Manage cross-project synergy tracking between sibling projects. Use when the user wants to log a shared pattern, a divergence, an extraction candidate, or something a sibling project has that this one doesn't. Also use when the user wants to promote synergy entries to Basic Memory (workflow 5). NOT for upstream dependency bugs or vendor friction (use /upstream-tracker for those). Trigger phrases: 'synergy', 'sibling project', 'cross-project', 'extraction candidate', 'compare with [project]'…
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
# Synergy Tracker
Manage the `SYNERGY-*.md` files that track shared patterns, divergences,
extraction candidates, and capabilities observed in sibling projects while
building this one. This skill tracks patterns and capabilities across
peer/sibling projects under the same maintainer — not upstream dependency
friction (use `/upstream-tracker` for that).
## Tracking Files
### Sibling projects (permanent files)
Sibling projects are declared in `.claude/synergy-registry.json` (if it exists)
as an array of `{name, file, remote, bm-entity, relationship}` objects. See
`references/synergy-entry-format.md` for the full registry schema.
To discover which projects are registered, read `.claude/synergy-registry.json`
if it exists. If it does not exist, glob for `SYNERGY-*.md` to infer sibling
names from existing files. If neither is present, ask the user which sibling
project is involved before proceeding.
### File naming
Files are named `SYNERGY-<project-name>.md`. The project name is taken from
the `name` field in the registry (tier 3 of the canonical derivation
algorithm — synergy-tracker's subject is always sibling). For projects
…Read the whole file at its exact version.
How to install
mdr add voxpelli/claude-beads/synergy-tracker@sha256:a602bd864b2a70baThe line at the top of this page pins the label git:20260604.119543a, 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.
[](https://markdownregistry.com/a/art_uzwa7yd4p64p6jat)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 8, 2026 and Jun 4, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260604.119543a latest | 2026-06-04 | 119543a | 48,798 B | A | view · diff |
| git:20260603.95c01bc | 2026-06-03 | 95c01bc | 46,561 B | A | view · diff |
| git:20260602.6cb05c5 | 2026-06-02 | 6cb05c5 | 41,814 B | A | view · diff |
| git:20260508.73fb529 | 2026-05-08 | 73fb529 | 41,183 B | A | view · diff |
| git:20260508.9643390 | 2026-05-08 | 9643390 | 40,110 B | A | view |
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 (48798 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
voxpelli/claude-beads · 3 stars · license MIT · pushed 2026-10-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_uzwa7yd4p64p6jat GET https://markdownregistry.com/api/v1/resolve?ref=voxpelli/claude-beads/synergy-tracker GET https://markdownregistry.com/api/v1/blob/a602bd864b2a70ba9823f93532ed78be6382fdad50578236e8894c66623dbde9
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.