Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →syncable-dev/memtrace-fleet-publish-intent
Declare a structural intent BEFORE editing in a fleet — what symbols you'll touch and why — so other agents on your branch coordinate around you.
Passed 5 of 12 test cases with the skill, and 2 of 12 without it.
and 8 more in the full report
8 fixed3 passed either way13 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
When publishing an intent for `graph::calculate_weights` in `routing-service` on branch `session/route-opt`, which returned field provides the graph blast radius preview?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies impact_preview as the output field containing graph blast radius. | Missed | Passed |
The instructions your model reads when the skill loads.
fleet_publish_intent is step 1 of the fleet protocol: announce what you're about
to touch so other agents on the same (repo, branch) coordinate around you.
It's a typed, ~20-token declaration — not prose.
fleet_publish_intent({
repo_id: "myrepo",
branch: "session/auth-revamp", // your fleet's session branch
agent_id:"agent-a",
touched: ["auth::verify_token"], // qualified symbol identities
intent: {"refactor": {"pattern": "change_signature"}},
assignment: "widen verify_token signature for pagination" // the alignment anchor
})
Full parameter spec for every Memtrace tool: references/mcp-parameters.md (bundled at the memtrace-skills plugin root).
{
"impact_preview": "…graph blast radius of the touched symbols…",
"active_conflicts": [],
"coordination": { "would_escalate": false, "suggested_partition": null }
}
impact_preview — the real graph blast radius of the touched symbols.active_conflicts — overlapping live intents on your branch (none from other
branches; coordination is branch-scoped).coordination — a shift-left hint: would_escalate, a suggested_partition
(who should own a contested symbol), and advice to realign before you edit.{"refactor":{"pattern":"rename_symbol"|"change_signature"|"move_symbol"|"extract_function"|…}}test cases passed, vs 2 / 12 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.