agentleFS
stoa-platformstoa-platform/stoa/.claude/skills/impact/SKILL.md

impact

Skill9 starsChanged 7 months agoApache-2.0View on GitHub

User runs /impact <service> to answer: "If I kill this service, what breaks?" If service not found, show the error (lists available services). Display the table output from --reverse — shows all impacted services with depth (direct vs transitive) and type. Display the Mermaid subgraph (colored: red=down, orange=direct, yellow=transitive). If kubectl is available and configured, enrich with pod status: Present enriched table: If kubectl is unavailable, skip enrichment and note: "kubectl not available — showing static graph only." Output a…

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use debug and docs.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    debug

    Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    docs

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If service not found, show the error (lists available services).

    line 15
  2. Very specific:

    If kubectl is available and configured, enrich with pod status:

    line 31
  3. Distinctive:

    If kubectl is unavailable, skip enrichment and note: "kubectl not available — showing static graph only."

    line 45

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “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

/impact — Service Impact Analysis

Trigger

User runs /impact <service> to answer: "If I kill this service, what breaks?"

Steps

1. Validate Service

./scripts/ops/catalog-graph.sh --reverse <service>

If service not found, show the error (lists available services).

2. Show Reverse Dependencies

Display the table output from --reverse — shows all impacted services with depth (direct vs transitive) and type.

3. Show Impact Graph

./scripts/ops/catalog-graph.sh --impact <service>

Display the Mermaid subgraph (colored: red=down, orange=direct, yellow=transitive).

4. Enrich with Live State (optional)

If kubectl is available and configured, enrich with pod status:

# For each impacted service, check live state
kubectl get pods -n stoa-system -l app=<service-name> -o wide --no-headers 2>/dev/null

Present enriched table:

ServiceImpactPodsStatusImage
control-plane-apidirect2/2Runningghcr.io/stoa-platform/control-plane-api:latest
control-plane-uitransitive1/1Runningghcr.io/stoa-platform/control-plane-ui:latest

If kubectl is unavailable, skip enrichment and note: "kubectl not available — showing static graph only."

5. Summary

Output a one-line blast radius summary:

Blast radius: N services impacted (X direct, Y transitive) across Z types

Modes

CommandOutput
/impact <service>Full analysis (table + graph + live enrichment)
/impact <service> --staticSkip kubectl enrichment (graph only)

Rules

  • Read-only — never modify any service or infrastructure
  • No IPs — never display IP addresses in output
  • No secrets — never display secret values
  • Graceful degradation — if kubectl fails, fall back to static graph
  • Catalog is source of truth — live state enriches but doesn't replace catalog data

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.