Install
$ agentstack add skill-swapnildahiphale-opensre-infrastructure-neo4j ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Infrastructure Knowledge Graph (Neo4j)
When to use
- Before starting an investigation, to understand the service topology
- When you need to know what depends on a service (blast radius analysis)
- When you need Kubernetes status of a service (pods, deployments, replicas)
- When you need to understand the relationship between services
How to use
Get service topology
python /app/tools/neo4j_semantic_layer.py --action service-info --service
Get Kubernetes status
python /app/tools/neo4j_semantic_layer.py --action k8s-status --service
Get service relationships
python /app/tools/neo4j_semantic_layer.py --action relationships --service
Run custom Cypher query
python /app/tools/neo4j_semantic_layer.py --action cypher --query "MATCH (s:Service) RETURN s.name LIMIT 10"
Methodology
- Pre-investigation context: Before analyzing logs or metrics, query the KG to understand:
- What the service does
- What depends on it (downstream impact)
- What it depends on (upstream causes)
- Current K8s health status
- Blast radius analysis: When a service is affected:
- Query all downstream dependencies
- Check if downstream services also show errors
- Report the full blast radius
- Root cause correlation: When multiple services are affected:
- Query the topology to find common upstream dependencies
- The shared dependency is likely the root cause
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: swapnildahiphale
- Source: swapnildahiphale/OpenSRE
- License: Apache-2.0
- Homepage: https://opensre.in
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.