Agent skill · Audited from source
Memtrace Index
skill · syncable-dev/memtrace-publicNOASSERTION licenceAudited 30 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: 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…
Cite
Cite this page
ModelsAtlas. “Memtrace Index (syncable-dev/memtrace-public)”. Retrieved 30 Oct 2026. https://modelsatlas.com/skills/syncable-dev/memtrace-index
Trust audit
Audit 0.4.1 · source read 30 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 · 30 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-indexThe 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: 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…
---
name: memtrace-index
description: "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 exploration needs an index, or when searches return 0/partial results for source paths under an indexed root. Use this before Grep, Glob, rg, find, or manual code search whenever the repo can be indexed. For ongoing watch mode / live re-indexing after the initial index, use memtrace-continuous-memory."
---
## Overview
Index a local codebase into the persistent code knowledge graph. This is always the first step — it parses every source file, resolves cross-file relationships, detects API endpoints/calls, runs community detection and process tracing, and embeds all symbols for semantic search.
## Quick Reference
| Parameter | Purpose |
|-----------|---------|
| `path` | Absolute path to the directory to index |
| `incremental` | Only re-parse changed files (use for subsequent runs) |
| `clear_existing` | Wipe and rebuild from scratch |
> **Parameter types:** MCP parameters are strictly typed. Numbers (`limit`, `depth`, `min_size`, `last_n`, etc.) must be JSON numbers — not strings. Use `limit: 20`, never `limit: "20"`. Passing a string yields `MCP error -32602: invalid type: string, expected usize`.
Full parameter spec for every Memtrace tool: `references/mcp-parameters.md` (bundled at the memtrace-skills plugin root).
## Steps
### 1. Check if already indexed
Use the `list_indexed_repositories` MCP tool first. If the repo is already indexed and recent, skip to step 4.
**Success criteria:** You have a list of repo_ids and their last-indexed timestamps.
If a repo is present but searches miss a source subdirectory under that repo
root (for example `ui/`, `memtrace-ui/`, `web/`, `frontend/`, or `src/`), treat
that as a stale/partial index. Do not use grep as a workaround. Run incremental
indexing on the repo root, then retry the Memtrace query.
### 2. Index the directory
Use the `index_directory` MCP tool:
- Set `path` to the project root (absolute path)
- Set `incremental: true` if re-indexing after changes
- Set `clear_existing: true` only if a full rebuild is needed
If the selected path is just a folder containing multiple independent git repos,
do not index that parent folder unless the user explicitly wants a shared
workspace. For separate repos, index each repo root separately. For intentional
sharing, ask the user to bless the parent explicitly with
`memtrace start --bless-workspace` first, then verify the boundary with
`memtrace workspace status <path>`.
**Success criteria:** You receive a `job_id` immediately.
### 3. Poll for completion
Use `check_job_status` with the `job_id` every 2–3 seconds. **The loop must never run unbounded** — hard cap at ~100 polls (~5 minutes). On hitting the cap: stop polling, report the `job_id` and last observed status to the user, and tell them the job keeps running server-side — they (or you, later) can resume with `check_job_status` on that `job_id` or find it via `list_jobs`.
Pipeline stages in order: **scan → parse → resolve → communities → processes → persist → embeddings → api_detect → done**
Wait until `status = "completed"`. If `status = "failed"`, report the error message to the user.
### 4. Report to user
After indexing completes, call `list_indexed_repositories` to confirm the repo appears with correct node/edge counts. Report: repo_id, languages detected, total symbols, total relationships.
**Save the `repo_id`** — most other memtrace tools require it.
## Error Handling
| Error | Action |
|-------|--------|
| Path does not exist | Ask user to verify the absolute path |
| Job status "failed" | Report the error message; suggest `clear_existing: true` for a fresh rebuild |
| Timeout (job running > 5 min) | Large repos are normal, but respect the poll cap: stop, report `job_id` + last status, resume later via `check_job_status` / `list_jobs`. For monorepos, index subdirectories separately |
| Already indexed | Use `incremental: true` to update, or skip indexing entirely |
## Output
`index_directory` returns a job handle immediately; `check_job_status` tracks it to a terminal state:
```json
{ "job_id": "6f9a2c1e-...-uuid" }
{ "status": "completed" }
```
While running, the job advances through the pipeline stages listed in step 3; `status = "failed"` carries an error message. The final user-facing report (confirmed via `list_indexed_repositories`) covers: `repo_id`, languages detected, total symbols, total relationships (node/edge counts).Excerpt, first 4,647 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
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
3e7894d935d8
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
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,…
syncable-dev/memtrace-public
Review GitHub pull requests with Memtrace's local graph-backed review engine. Use when the user asks to review a GitHub pull request, run Memtrace code review, post Memtrace review comments, create a PR with a review…
Questions about Memtrace Index
What does the Memtrace Index skill do?
Is Memtrace Index safe to install?
What can Memtrace Index access on my machine?
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 · 30 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 Index skill do?
- Is Memtrace Index safe to install?
- What can Memtrace Index access on my machine?