Agent skill · Audited from source
Memtrace Incident Investigation
skill · syncable-dev/memtrace-publicNOASSERTION licenceAudited 29 Oct 2026 · source 3e7894d935d8
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 3e7894d935d8 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Investigate source-code bugs, incidents, regressions, production issues, and failures to root cause with Memtrace symbol search, impact, call graph, and temporal history. Use when the user asks about root cause…
Cite
Cite this page
ModelsAtlas. “Memtrace Incident Investigation (syncable-dev/memtrace-public)”. Retrieved 29 Oct 2026. https://modelsatlas.com/skills/syncable-dev/memtrace-incident-investigation
Trust audit
Audit 0.4.1 · source read 29 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 17,406 of 18,389 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 3e7894d935d8 · 29 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publishersyncable-dev GitHub organizationOwner of the repository this skill is read from
- Source foldersyncable-dev/memtrace-public/plugins/memtrace-skills/skills/memtrace-incident-investigationThe exact folder we audited
- LicenceNOASSERTIONAs the repository states it
- Commit pinned for this verdict3e7894d935d8A new audit runs when the source changes
- Repository statusNot archivedLast push 1 day ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Investigate source-code bugs, incidents, regressions, production issues, and failures to root cause with Memtrace symbol search, impact, call graph, and temporal history. Use when the user asks about root cause…
---
name: memtrace-incident-investigation
description: "Investigate source-code bugs, incidents, regressions, production issues, and failures to root cause with Memtrace symbol search, impact, call graph, and temporal history. Use when the user asks about root cause analysis, what broke, or what changed when debugging a failure. Do not start with Grep, Glob, rg, find, or manual file search for code causes. For plain what-changed questions without a failure, use memtrace-evolution."
---
## Overview
Root cause investigation workflow for incidents, regressions, and production issues. Uses `get_evolution` to list changes near the incident time, then traces blast radius and execution flows to identify the likely cause.
## Steps
### 1. Establish the timeline
Determine:
- **Incident time** — when did the problem start? (This becomes the `to` parameter)
- **Lookback window** — how far back to search? Start with 24 hours, expand if needed.
- **Repo(s)** — which services are affected? Call `list_indexed_repositories` to get repo_ids.
### 2. List changes near the incident
Call `get_evolution`:
```json
{
"repo_id": "<affected-repo>",
"from": "<incident_time minus lookback, e.g. 24h before>",
"to": "<incident_time ISO-8601>",
"mode": "recent",
"limit": 100
}
```
**Why `recent` mode?** Returns a chronological per-episode changelog. Focus on episodes whose `reference_time` is closest to the incident — especially those with high `nodes_added` + `nodes_removed` or that touch files in the failure area.
Paginate with `cursor` if `next_cursor` is present in the response.
**Success criteria:** A list of episodes in the window, with touched files and change counts for each.
### 3. Identify hotspot files and symbols
Call `get_evolution` again on the same window with `mode: "compound"`:
```json
{
"repo_id": "<affected-repo>",
"from": "<same as step 2>",
"to": "<same as step 2>",
"mode": "compound"
}
```
Review `top_changed_files` and `top_touched_symbols`. Cross-reference with the failure area (endpoint, module, error stack).
**Decision:** Prioritize symbols/files that appear in both the recent episode list (step 2) and the compound hotspots (step 3).
### 4. Check for unexpected changes to stable code
For hotspot symbols from step 3, resolve each with `find_symbol`:
```json
{ "repo_id": "<affected-repo>", "name": "<symbol>", "limit": 10 }
```
Then call `get_timeline` — stable code that suddenly changed is suspect:
```json
{ "repo_id": "<affected-repo>", "scope_path": "<from find_symbol>", "file_path": "<from find_symbol>" }
```
### 5. Assess the blast radius
For the top 3–5 symbols, call `get_impact`:
```json
{ "repo_id": "<affected-repo>", "target": "<symbol>", "direction": "upstream" }
```
- How many downstream consumers were affected?
- What execution flows pass through this symbol?
**Decision:** Prioritize symbols where the blast radius overlaps with the reported failure area.
### 6. Trace execution flows
Use `get_symbol_context` on the top suspects to see which processes (HTTP handlers, background jobs, etc.) they participate in.
**Decision:** If the incident is in a specific endpoint/flow, focus on suspects that are members of that process.
### 7. Build the full timeline for the suspect
Once you have a primary suspect, call `get_timeline` with `repo_id`, `scope_path`, and `file_path`:
- What changed in each episode?
- When was the last "stable" version?
- Was the change a modification, or was it newly added?
### 8. Correlate adds vs removes per episode
From the step 2 `recent` response, inspect each episode's `nodes_added` and `nodes_removed`:
- High `nodes_added` — new code introduced (potential new bugs)
- High `nodes_removed` — deleted code (potential missing functionality)
- Both moderate — changed behaviour (potential regressions)
### 9. Check historical coupling (cochange)
For the primary suspect, call `get_cochange_context`:
```json
{ "repo_id": "<affected-repo>", "target": "<symbol>", "limit": 10 }
```
- Which symbols historically co-change with this one?
- If the blast radius from `get_impact` doesn't explain the failure area, check cochange partners — the coupling may be behavioral, not structural.
**Decision:** If a cochange partner is in the failure area but has no direct call relationship to the suspect, it's a hidden dependency — investigate both.
### 10. Replay the sub-commit implementation history (if needed)
If the suspect's episode isn't clear, call `get_episode_replay`:
```json
{
"repo_id": "<affected-repo>",
"episode_index": 0,
"symbol": "<suspect>",
"mode": "graph_summary"
}
```
- Look for `attempted_and_reverted` hints — approaches tried and rolled back within the episode often explain why the committed state looks the way it does.
## Report: Root Cause Analysis
1. **Incident Timeline** — when it started, what was observed
2. **Most Likely Cause** — episodes and symbols closest to the incident with blast radius confirmation
3. **Supporting Evidence** — timeline sparsity (stable code suddenly changed?), blast radius overlap, process membership overlap
4. **Change History** — full timeline of the suspect symbol
5. **Affected Scope** — all processes and downstream consumers impacted
6. **Remediation** — revert the change, fix forward, or mitigate
## Tool selection guide for incidents
| Phase | Tool / mode | Why |
|---|---|---|
| Initial triage | `get_evolution` `recent` | Per-episode changelog near the incident |
| Hotspot identification | `get_evolution` `compound` | Top changed files and symbols in the window |
| Scope assessment | `get_impact` | Blast radius of suspect symbols |
| Hidden coupling | `get_cochange_context` | Behavioral coupling not in the call graph |
| Symbol history | `get_timeline` | Full version history of a suspect |
| Sub-commit intent | `get_episode_replay` | What was tried before the committed state |
| Quick window check | `get_evolution` `overview` | Totals only — use before narrowing the wExcerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 3e7894d
git clone https://github.com/syncable-dev/memtrace-public git -C memtrace-public checkout 3e7894d935d8
The author documents no install command, so this uses the repository directly. Our verdict covers commit 3e7894d935d8 only.
Works in which agents?
What its own text says, not a test
| Agent | Status | More |
|---|---|---|
| Cursor | Mentioned in its text, not tested | Skills for Cursor · About Cursor |
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
3e7894d935d8
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/syncable-dev/memtrace-incident-investigation/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
All coding & review skills →syncable-dev/memtrace-public
Map source-code relationships between symbols. Use when the user asks about callers, callees, references, imports, exports, type usages, class hierarchy, inheritance, implementations, overrides, or dependencies between…
syncable-dev/memtrace-public
Find source code with Memtrace hybrid BM25+semantic search: symbols, functions, classes, types, constants, definitions, implementations, logic, or error strings inside code. Use when the user wants to find, search,…
syncable-dev/memtrace-public
Catch up on everything that changed in an indexed source-code repo since the last session, using stored session anchors and Memtrace change memory. Use when the user asks to continue, catch up, resume, see what changed…
syncable-dev/memtrace-public
Index a source-code repo into the Memtrace knowledge graph and poll the job to completion. Use when the user asks to index, parse, ingest, reindex, watch, or prepare a source-code repo for Memtrace analysis, when code…
syncable-dev/memtrace-public
Find dead code, complexity hotspots, and refactoring candidates in indexed source code. Use when the user asks about source-code quality, dead code, unused functions, zero callers, complexity, cyclomatic complexity,…
syncable-dev/memtrace-public
Build a phased, risk-scored refactoring plan from Memtrace complexity, dead-code, bridge, impact analysis, and Cortex decision-memory constraints. Use when the user wants to refactor source code, reduce complexity,…
Add this badge to your README
[](https://modelsatlas.com/skills/syncable-dev/memtrace-incident-investigation/)
<a href="https://modelsatlas.com/skills/syncable-dev/memtrace-incident-investigation/"><img src="https://modelsatlas.com/skills/syncable-dev/memtrace-incident-investigation/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about Memtrace Incident Investigation
What does the Memtrace Incident Investigation skill do?
Is Memtrace Incident Investigation safe to install?
What can Memtrace Incident Investigation access on my machine?
Which assistants does Memtrace Incident Investigation work with?
How current is this page?
Sources
- github.com/syncable-dev/memtrace-public/tree/main/plugins/memtra — the audited source at commit 3e7894d935d8 and every finding aboveObserved · 29 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the Memtrace Incident Investigation skill do?
- Is Memtrace Incident Investigation safe to install?
- What can Memtrace Incident Investigation access on my machine?