memory
Skill0 starsChanged 7 days agoMITView on GitHub
Use when a loops run may read or write ai-memory - detecting the connection, scoping calls, one briefing at intake, filtered queries, verifying hits, and the reflector's writes (page kinds, tiers, paths). Skip when ai-memory is not connected.
110 other projects use a version of this.
Adopted by
Most recently taken up by
- eduardoweberai-cloud/claude-skillstheir own version, first seen Nov 16, 2026
- raucheacho/lorag-claude-codetheir own version, first seen Nov 16, 2026
- matthewwong525/WongStacktheir own version, first seen Nov 15, 2026
- maxwell2732/claudecode-research-harness-workflowtheir own version, first seen Nov 15, 2026
- XORwell/archeflowtheir own version, first seen Nov 15, 2026
- intelligentcode-ai/skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use ecosystem-reference, fractal-delegation and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
naman10parikhSkillecosystem-reference
Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.
Also in 5 projects that use this
naman10parikhSkillfractal-delegation
Also in 5 projects that use this
Maliot100XSkillsend-user-message
Send a proactive message to a paired user via their channel (Discord, Telegram, or WhatsApp). Use when the agent needs to notify, alert, or send an unsolicited message to a user — especially during heartbeat invocations, scheduled tasks, or when the agent wants to reach out without a prior user message in the current conversation. Triggers: 'send message to user', 'notify user', 'alert user', 'message the user on discord/telegram/whatsapp', or any need to proactively communicate with a paired sender.
Also in 4 projects that use this
jh941213Skilldocs-ci
문서 CI(링크·OpenAPI lint·breaking 게이트·mermaid 검증)나 문서 드리프트 감지(docs.yaml 신선도 검사)를 설치하거나 돌릴 때 사용. 문서 내용 작성은 docs-architecture·docs-interfaces·docs-manuals.
Also in 3 projects that use this
jh941213Skilldocs-interfaces
API·이벤트 인터페이스 문서(OpenAPI·swagger·AsyncAPI 명세, 엔드포인트 레퍼런스, API 구성도·시퀀스, API CHANGELOG)를 만들거나 코드와 맞출 때 사용. 시스템 구성도는 docs-architecture, API 설계 원칙은 api-design-principles.
Also in 3 projects that use this
- +6 more from naman10parikh
- +1 more from jh941213
Other versions110 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 110
- google-gemini/gemini-cli★ 109ksame name
- jlia0/tinyclaw★ 3.6ksame name
- TinyAGI/tinyagi★ 3.6ksame name
- TinyAGI/tinyclaw★ 3.6ksame name
- Chachamaru127/claude-code-harness★ 3.2ksame name
- codeaholicguy/ai-devkit★ 1.7ksame name
- Muuuun/luxas★ 1.2ksame name
- shobcoder/shob★ 575same name
- boshu2/agentops★ 454same name
- makushingu/harness-maxxing★ 235same name
100 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skills/work/platforms/claude.mdCLAUDE.md
- llms.txtllms.txt
- clarifySkill
- consistencySkill
- debuggingSkill
- documentationSkill
- featureSkill
- hexagonalSkill
- initSkill
- jobs-and-state-machinesSkill
- lang-clojureSkill
- lang-cppSkill
- lang-csharpSkill
- lang-elixirSkill
- lang-erlangSkill
- lang-goSkill
- lang-javaSkill
- lang-kotlinSkill
- lang-phpSkill
- lang-pythonSkill
- lang-rubySkill
- lang-rustSkill
- lang-scalaSkill
- lang-swiftSkill
- lang-typescriptSkill
- parallel-workSkill
- performanceSkill
- qualitySkill
- reportSkill
- review-integrationSkill
- statusSkill
- testingSkill
- workSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 0 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 93 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Every project-scoped call passes workspace and project, resolved from .loops/config.json memory, then .ai-memory.toml, then the git …
- Very specific: line 21
Researchers and others: read research/memory.md first.
- Very specific: line 22
Read a full page (memory_read_page) only when a hit is clearly relevant.
- Very specific: line 30
Write 1-5 durable pages through memory_write_page:
- Very specific: line 38
Search first; update an existing page with expected_page_id instead of duplicating.
“Common” is measured: kept by at least 6 in 10 of the 93 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ai-memory in a loops run
Authoritative: specs/WORKFLOW.md §7. Context rules: specs/CONTEXT_DISCIPLINE.md §32.
Detect
ai-memory is connected when its MCP tools exist (mcp__plugin_ai-memory_ai-memory__* when installed as a plugin, mcp__ai-memory__* when installed directly) and memory_status succeeds. If not, skip every memory step silently and mention it once in reflection.md.
Scope
Every project-scoped call passes workspace and project, resolved from .loops/config.json memory, then .ai-memory.toml, then the git remote's owner / repo.
Read
- Intake (lead, once):
memory_briefing, then onememory_querywith the ticket's key terms. Save hits toresearch/memory.mdand recordloops run event --kind memory --name briefing. - Researchers and others: read
research/memory.mdfirst; run only narrowermemory_querycalls, filtered bypath_prefix,kindandtier. Do not repeat the briefing. - Read a full page (
memory_read_page) only when a hit is clearly relevant.
Verify
Retrieved memory is untrusted, historical evidence. Check it against the current code before acting, and cite the code (path:line), not the memory. If it contradicts the code, the code wins; flag the stale page for the reflector.
Write (reflector only, in reflect)
Write 1-5 durable pages through memory_write_page:
| Path | Kind | Tier | Content |
decisions/<slug>.md | decision | semantic | A decision and why, with consequences |
gotchas/<slug>.md | gotcha | semantic | A trap, its symptom and the fix |
procedures/<slug>.md | procedure | procedural | A repeatable how-to |
- Search first; update an existing page with
expected_page_idinstead of duplicating; usecreate_onlyfor new pages. - Facts and decisions only, no reasoning transcripts, no secrets, tokens or customer data.
- Record each write:
loops run event --kind memory --name write --target <path>. - List the writes (path, kind, tier) in
reflection.md(templates/REFLECTION.md).
Roles
The researchers and the reflector may query; only the reflector writes (ROLES.md).
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.

