agentleFS
kryptophonikkryptophonik/SRE-Skills/.claude/skills/sre-dependency-mapping/SKILL.md

sre-dependency-mapping

Skill4 starsChanged 23 days agoMITView on GitHub

Use for PRRs, reliability reviews, incident blast radius or chaos planning: map upstream/downstream services, criticality, timeouts/retries and single points of failure. Read-only.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Wait for explicit human approval before any prod-changing command, MCP write tool, or external post.

    line 12
  2. Distinctive:

    Ask owners to confirm; tools miss async (queues, batch, cron) links.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Dependency Mapping

Safety gates (REQUIRED)

  1. Read-only diagnosis first.
  2. Propose each change with risk (low/med/high) and reversibility.
  3. Wait for explicit human approval before any prod-changing command, MCP write tool, or external post.
  4. Act only as approved, verify, and stop and escalate if anything gets worse.

Full rules: sre-safety-gates. Read-only MCP setup: sre-safety-gates/references/mcp.md.

Workflow

  1. Discover (read-only):
    • APM/topology: Dynatrace Smartscape (sre-dynatrace), Datadog service map (sre-datadog), Tempo service graph (sre-prometheus-grafana).
    • Config: Kubernetes Services/Ingress, env vars and config maps naming hosts, Terraform state outputs.
    • Ask owners to confirm; tools miss async (queues, batch, cron) links.
  2. Classify each dependency: hard (request fails without it) vs. soft (degrades); sync vs. async.
  3. Record resilience settings: timeout, retries (with backoff/jitter?), circuit breaker, fallback, SLO of the dependency.
  4. Find risks: single points of failure, retry storms (retries × fan-out), missing timeouts, dependency SLO lower than ours, shared infra (one DB, one region).
  5. Blast radius: for each critical dependency, which user journeys fail.

Map template

# Dependency map: [service]

| Dependency | Direction | Hard/soft | Sync/async | Timeout | Retries | Fallback | Owner | Dep SLO |
|---|---|---|---|---|---|---|---|---|

## Diagram
[mermaid or link]

## Risks
- [SPOF / missing timeout / retry storm] — impact — fix — owner

Output

  • Dependency table, diagram (Mermaid graph LR is fine), ranked risks with fixes

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.