Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →syncable-dev/memtrace-first
Route code discovery, debugging, flow tracing, how-code-works questions, and pre-edit rationale checks in indexed source-code repos to Memtrace graph plus Cortex decision tools. Use first before searching/reading code, and before editing, refactoring, deleting, or re-picking an approach that may have a recorded decision, ban, convention, or contract.
Passed 10 of 15 test cases with the skill, and 2 of 15 without it.
and 10 more in the full report
13 fixed2 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
You need to retrieve change history for `order_service.go` over the last 90 days using get_evolution. What parameter name is used to specify this historical lookback window?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies from as the parameter name for specifying the lookback window. | Missed | Passed |
The instructions your model reads when the skill loads.
IF THE REPO IS INDEXED IN MEMTRACE → USE MEMTRACE TOOLS FIRST.
After a search hit, route to GRAPH tools (get_symbol_context, get_impact,
analyze_relationships) — that's what Memtrace uniquely provides. Read source
ONLY when you're about to edit or quote, and read only the bounded span
returned by Memtrace (start_line .. end_line + small context). Do not
Grep/Glob/Find to "locate" anything already in the graph, and do not read
the whole file when Memtrace has given you exact lines.
BEFORE you edit/refactor/delete existing code or choose/re-pick a pattern,
call Cortex decision memory: recall_decision for the symbol/subsystem/approach,
and use provenance/contracts when a symbol_id is available. Use Memtrace's graph
tools for structure and blast radius; use Cortex for rationale, bans, and
contracts.
Memtrace is the memory layer of the codebase, not a search engine that returns code. It has the full knowledge graph — every symbol, call, import, community, process, and API — with a time dimension. The point is to navigate that graph: who calls this, what's the blast radius, when did this change, what community is it part of. File tools are blind to all of that.
No exceptions for what's in the graph.
Do not print usage receipts in normal answers. Memtrace records tool usage, graph facts, file references, and estimated context avoided internally. Users can inspect that in the local UI's Value panel.
Memtrace's hybrid search = BM25 over symbol metadata (name, signature, file_path, kind) + semantic vector search over embedded code bodies (first ~1500 chars of every Function / Method / Class / Struct / Interface body), fused via Reciprocal Rank Fusion.
The semantic side means string literals, error messages, magic constants, log strings, and any text inside an indexed symbol's body are findable through find_code. The body got embedded; the embedding catches it. You do NOT need Grep to hunt for STRIPE_KEY_FOO_BAR if it lives inside a function in your indexed codebase.
If Memtrace returns 0 results, or repository stats look incomplete, do not infer that a source subdirectory is outside the index. Diagnose through Memtrace:
test cases passed, vs 2 / 15 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.