AI i agenci · Automatyzacja
fact-memory
/fact-memory
Zapisuje, aktualizuje i przywołuje trwałe fakty, opisując ich budowę, cykl życia i sposób pomiaru.
Dla kogo
- Autor
- vlat0101 ↗
- Repozytorium
- agent-playbook ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 05.11.2026
Ocena i bezpieczeństwo
90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Przestarzałość
Brak sygnałów. Repozytorium zmienione 05.11.2026, bez odwołań do wycofanych modeli i API.
Licencja
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Zapisuje, aktualizuje i przywołuje trwałe fakty, opisując ich budowę, cykl życia i sposób pomiaru.
Oryginalny opis (EN)
Use when storing, updating or recalling durable facts. Anatomy, lifecycle, measurement.
Jak działa
- Where a thing goes
- Anatomy
- The write sequence
- Lifecycle
- Keywords
- Entities
- Provenance
- Measurement
- Maintenance
- Done when
Sekcje z nagłówków SKILL.md, w oryginale · 115 linii, 804 słów
Podgląd SKILL.md
---
name: fact-memory
description: "Use when storing, updating or recalling durable facts. Anatomy, lifecycle, measurement."
version: 1.0.0
license: MIT
metadata:
hermes:
tags: [guide, fact]
---
# Fact memory
Facts are written as short standalone statements and loaded only when relevant, so
recall stays broad while the always-on context stays small.
## Where a thing goes
Ask in order, stop at the first yes:
1. Will it matter in a session about something unrelated? → always-on note.
2. Is it a procedure with steps and pitfalls? → a skill.
3. Is it a durable statement about a person, thing or decision? → the fact store.
4. Only true for this task, this week? → nowhere. That is session history.
Never put a credential in any of them.
## Anatomy
One sentence, one claim, standalone, about 20 words. It must make sense with no
conversation around it, because that is how it will be read.
| Bad | Why | Good |
|---|---|---|
| "Moved it to Tuesday" | No subject | "Refuse collection moved to Tuesday from 2026-04-01." |
| "Prefers the other one" | No referent | "Prefers the 14-inch laptop over the 16-inch for travel." |
| "Always check the vault" | An instruction | "Credentials are stored in the vault, not in config files." |
| A 200-word incident story | Too long to rank | Three facts: what broke, what fixed it, what was decided |
## The write sequence
1. **Search first**, using the words you would search later. A fact that already
answers it means you are about to write a duplicate.
2. **Read the similarity and conflict list the store returns on add.** It is telling
you what you are about to contradict or duplicate.
3. **Pick the lifecycle verb** — a new fact about an old subject is not automatically
an add.
4. **Write sentence, entities, keywords, origin.** A `valid_from` date only if the
message gave one. Never invent a date.
5. **Resolve any conflict it reports.** One of the two facts is now wrong, and the
store cannot know which.
## Lifecycle
| Verb | Means | Note |
|---|---|---|
| add | New subject | |
| change | It became different | Keep the old version; the history explains past decisions |
| end | No longer true, nothing replaces it | Not a delete |
| correct | It was never true | Different claim from `change`: the old value was acted on while wrong |
| revert | Undo the last change | |
| forget | Human asked | Only on explicit request |
**Never add a second fact beside a stale one.** Both come back in recall, ranked, and
the agent states whichever wins.
## Keywords
Three to eight words **not in the fact text**: synonyms, broader terms, other word
roots, other languages the human uses. Test: would you search this word to find this
fact?
"Mom's birthday is 3 May" → `birth date, anniversary, mum, cumpleaños, 生日`, not
`birthday, May`.
## Entities
Pass the entity whenever the name is one word or ambiguous — a first name, a pet, a
hostname, a product with a common name. Then:
- **alias** when one thing has two names, before facts split down the middle.
- **split** when one entity turns out to be two things.
- **delete the entity, keep the facts** when the "name" was a phrase or a command.
- **provisional** entities are guesses from text that nobody confirmed. Review them.
## Provenance
| Origin | Consequence |
|---|---|
| said | True until corrected |
| confirmed | A conclusion the human agreed with |
| inferred | Your conclusion. Marked as such; do not present it as their view |
An inferred fact never becomes a said fact by repetition.
## Measurement
| Metric | Act when |
|---|---|
| Always-on budget utilisation | Above 90%: consolidate before an add is rejected |
| Facts with no keywords | Any: invisible to search |
| Provisional entities | More than a handful: confirm or delete |
| Open contradictions | Any: one of the two is wrong now |
| Stale-but-open facts | Retire or re-confirm |
| Re-explanation rate (per week) | Each miss is a keyword problem, not a bug |
A fact that keeps surfacing in irrelevant sessions is noise: narrow its keywords or
merge it. Do not reinforce it.
## Maintenance
Nightly: extract candidates (durable only), merge duplicates, end facts whose subject
is gone, sweep requested deletions. Weekly: review list, entities, the metrics.
Monthly: read ten random facts and ask "is this still true".
Consolidation may merge. It may not delete the record that an earlier version
existed.
## Done when
- A superseded fact was changed, not duplicated.
- A wrong fact was corrected, not overwritten.
- A fact is found by asking in different words.
- Asking about something absent returns "nothing stored", not an invention.
Wersje
W bazie nie ma innych skilli o nazwie fact-memory.
Migawka bazy z 13.11.2026 · wersja paczki 8d52de745568 (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
- 100memory
Przechowuje i przywołuje pamięć długoterminową: zapisuje fakty poznane w rozmowach oraz wiedzę o projektach i preferencjach. - 100brain-memory
Przechowuje trwałą pamięć między rozmowami w bazie Brain: preferencje, decyzje, fakty o projektach i ludziach oraz ich odzyskiwanie. - 100memory-extraction
Na koniec sesji zapisuje trwałe fakty z bieżącej sesji do .claude/memory/, w głównym agencie na podstawie transkryptu w kontekście i istniejącej pamięci, po sygnale z hooka Stop. - 100memory
Zapisuje trwałe fakty, decyzje i preferencje w pamięci długoterminowej memini oraz przywołuje odpowiedni kontekst przed rozpoczęciem zadania. - 96project-memory
Zapisuje trwałe fakty o projekcie, takie jak decyzje i pułapki, w pliku pamięci, by kolejne sesje nie odkrywały ich od nowa. - 95ai-memory-durable-pages
Zapisuje, aktualizuje, adnotuje lub usuwa trwałe strony wiki w ai-memory, gdy trzeba zachować wiedzę projektu.