Agent skill · Audited from source
Memtrace Evolution
skill · syncable-dev/memtrace-publicNOASSERTION licenceAudited 28 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: Trace source-code change history from Memtrace's symbol-level temporal memory. Use when the user asks about change history, recent modifications, what changed since a date, symbol timeline, evolution, unexpected…
Cite
Cite this page
ModelsAtlas. “Memtrace Evolution (syncable-dev/memtrace-public)”. Retrieved 28 Oct 2026. https://modelsatlas.com/skills/syncable-dev/memtrace-evolution
Trust audit
Audit 0.4.1 · source read 28 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 · 28 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-evolutionThe exact folder we audited
- LicenceNOASSERTIONAs the repository states it
- Commit pinned for this verdict3e7894d935d8A new audit runs when the source changes
- Repository statusNot archivedPushed today
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Trace source-code change history from Memtrace's symbol-level temporal memory. Use when the user asks about change history, recent modifications, what changed since a date, symbol timeline, evolution, unexpected…
---
name: memtrace-evolution
description: "Trace source-code change history from Memtrace's symbol-level temporal memory. Use when the user asks about change history, recent modifications, what changed since a date, symbol timeline, evolution, unexpected changes, or incident timelines. Do not use git log, git diff, Grep, or manual file search to reconstruct history. Do NOT use for current-state architecture overviews (use memtrace-codebase-exploration) or for replaying one commit/save's graph diff (use memtrace-episode-replay)."
---
## Overview
Temporal analysis for "what changed in this repo between two points in time?" Works on both git commits and uncommitted working-tree saves.
## Required parameters — read before calling
`get_evolution` **always** requires `repo_id` and `from`. There is no `days` parameter.
| Parameter | Required | Type | Example |
|---|---|---|---|
| `repo_id` | yes | string | `"memdb"` |
| `from` | yes | string | `"90d ago"`, `"2026-04-01T00:00:00Z"`, `"yesterday"` |
| `to` | no | string | defaults to now; set to incident time when investigating |
| `mode` | no | string | `"recent"` (default), `"compound"`, `"summary"`, `"overview"` |
| `target` | no | string | symbol name or file path substring to scope results |
| `branch` | no | string | branch filter |
> **Parameter types:** MCP parameters are strictly typed. Numbers (`limit`, `cursor`, etc.) must be JSON numbers — not strings. Use `limit: 100`, never `limit: "100"`.
### Time-window parameters — do not confuse these tools
| Tool | Time param | Example | Notes |
|---|---|---|---|
| `get_evolution` | **`from`** (required) | `"90d ago"` | optional `to`; **never** pass `days` |
| `get_changes_since` | **`since`** (required) | `"2026-04-13T10:43:00Z"` | optional `until` |
| `replay_history` | **`days`** (optional) | `90` | re-walks git history — different tool entirely |
Common failure: `MCP error -32602: missing field 'from'` — you omitted `from` or passed `days` instead.
```json
// CORRECT — 90-day overview
{ "repo_id": "memdb", "from": "90d ago", "mode": "overview" }
// WRONG — days is not a get_evolution parameter
{ "repo_id": "memdb", "days": 90, "mode": "overview" }
```
## Query modes — only these four exist
| Mode | What you get | Best for |
|---|---|---|
| `recent` | Per-episode list with nodes/edges added/removed; paginate with `limit` + `cursor` | Incident timelines, walking commit-by-commit |
| `compound` | Totals plus `top_changed_files` and `top_touched_symbols` | "What changed?" when you need hotspots |
| `summary` | Totals plus `first_episode` / `last_episode` metadata | Cheapest window check |
| `overview` | Alias for `summary` | Same as `summary` |
Modes **`impact`**, **`novel`**, and **`directional`** are **not implemented** — calling them returns `unknown mode`.
### `recent` mode filters (ignored by `compound` / `summary`)
| Param | Purpose |
|---|---|
| `file_path` | substring match against episode `touched_files` |
| `kind` | `"git_commit"` or `"working_tree"` |
| `limit` | page size (default 100 episodes) |
| `cursor` | pagination offset; follow `next_cursor` in response |
Full parameter spec for every Memtrace tool: `references/mcp-parameters.md` (bundled at the memtrace-skills plugin root).
## Steps
### 1. Get `repo_id`
```
list_indexed_repositories()
```
### 2. Choose the time window
- `from` — start (required). Relative strings work: `"7d ago"`, `"24 hours ago"`.
- `to` — end (optional, defaults to now). Set to the incident timestamp when investigating regressions.
If resuming a session and you have a stored timestamp from last time, prefer `get_changes_since(since=...)` — see `memtrace-session-continuity`.
### 3. Choose the mode
```
User wants...
├── per-commit / per-save changelog → recent
├── top changed files + symbols → compound
├── quick totals only → summary or overview
└── one symbol's full history → get_timeline (not get_evolution)
```
### 4. Execute
```json
// General "what changed lately?"
{ "repo_id": "memdb", "from": "30d ago", "mode": "compound" }
// Changes in one file last week
{ "repo_id": "memdb", "from": "7d ago", "mode": "recent", "file_path": "auth.ts", "limit": 50 }
// Incident: 24h before failure until failure time
{ "repo_id": "memdb", "from": "2026-04-16T13:00:00Z", "to": "2026-04-17T13:00:00Z", "mode": "recent" }
```
### 5. Interpret results
**`recent` mode** — each entry in `episodes[]`:
- `episode` — metadata (`source_type`, `reference_time`, `touched_files`, ...)
- `nodes_added`, `nodes_removed`, `edges_added`, `edges_removed`
**`compound` mode:**
- `totals` — aggregate counts
- `top_changed_files` — files with most activity
- `top_touched_symbols` — symbols with most activity
**`summary` / `overview` mode:**
- `totals` — episode and node/edge counts
- `first_episode`, `last_episode` — window boundaries
### 6. Drill deeper
| Need | Tool |
|---|---|
| Full history of one symbol | `get_timeline(repo_id, scope_path, file_path)` |
| Blast radius of a suspect symbol | `get_impact(repo_id, target)` |
| What a diff would affect | `detect_changes(repo_id, diff=...)` |
| Behavioral coupling | `get_cochange_context(repo_id, target=<symbol>)` |
| Sub-commit tried-and-reverted history | `get_episode_replay` |
## Output
Sample `compound` payload (per-mode field lists: step 5 above):
```json
{
"totals": { "episodes": 42, "nodes_added": 310, "nodes_removed": 95,
"edges_added": 541, "edges_removed": 120 },
"top_changed_files": [ /* files ranked by activity */ ],
"top_touched_symbols": [ /* symbols ranked by activity */ ]
}
```
`recent` returns `episodes[]` + `totals` + `page.next_cursor`; `summary`/`overview` return `totals` + `first_episode`/`last_episode`.
## Common mistakes
| Mistake | Reality |
|---|---|
| Passing `days: 90` | Use `from: "90d ago"` — `days` is only on `replay_history` |
| Omitting `from` | Required — call fails with `-32602` before any query runs |
| UsinExcerpt, 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-evolution/)
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-evolution/)
<a href="https://modelsatlas.com/skills/syncable-dev/memtrace-evolution/"><img src="https://modelsatlas.com/skills/syncable-dev/memtrace-evolution/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about Memtrace Evolution
What does the Memtrace Evolution skill do?
Is Memtrace Evolution safe to install?
What can Memtrace Evolution access on my machine?
What do I need installed to use Memtrace Evolution?
Which assistants does Memtrace Evolution 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 · 28 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 Evolution skill do?
- Is Memtrace Evolution safe to install?
- What can Memtrace Evolution access on my machine?