wicked-garden-mem
Skill9 starsChanged 7 months agoMITView on GitHub
Cross-session memory + knowledge over wicked-estate. One skill, routed actions: store (a durable decision/pattern/gotcha), recall (this project's memories; all scopes on opt-in), answer (cited synthesis from the knowledge + memory stores, plus live data-source rows when a crew step may query them), review (browse coverage by kind/tier), forget (kind-guarded erase of a scope subtree), maintain (reflect + coverage pulse; estate consolidates in-store), ingest (file or directory → knowledge chunks, binary docs via vision), and capture (session-teardown sweep of decisions/patterns/gotchas).
- Installs packages
In this repository142 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- plugin-json-schemaSkill
- readme-style-guideSkill
- releaseSkill
- scaffoldSkill
- wicked-garden-agentic-agentic-patternsSkill
- wicked-garden-agentic-architectSkill
- wicked-garden-agentic-context-engineeringSkill
- wicked-garden-agentic-frameworksSkill
- wicked-garden-agentic-performance-analystSkill
- wicked-garden-agentic-review-methodologySkill
- wicked-garden-agentic-safety-reviewerSkill
- wicked-garden-agenticSkill
- wicked-garden-agentic-trust-and-safetySkill
- wicked-garden-appsSkill
- wicked-garden-archetypeSkill
- wicked-garden-build-guideSkill
- wicked-garden-classifySkill
- wicked-garden-coreSkill
- wicked-garden-data-engineerSkill
- wicked-garden-dataSkill
- wicked-garden-deliberateSkill
- wicked-garden-demoSkill
- wicked-garden-domain-coverageSkill
- wicked-garden-domain-extractorSkill
- wicked-garden-domain-modelerSkill
- wicked-garden-domainSkill
- wicked-garden-draftSkill
- wicked-garden-editor-scaffoldSkill
- wicked-garden-engineering-api-documentarianSkill
- wicked-garden-engineering-architectureSkill
- wicked-garden-engineering-backendSkill
- wicked-garden-engineering-debuggingSkill
- wicked-garden-engineering-docsSkill
- wicked-garden-engineering-frontendSkill
- wicked-garden-engineering-integrationSkill
- wicked-garden-engineering-large-scale-migrationSkill
- wicked-garden-engineering-migration-engineerSkill
- wicked-garden-engineering-patchSkill
- wicked-garden-engineeringSkill
- wicked-garden-engineering-solution-architectSkill
- wicked-garden-engineering-system-designSkill
- wicked-garden-engineering-unit-test-qualitySkill
- wicked-garden-governed-workerSkill
- wicked-garden-groundSkill
- wicked-garden-jam-brainstorm-facilitatorSkill
- wicked-garden-jam-councilSkill
- wicked-garden-jamSkill
- wicked-garden-learnSkill
- wicked-garden-mcp-scaffoldSkill
- wicked-garden-mcpSkill
- wicked-garden-mem-captureSkill
- wicked-garden-mem-ingestSkill
- wicked-garden-personaSkill
- wicked-garden-platform-auditSkill
- wicked-garden-platform-compliance-officerSkill
- wicked-garden-platform-complianceSkill
- wicked-garden-platform-errorsSkill
- wicked-garden-platform-gate-benchmark-rebaselineSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 63
If none of these is available, or Python 3 is missing, skip the script-backed step, say so, and follow the manual alternative where one is …
- Distinctive: line 207
No hook extracts memories from the transcript.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
wicked-garden:mem — memory + knowledge over wicked-estate
The engine is wicked-estate (its memory.* / knowledge.* tools, reached through the
read-only estate shim the backend script spawns — the one way on every seat); the seam
is one deterministic backend script. Per estate's DEC-R doctrine, the agent
reasons (what to store, how to chunk, what an answer means) and the engine
ranks/persists — the backend only moves JSON. Every action degrades
gracefully: when estate is unreachable the backend returns
{"ok": false, "reason": ...} instead of crashing.
wicked-garden run \
scripts/mem/estate_memory.py <action> '<json-args>'Long content: pass - as json-args and pipe the JSON via stdin.
Every call from a seat carries --readonly — a governed run's unit, a chat turn, any session
where you are the agent (when in doubt, --readonly):
wicked-garden run scripts/mem/estate_memory.py <action> '<json-args>' --readonlyA human operator at a terminal may omit it to store / ingest / forget. The backend forwards
--readonly to the estate shim (scripts/_estate_client.py), which spawns the estate binary
read-only with the store pinned from
the environment (WICKED_ESTATE_DB / WICKED_HOME / WICKED_MEMORY_DB) or --db <path>; an
unpinned store is refused (ok: false), and store / capture-batch / ingest / write /
forget are refused by the read-only engine — save a learning with propose instead
(§ Propose: one line, the backend builds the proposal), or file knowledge/policy proposals
through the wicked-garden-repo-learn skill's capture contract. recall / review / sources / health
work unchanged. Spell --readonly exactly (--read-only is a usage error). This is the one way
to the stores on every seat and in every session kind: no estate tool is registered on a seat,
nothing to connect, nothing to fall back to.
Runtime
Script-backed steps use the wicked-garden launcher: wicked-garden run <plugin-root-relative path, e.g. scripts/…> [args]. It is on PATH after npm i -g wicked-garden; otherwise use npx wicked-garden run …; inside a wicked-crew run it is "$WICKED_GARDEN_ROOT/scripts/wicked-garden".
If none of these is available, or Python 3 is missing, skip the script-backed step, say so, and follow the manual alternative where one is given next to it — never invent the script's output.
Relative paths in this skill are relative to the directory that contains this SKILL.md.
Routing
| Action | Use for | How |
store | persist one learning (decision, pattern, gotcha, discovery) | § Store |
propose | save one learning from a read-only seat (lands pending for operator approval) | § Propose |
recall | find memories ("what do we know about X") | § Recall |
answer | grounded, cited answer from the stores, and from a live data source's rows when crew lets the step query it | the wicked-garden-search skill's refs/answer.md |
review | browse what's stored (counts by kind/tier, scope digest) | § Review / Maintain |
forget | erase a scope subtree (kind-guarded) | § Forget |
maintain | reflect + coverage pulse (consolidation runs in-store) | § Review / Maintain |
ingest | file/dir → knowledge chunks (pdf/docx/pptx/xlsx/images via vision) | dispatch wicked-garden-mem-ingest |
capture | end-of-session sweep → memories | dispatch wicked-garden-mem-capture |
Scope conventions, kind/tier vocabulary, and the brain-migration layout: refs/scopes.md.
A chat seat asked by wicked-crew to label the operator's decisions reads refs/decision-report.md and ends its reply with that block.
Store
- Apply the durability test: would this help a fresh session, on a
different task, three months from now? Store a rule, why it holds, and
when it applies, in 1–3 self-contained sentences. Never store progress or
status, release versions ("shipped 2.4.1"), commit SHAs, PR/run ids, PIDs,
"today", or what the repo,
CHANGELOG or tracker already records. That test is your judgment. The
backend refuses only a body under 40 characters, a bare id / SHA / version
and first-person narration (
not a durable learning: don't store, don't work around it); it stores bodies containing ids, versions or SHAs and returnswarningsnaming them, so check those before you store. Provenance: memory is what we witnessed, were told, or decided. A claim read from code, docs or the web is knowledge: usewrite({"content","class":"concept","source"}) oringestinstead;storerefuses content that carries asource. - Pick
kind(+ tier defaults):fact→ semantic (decisions, gotchas, stable facts) ·skill→ procedural (patterns, how-tos; a convention the team must follow is a rule: propose it aspolicy:<type>, see the mem-capture worker's Step 3b) ·entity→ semantic (a person/system profile). Addabouttags for recall hooks. - Run the backend:
Scope defaults to... estate_memory.py store '{"content":"<distilled>","kind":"fact","about":["tag1","tag2"]}'project:<cwd-basename>; pass"scope"to override (see refs/scopes.md). - Confirm the returned
memory_id; onok: falsereport the degrade — do not silently drop the learning.
Propose — the one-line memory path on a seat
A seat is read-only, so store is refused there. propose is the write it still has:
wicked-garden run scripts/mem/estate_memory.py --readonly propose '<the rule, why it holds, when it applies>'
printf '%s' '<long text>' | wicked-garden run scripts/mem/estate_memory.py --readonly propose -The backend builds the whole proposal: kind_type: "memory", payload {content, tier}
(fact → semantic; pass {"content": …, "kind": "skill"} for a how-to → procedural),
and facets {repo, project} from the cwd's checkout (project = the cwd name outside one;
a run's WICKED_RUN_PROJECT wins). The § Store durability test applies and the backend
enforces the same refusals. It answers {"ok": true, "id": …, "facets": …}; the memory is
pending until an operator approves it. On ok: false, report the reason.
Recall
... estate_memory.py recall '{"query":"<topic>"}'By default recall searches the current project (project:<cwd-basename>)
and its ancestors, so root-scoped memories stay visible and other projects'
memories do not leak in. Operator memories (operator:<id>, how the user
works) are recalled in every project. Pass "scope" to recall another project the same
way. Searching everything, brain-migrated leaves
(brain:<project>/doc:<id>) included, is an explicit opt-in:
"scope_prefix": "" (or "scope_prefix": "project:<name>" for one subtree). Items return content, scope, tier,
and score; present the top hits and cite memory_id/scope when the user
needs provenance. For a synthesized, citation-bearing answer use the
answer action instead.
Steering doctrine (the governance rules, 7 steering types) lives in the
knowledge store under wiki: scopes (a historical prefix — e.g.
wiki:architecture: planes, storage doctrine, event grammar, ADR
rationale): recall it with knowledge.recall /
{"scope_prefix": "wiki:"} via answer, and recall the enforceable rules
behind it with the estate rules.recall tool through the read-only shim —
wicked-garden run scripts/_estate_client.py --readonly call '{"tool":"rules.recall","arguments":{…}}' — (faceted, severity-ordered,
each hit citing its source doc). Managing steering (import / chat / edit /
retire) is operator work — see crates/wicked-governance/STEERING.md
in wicked-core.
Review / Maintain
... estate_memory.py review '{}' # counts by kind/tier
... estate_memory.py review '{"scope":"project:x"}' # + distilled digest
... estate_memory.py maintain '{}' # reflect + coverageEstate owns the memory lifecycle in-store (decay, promotion, merge — the
consolidate engine); maintain is the user-facing pulse, not a batch job to
schedule. Report total, the kind/tier distribution, and any distilled
facts from reflect.
Forget
... estate_memory.py forget '{"scope_prefix":"brain:old-project"}'Erase is subtree-wide and permanent, so the backend enforces a kind-guard:
the prefix must contain a kind:id segment. Erasing everything requires an
explicit {"scope_prefix": "", "confirm_erase_all": true} — confirm with
the user before ever doing that. Report deleted_count.
Ingest — files and directories into the knowledge store
Dispatch the wicked-garden-mem-ingest fork worker with the source path
(and optional scope/title). It detects text vs binary, chunks text
deterministically, extracts pdf/docx/pptx/xlsx/images via LLM vision, writes
through estate knowledge.ingest (every chunk carries source provenance),
and verifies with a seeded recall. Estate's embedded method card
(skill://knowledge-ingest/SKILL.md) is the chunking doctrine.
Capture — session teardown
Dispatch the wicked-garden-mem-capture fork worker at session end ("
capture what we learned", before /clear or exit). It sweeps the conversation
for decisions, patterns, gotchas, discoveries, and preferences, classifies
each onto the estate kind/tier vocabulary, and batch-writes them via
capture-batch. A standing rule the user stated ("always…", "never…") is
filed as a policy:<type> proposal for review (reach operator, every
project, unless they named a project), not stored as a memory. How the user
works (style, preferences, standing extra steps) is an operator memory at
operator:local, recalled in every project.
Report what it stored and proposed.
No hook extracts memories from the transcript. The Stop hook used to pattern-match "decided to…" / "going to…" and filled the store with narration, so it was removed: a learning is stored because someone chose to store it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

