Use when the user explicitly asks to clean, compact, prune, trim, deduplicate, optimize, or reduce Wingman memory, or asks to resolve stale or conflicting memory rules.
NewMaintained
Automatic
◆Knowledge Management pack
Last verified 9/1/2026
What it changes
3 of 22 test cases passed with the skill.
Pass-rate lift
—
Tokens
+104%
Agent turns
0%
Response time
+16%
Model gemini-3.6-flashMeasured 9/1/2026v13 of 22 cases passed with skill · 5 comparable
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 5 comparable cases; this report requires 8.
What's inside
The instructions your model reads when the skill loads.
SKILL.md140 lines2 filesincludes scripts
Wingman Memory Clean
Clean Wingman memory only when the user explicitly asks. Preserve the ownership model while reducing default-read noise and conflicts.
Ownership Model
brief.md / domains/ = current projection, current binding truth bodies
history/events/ = event log, historical event bodies
history indexes = projection indexes for historical lookup
context.md = hot cache, active work state and short pointers
Cleanups should move memory toward one owning body per durable item:
current rule body lives in brief.md or domains/;
historical event body lives in history/events/;
historical lookup entry lives in projection indexes;
hot state or short pointer lives in context.md.
Repository Gate
Check .wingman/memory/.
Check .wingman/memory/brief.md and .wingman/memory/context.md.
If core files are missing, stop and report repository memory state.
Read brief.md and context.md first.
Read domain or history files only when the requested cleanup scope points to them.
Never scan all memory files by default.
Scope Selection
Use the smallest scope that matches the request:
Scope
Read
Use When
context
context.md, relevant current truth/history if linked
Context contains stale hot state, verbose old logs, or duplicate bodies.
current-truth
brief.md, relevant domains
Current rules are duplicated, stale, conflicting, missing identity, or missing relations.
history-index
relevant projections
History projections are bloated, missing useful routing, or copying event bodies.
history-event
named event bodies only
User explicitly asks to inspect or edit specific history events.