Individual skill
infrastructure-neo4j
Query the OpenSRE knowledge graph for service topology, dependencies, and blast radius. Use after you identify an affected service or deployment — not on vague initial alerts alone.
sre-agent/.claude/skills/infrastructure-neo4j/SKILL.md
Source commit 2323af0551856ff4669b73dc36329d16aa19ed24
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 178
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-sre Repository topic
- site-reliability-engineering Repository topic
- ai-agent Repository topic
- devops Repository topic
- episodic-memory Repository topic
- incident-investigation Repository topic
- incident-response Repository topic
- knowledge-graph Repository topic
- sre-agent Repository topic
- self-hosted Repository topic
- devops Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,174 bytesSKILL.mdcore · 2,174 bytesSKILL.mdcore · 2,174 bytesSKILL.mdcore · 2,174 bytesSKILL.mdcore · 2,174 bytesscripts/get_k8s_status.pyruns · 911 bytesscripts/query_relationships.pyruns · 914 bytesscripts/topology_search.pyruns · 2,670 bytes
Read excerpt
# infrastructure-neo4j
Query the OpenSRE knowledge graph (Neo4j) for service topology, dependencies, and blast radius.
## When to use
Use **after** you know which service or deployment is affected:
- Alert or ticket names a service (checkout, payments, surveys build target)
- Logs or metrics identify a failing deployment
- You need blast radius — what depends on this service, what it depends on
**Do not** query on vague tickets alone (e.g. "build pipeline failing" with no service). Gather evidence first, then query with the service name.
