Bead Dependency Mapper
Use this agent when mapping bead dependencies — finding bottlenecks (open issues blocking the most other open work), detecting dependency cycles, or reasoning about the critical path through a bd Dolt database.
- Type
- Subagent
- Repository
- jeremylongshore/tons-of-skills-marketplace
- GitHub stars
- 2.8k
- License
- MIT
- Repo last updated
- Sep 27, 2026
- Model
- opus
- Version
- 0.1.0
- Author
- Jeremy Longshore
What Bead Dependency Mapper is
Bead Dependency Mapper is a subagent published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”
A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.
Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Bead Dependency Mapper and get back a compact result.
It is set up to use these tools: Read, Bash(bash ${CLAUDE_PLUGIN_ROOT}/scripts/dep-graph.sh:*), mcp__dolt-mcp-vcs__query, mcp__dolt-mcp-vcs__list_databases. Limiting tools is a good sign: the subagent can only do what those tools allow.
How to install Bead Dependency Mapper
Claude Code
- Download bead-dependency-mapper.md from the repository.
- Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
- Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Claude Cowork
- Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
- Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.
Inside the source file
An excerpt from plugins/mcp/dolt-mcp-vcs/agents/bead-dependency-mapper.md, shared under the repository's MIT license. Read the full file on GitHub.
You are a bead dependency mapper. You turn the dependencies table into actionable structure: which open issues are bottlenecks, where the cycles are, and what the critical path looks like.
Introspect the live schema — don't assume it. You run in your own context against the live database via the Dolt MCP. Before trusting any table/column name or dependency-type value, confirm it against the live DB (SHOW TABLES, information_schema.columns, SELECT DISTINCT type FROM dependencies). references/dolt-internals.md is only a directory of authoritative sources, not a schema snapshot — the live schema is the authority.
Your SQL access is read-only (blueprint §3). The mcpdolt-mcp-vcsquery tool is for SELECT/introspection only — never issue a mutation through it. Any write belongs on an agent-owned branch through the gated client (scripts/dolt-mcp-client.py); merge/push/reset/branch-delete are recommend-only, surfaced for a human.
Core Responsibilities
- Identify bottlenecks — open issues blocking the most other open issues.
- Detect dependency cycles (direct and, where feasible, indirect).
- Map the critical path / blocking chains toward a target issue.
- Answer ad-hoc dependency questions via SQL.
Process
- Find the database. Call mcpdolt-mcp-vcslist_databases to confirm the bead database name; set DOLT_DATABASE/DOLT_PORT.
- Run the canned analysis. bash ${CLAUDE_PLUGIN_ROOT:-.}/scripts/dep-graph.sh --top 10 returns the bottleneck ranking plus a direct-cycle check.
- Ad-hoc / deeper graphs. Call mcpdolt-mcp-vcsquery directly. The encoding: a blocks dependency row has issue_id = the BLOCKED issue and depends_on_id = the BLOCKER. Restrict to open-on-both-sides (status<>'closed') for actionable bottlenecks. Use recursive CTEs for multi-hop chains where needed.
- Interpret. Translate the ranking into "clear this issue first to unblock N others."
Quality Standards
- Distinguish blocks (scheduling dependency) from parent-child (epic membership) — only blocks defines the critical path.
- Filter to open-on-both-sides for bottlenecks; a closed blocker isn't blocking anything.
- Report IDs with titles.
Output Format
A ranked bottleneck table (blocker, blocking_open, title), a cycles section (ideally empty), and a one-line "unblock-first" recommendation.
Edge Cases
- No bottlenecks / no cycles is a healthy graph — report it positively.
- Deep recursive chains can be large; cap depth and say so rather than truncating silently.
- A self-dependency or cycle is a data bug — surface it for repair, don't treat it as normal structure.
Before you install
- Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
- Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
- Try it in a test project or a copy of your files before pointing it at real work.
- Pin the version you tested, and review changes before updating.
- Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.
FAQ
What is Bead Dependency Mapper?
Bead Dependency Mapper is a subagent for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Use this agent when mapping bead dependencies — finding bottlenecks (open issues blocking the most other open work), detecting dependency cycles, or reasoning about the critical path through a bd Dolt database.
How do I install Bead Dependency Mapper in Claude Code?
Download bead-dependency-mapper.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Can I use Bead Dependency Mapper in Claude Cowork?
Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
Is Bead Dependency Mapper safe to install?
It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.
Similar resources
- Cut Designs and manages icon systems and custom illustrations that extend the brand visually. Use when you need an icon system audit, an SVG optimization pass, or an illustration style spec. Trigger with \"audit the icon system\", \"optimize these SVGs\". Subagent · jeremylongshore/tons-of-skills-marketplace
- Data Collector Fetches raw analytics data from Umami MCP across all tracked sites and returns structured datasets for specialist agents — never interprets, only collects. Use when kicking off an analytics pipeline or pulling fresh metrics for any time range. Trigger with \"collect analytics data\", \"fetch site metrics\". Subagent · jeremylongshore/tons-of-skills-marketplace
- Data Generator Generates realistic, locale-aware test data (users, products, orders, custom schemas) using Faker.js, Factory Boy, or json-schema-faker — producing factory functions, database seed scripts, and fixture files ready for immediate use. Use when setting up a test environment or populating a dev database with production-scale data. Trigger with \"generate test data\", \"create seed data factories\". Subagent · jeremylongshore/tons-of-skills-marketplace
- Daily Health Check Execute SOP-101 Morning Health Check Routine for all FairDB VPS instances Slash Command · jeremylongshore/tons-of-skills-marketplace
- Bead Epic Auditor Use this agent when auditing bead epics for closure drift — finding open epics whose entire child set is already closed (so their GitHub/Plane cluster issue never got the close fan-out), or otherwise reasoning about epic/subtree completion across a bd Dolt database. Subagent · jeremylongshore/tons-of-skills-marketplace
- Batch Scheduler Plans efficient batch recording sessions that group multiple videos by topic, manage energy and breaks, and produce detailed run-of-show schedules to maximize output per recording day. Use when scheduling a recording block. Trigger with \"plan batch recording session\", \"schedule my recording day\". Subagent · jeremylongshore/tons-of-skills-marketplace
- Bead Recovery Specialist Use this agent for bd/Dolt incident response — a dolt-server that won't start or has orphaned, server sprawl, suspected lost writes after rapid bd updates, JSONL that lags the database, or migrating a workspace between embedded and server mode. It knows the rapid-write race is already fixed in bd 1.0.4 and that residual lag is only the JSONL export throttle. Subagent · jeremylongshore/tons-of-skills-marketplace
- Backend Architect Scalable backend system design expert covering monolith vs microservices trade-offs, caching strategies, message queues, gRPC, and containerized infrastructure patterns. Use when choosing an architecture pattern, designing for scale, or solving distributed system challenges. Trigger with \"backend architecture\", \"system design help\". Subagent · jeremylongshore/tons-of-skills-marketplace