Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →syncable-dev/memtrace-index
Index a source-code repo into the Memtrace knowledge graph and poll the job to completion.
Passed 8 of 13 test cases with the skill, and 4 of 13 without it.
and 9 more in the full report
8 fixed5 passed either way8 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
How frequently should `check_job_status` be called when waiting for a Memtrace indexing job handle, and what is the maximum poll iteration count?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies polling job status every 2 to 3 seconds. | Missed | Passed |
| Enforces a hard cap of approximately 100 polls. | Passed | Passed |
The instructions your model reads when the skill loads.
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.
| 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. Uselimit: 20, neverlimit: "20". Passing a string yieldsMCP 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).
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.
Use the index_directory MCP tool:
path to the project root (absolute path)incremental: true if re-indexing after changesclear_existing: true only if a full rebuild is neededIf 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
test cases passed, vs 4 / 13 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.