How do I install the Dependency Mapping skill?

Run npx skillmds@latest add onedro1d/dependency-mapping in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dependency Mapping safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dependency Mapping?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dependency Mapping free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dependency Mapping?

OneDro1d (@onedro1d) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dependency Mapping by onedro1d — Agent Skill

Name: Dependency Mapping
Author: OneDro1d

Dependency Mapping

Trace a request/data flow end-to-end across services, queues, databases, object stores, and APIs to find every component a change or bug touches. Use when a problem spans boundaries or before changing a shared contract. Triggers on "trace the flow", "what depends on", "blast radius", "end to end path", "who consumes/produces".

OneDro1d e3494c9 1.6 KB Updated Sep 17, 2026

File contents

Dependency Mapping (cross-boundary tracing)

Goal: produce the exact chain of components a flow or change touches, so nothing downstream is missed. In a message-driven system, follow the routing keys, not just function calls.

Method

Start from .claude/context/SERVICE-MAP.md (the "In → Out" columns give the spine).
For each hop, confirm in code: producer's publish/routing key → the consumer whose config binds that key → its handler. Use the shared-models CLAUDE.md contract index to resolve names.
Note every store touched (DB table, graph edge, object-store key) and every API (HTTP route, gRPC RPC).
Flag the cross-service contracts that break silently if changed (object-store key shape, record field names, routing keys, shared DB columns).

Output (structured, hand to investigator/architect)

FLOW: <name>
HOPS: svc → (routingKey) → svc → ...   [each with file:line]
STORES: <DB tables / graph edges / object-store keys touched>
APIS: <HTTP routes / RPCs>
SHARED CONTRACTS AT RISK: <list>
UNKNOWNS: <what you could not confirm in code>

Don't

Don't assume the SERVICE-MAP diagram is current if code disagrees — report the drift.
Don't stop at the first service; a "fix" in one hop often needs the consumer updated too.

Frequently asked questions