Individual skill
memory-search
Search OpenSRE memory for past investigations similar to what you are seeing now. Use after you have concrete evidence (error message, failing component, stack trace)—not on vague initial alerts alone.
sre-agent/.claude/skills/memory-search/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)
- 179
- Repository last updated
- Nov 8, 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
- engineering 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,286 bytesSKILL.mdcore · 2,286 bytesSKILL.mdcore · 2,286 bytesscripts/search.pyruns · 2,858 bytes
Read excerpt
# memory-search
Search OpenSRE memory for past investigations similar to what you are seeing now.
## When to use
Use memory search **after** you have concrete evidence—not on vague initial alerts alone:
- You have an error message, stack trace, or failing job output
- You identified a failing component or service
- A symptom may have been investigated before and you want prior root causes or skills that worked
**Do not** search on ticket titles alone (e.g. "build pipeline failing"). Gather facts first (read Jenkins console, check logs), then search with an enriched query.
