agentleFS
alexeybanalexeyban/EKOS/.claude/skills/memory/SKILL.md

memory

Skill26 starsChanged 9 days agoMITView on GitHub

Routing note for memory in this estate. Use ONLY when the user types /memory explicitly. This skill no longer stores or retrieves anything itself — it names which system owns each kind of memory. Do NOT use it to record or recall anything: for anchored per-codebase notes use the session-memory skill, for querying compiled knowledge use the ekos-knowledge skill.

99 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • naman10parikhSkill

    ecosystem-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

  • naman10parikhSkill

    fractal-delegation

    Also in 5 projects that use this

  • Maliot100XSkill

    send-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

  • jh941213Skill

    docs-ci

    문서 CI(링크·OpenAPI lint·breaking 게이트·mermaid 검증)나 문서 드리프트 감지(docs.yaml 신선도 검사)를 설치하거나 돌릴 때 사용. 문서 내용 작성은 docs-architecture·docs-interfaces·docs-manuals.

    Also in 3 projects that use this

  • jh941213Skill

    docs-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

The file

Files
SKILL.md

Memory — routing only

This skill used to keep estate-wide notes as Markdown files indexed through the EKOS ledger. It was retired on 2026-09-21. Its store had not been written to since 2026-07-17, and it had four defects that made it actively misleading — most importantly it resolved its own note directory to the wrong path, so a session would report "no memory notes exist" while notes sat one directory up.

Who owns what

You want to…Use
record or recall a note about this codebase, anchored to a real object and flagged when that object changesthe session-memory skill (ekos_session_*)
ask what exists across the estate — tables, services, files, contributors — from compiled knowledgethe ekos-knowledge skill (ekos_search, ekos_ekl, ekos_state, …)
carry narrative, preferences and working agreements across sessionsClaude Code's own memory (~/.claude/projects/<project>/memory/, indexed by MEMORY.md)

Those three do not overlap: the first is per-codebase and object-anchored, the second is read-only over compiled facts, the third is free-text and cross-session.

The old notes

Nine legacy notes remain on disk at /home/legion/PycharmProjects/memory/, untouched. Read them directly if you need them; nothing indexes them any more. They follow a <scope>--<type>--<keywords>.md convention.

Why the retrieval instructions are gone

They told the agent to run ekos_search "..." as a shell command. There is no such binary and no such CLI subcommand — ekos_search is an MCP tool (mcp__ekos__ekos_search). Use ekos-knowledge, which gets this right.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.