Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →syncable-dev/memtrace-decision-memory
Use Cortex decision memory through the normal Memtrace MCP tools. Trigger for free-text questions about what was decided, chosen, rejected, banned, or established as a convention; for why a symbol exists or which contracts constrain it; for whether a known decision held, drifted, or was violated; and for the implementation arc behind a decision. Use before non-trivial edits, refactors, deletions, or re-picking a library, pattern, architecture, or subsystem behavior. Routes internally across reca
Passed 3 of 9 test cases with the skill, and 2 of 9 without it.
and 7 more in the full report
6 fixed2 passed either way12 still failing2 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.
Can I invoke why_is_this_here directly using the name 'AuthenticationService.validateToken'?
| Checked | Without skill | With skill |
|---|---|---|
| Clarifies that why_is_this_here requires a numeric symbol_id rather than a string name | Missed | Passed |
| Recommends starting with recall_decision to find the symbol or decision context | Missed | Passed |
The instructions your model reads when the skill loads.
BEFORE you assume why code exists, contradict a convention, re-pick a settled
choice, or delete code that "looks unused/weird" → CHECK DECISION MEMORY.
recall_decision(free-text) → what did we decide / ban about X?
why_is_this_here(symbol_id) → what decision put this here?
verify_intent(decision_id) → did that decision still hold, or was it violated?
get_arc(decision_id) → what episodes implemented it?
governing_contracts(sym_id) → what constraints bind this symbol?
This is the rationale layer of the codebase. memtrace-first answers what the
code is and how it's wired (symbols, calls, git, blast radius). Decision memory
answers why it is the way it is, what we already decided, and whether that decision
still holds — extracted from real coding conversations and decisions, not the AST.
The graph can tell you a function exists and who calls it. Only decision memory can tell you that three weeks ago you banned the approach you're about to reintroduce.
Full parameter spec for every Memtrace tool: references/mcp-parameters.md (bundled at the memtrace-skills plugin root).
These five tools are deterministic, zero-LLM. Every call returns a labeled Verdict / Evidence / CannotProve answer carrying its FactStatus and proof path. No tool ever fabricates an answer.
| Answer | What it means | What you must NOT do |
|---|---|---|
| Verdict + Evidence (Observed / DeterministicallyDerived / StatisticallyRanked) | A recorded decision/provenance backs this | — |
| CannotProve | No recorded decision governs this | Do not read it as "safe / approved / unconstrained." It means unknown, not permitted. Fall back to memtrace-first + asking the user. |
CannotProve is a real, trustworthy answer ("memory has nothing on this"), not a
failure and not a green light. Never invent a rationale to fill the gap.
test cases passed, vs 2 / 9 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.