Install any skill in seconds. Free to start, no credit card required.
Get Started Free →syncable-dev/memtrace-impact
Compute the blast radius of modifying a symbol through transitive graph impact.
Passed 16 of 19 test cases with the skill, and 7 of 19 without it.
and 9 more in the full report
11 fixed8 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to analyze impact for symbol `processOrder` in `ecommerce-engine`. I know its internal ID in the database is `sym_99812a`. Which JSON parameter field name should I populate with the string 'processOrder' when calling the impact analysis tool: target, symbol_id, or name?
| Checked | Without skill | With skill |
|---|---|---|
| Uses target as the parameter key for the symbol name processOrder | Missed | Passed |
The instructions your model reads when the skill loads.
Compute the blast radius of changing a specific symbol. Traces upstream (what depends on this) and downstream (what this depends on) through the knowledge graph to quantify risk before making modifications.
| Tool | Purpose |
|---|---|
get_impact | Blast radius from a symbol name (target) |
detect_changes | Scope symbols affected by a diff/patch |
Parameter types: MCP parameters are strictly typed. Numbers (
depth,limit, etc.) must be JSON numbers — not strings.
get_impact| Parameter | Required | Default | Notes |
|---|---|---|---|
repo_id | yes | — | |
target | yes | — | Symbol name (e.g. "validateToken") — not symbol_id |
direction | no | "both" | "upstream" | "downstream" | "both" |
depth | no | 5 | BFS depth (max 15) |
as_of | no | now | ISO-8601 for time-travel |
{ "repo_id": "memdb", "target": "validateToken", "direction": "both", "depth": 5 }
Full parameter spec for every Memtrace tool: references/mcp-parameters.md (bundled at the memtrace-skills plugin root).
If you don't know the exact name:
find_symbol(name="...") for exact identifiersfind_code(query="...") for natural-language queriesUse the returned name (and optional file_path hint) — graph tools resolve by name, not internal IDs.
test cases passed, vs 7 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.