memory
/memory
Wyszukuje, dopisuje i porządkuje wpisy w pamięci długoterminowej za pomocą narzędzia memory, także gdy trzeba usunąć nieaktualne lub błędne notatki.
- Autor
- yc-software ↗
- Repozytorium
- qm ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 27.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Wyszukuje, dopisuje i porządkuje wpisy w pamięci długoterminowej za pomocą narzędzia memory, także gdy trzeba usunąć nieaktualne lub błędne notatki.
Oryginalny opis (EN)
Deliberately search, add to, or curate your long-term memory with the `memory` tool — beyond the automatic recall/capture every turn already does. Use when asked who someone is or what they're working on, when you learn a durable fact worth keeping now, or when your notebook holds stale or wrong entries you should clean up.
Jak działa
- Org-wide notebook (admins)
- Failure modes
Podgląd SKILL.md
---
name: memory
description: Deliberately search, add to, or curate your long-term memory with the `memory` tool — beyond the automatic recall/capture every turn already does. Use when asked who someone is or what they're working on, when you learn a durable fact worth keeping now, or when your notebook holds stale or wrong entries you should clean up.
---
# memory — search, write, and curate what you remember
Everything here goes through the typed `memory` tool. Memory is NOT a file: writing
`memory/MEMORY.md` with `files` action `write` or shell commands lands on your computer's disk and is
silently lost — the tool is the one real path.
Every turn already auto-recalls a bounded selection from your notebooks into "## What you remember" and
auto-extracts facts after you reply. This skill is for what the automatic path misses:
- **Search** (`action: "search"`) — what you remember is bigger than what auto-recall
injects. Search spans every notebook this conversation may read (personal, channel,
org); when more than one is in reach, each hit is tagged with the notebook it came
from. Matching is substring-based (all terms must match), so prefer distinctive terms
(a name, a project) over sentences.
An empty result means those terms found no match, not that nothing is recorded. Try fewer terms or alternate wording before concluding a fact is absent.
- **Read another notebook** (`action: "read", scope: "channel:…"`) — use the exact
scope ID from a search result to load that authorized notebook. `search` accepts
`scope` too, to narrow a query. Omit it to search all authorized notebooks or read
the current notebook. Access comes from this turn's sharing policy; naming a
scope never grants access. Other notebooks are read-only.
- **Write now** (`action: "add"`, `facts: [{text}, …]`) — when the user corrects you or tells you
something they'll expect you to know later, persist it immediately instead of hoping
post-turn extraction catches it. Write self-contained facts (who/what, with enough
context to be useful cold). Duplicates are dropped; `added` in the reply is the count
actually new.
- **Curate** (`action: "edit"` with `facts: [{id, text}, …]`, `action: "delete"` with
`ids`) — search or read to get each fact's `#id`, then fix facts that changed and delete
stale, duplicate, or wrong ones. A call naming any id that isn't in this conversation's
notebook changes nothing and lists the bad ids. Curation is for quality — merging
duplicates, deleting disproven facts — not for deleting things the user asked you to
remember.
The notebook you write is this conversation's own (your personal one in a DM, the
channel's in a channel). Other authorized notebooks can be searched/read, not rewritten here.
The org-admin write path uses the self-API instead, called with
`$AGENT_API_URL` and `$AGENT_API_TOKEN` (both already in your environment on every turn —
if they are unset, this instance has no self-API; say so rather than pretending).
## Org-wide notebook (admins)
When the chatting user is an org admin, the self-API additionally accepts the org-wide
notebook as a target:
```bash
curl -fsS -X POST "$AGENT_API_URL/v1/memory/facts" \
-H "x-agent-capability: $AGENT_API_TOKEN" \
-H "content-type: application/json" \
-d '{"scope":"org","facts":["..."]}'
```
(`?scope=org` on `GET /v1/memory/self`; `"scope":"org"` in the body of `PATCH /v1/memory/facts`
with `{"facts":[{"id","text"}]}` or `DELETE /v1/memory/facts` with `{"ids":[…]}` to curate.)
Those writes land in the notebook every conversation in the org recalls, so confirm the
wording with the admin before writing and keep personal facts out of it. A `403 org
memory writes require an org admin` means the user isn't one — say so rather than
retrying (`GET $AGENT_API_URL/v1/admin/whoami` answers it definitively).
## Failure modes
- "memory isn't available in this conversation" — this conversation's memory policy
forbids it; don't retry, just say memory is off here.
- On a read-only wake (a heartbeat glance), memory can be searched and read but not
written — save the fact on a normal turn instead.
- `401 unauthorized` from the self-API — your token expired mid-turn; this resolves on
the next turn.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · yc-software/qm | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| topoteretes/cognee-integrations | 100 | Apache-2.0 |
| topoteretes/cognee-integrations | 100 | Apache-2.0 |
| topoteretes/cognee-integrations | 100 | Apache-2.0 |
| thebtf/engram | 100 | MIT |
| stxrmik/antigravity-plus | 100 | MIT |
| boshu2/agentops | 100 | Apache-2.0 |
Migawka bazy z 13.11.2026 · wersja paczki 73bbda29324a (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100codex-memory-curator
Audytuje i bezpiecznie porządkuje pamięć Codex: nieaktualne twierdzenia, przecieki między repozytoriami, wrażliwe wpisy i konfigurację pamięci. - 90daftari-memory
Korzysta z vaultu Daftari jako długoterminowej pamięci i przypomina decyzje, preferencje oraz kontekst projektów. - 95memmachine
Obsługuje serwer pamięci długoterminowej MemMachine dla agentów: klientów Python i TypeScript, API pamięci, wdrożenie i narzędzia MCP. - 100memory-cleanup
Czyści nieaktualne wpisy pamięci, jak zamknięte zgłoszenia, scalone MR-y, wygasłe przestrzenie nazw i stare logi sesji. - 100memory-audit
Porządkuje katalog memory projektu: porównuje aktywne pliki z bieżącym kodem i archiwizuje lub zastępuje nieaktualne wpisy. - 100memory-status
Pokazuje panel kondycji pamięci: liczbę linii, pliki tematów, zapełnienie, nieaktualne wpisy i rekomendacje, gdy trzeba sprawdzić, jak pełna i zdrowa jest pamięć agenta.