remembering
/remembering
Obsługuje zapamiętywanie i zapominanie: zapis trafia do kolejki, a zapomniana informacja jest archiwizowana, nie kasowana.
- Autor
- taylorsatula ↗
- Repozytorium
- mira-OSS ↗
- Licencja
- AGPL-3.0
- Ostatnia zmiana repozytorium
- 21.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 21.10.2026, bez odwołań do wycofanych modeli i API.
AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.
Co robi i kiedy
Obsługuje zapamiętywanie i zapominanie: zapis trafia do kolejki, a zapomniana informacja jest archiwizowana, nie kasowana.
Wyzwalacze z opisu
Oryginalny opis (EN)
Remembering: directed memory operations, done honestly. Use when the user asks you to remember, save, or keep something; to forget or remove something; says you remembered wrong and corrects the store; or asks why you do not remember something. Covers what 'saved' means (queued durably, committed when the conversation stretch closes), that forgetting is archiving and never deletion, how to fix a wrong memory without rewriting history, and why recall misses are surfacing, not loss. Questions about how your memory works belong to the self-knowledge skill instead.
Jak działa
- Creating: "remember this"
- Forgetting: "forget that"
- Correcting: "you remembered that wrong"
- Recall misses: "you don't remember X?"
Podgląd SKILL.md
--- name: remembering description: Remembering: directed memory operations, done honestly. Use when the user asks you to remember, save, or keep something; to forget or remove something; says you remembered wrong and corrects the store; or asks why you do not remember something. Covers what 'saved' means (queued durably, committed when the conversation stretch closes), that forgetting is archiving and never deletion, how to fix a wrong memory without rewriting history, and why recall misses are surfacing, not loss. Questions about how your memory works belong to the self-knowledge skill instead. --- # Remembering The user is not asking how your memory works; the self-knowledge skill answers that. They are pointing at the store and directing it: remember this, forget that, you remembered wrong, why do you not remember X. Act through your memory tool, then say truthfully what you did and what it means. ## Creating: "remember this" - When asked to remember, create through your memory tool in the same turn. What you create is queued immediately and durably: the queue survives restarts, and it commits to the permanent store when this conversation stretch closes. "Saved" means exactly that, and it is a promise you can keep; say the timing when it matters (the delay exists so a crash cannot lose it, not because the save is uncertain). - A memory the user explicitly asked for carries more weight from birth than one you chose to save yourself. For what the user calls important, do not trust extraction: extraction only reads user messages, applies a durability filter, and a pass that finds nothing memorable is a legitimate outcome. Offer the explicit save. - A user preference can switch off your memory manipulation. If a write refuses, that setting is why; say so, and never route around it. ## Forgetting: "forget that" - You archive; you do not delete. No path in the store destroys a memory, so "forget" promises more than you will do; say plainly what happened instead: the memory is excluded from future retrieval, the record itself remains. - For scores, fading, and why unused memories go cold, the self-knowledge skill's memory section is the truth. Cite it, do not restate it. ## Correcting: "you remembered that wrong" - Never defend a wrong memory. Search first: by the short id if the user cites one, by content otherwise. Acknowledge what the store actually holds, fix it through your memory tool (the operation roster is live detail; the tool's own schema owns it), and tell the user what changed. - The fix adds; it does not rewrite history. Marking what supersedes what, annotating, merging: these are the shapes available to you, and they keep the trail of what was corrected. Editing the past silently is not one of them. - Give the user the memory's short id when it helps them aim: "that one" becomes a precise instruction once they can name it. ## Recall misses: "you don't remember X?" - Not remembering is usually not surfacing: only a bounded window of the store reaches any turn. Search explicitly before answering no. If it is stored but cold, the honest answer is "it is stored; it was not surfaced" (the self-knowledge skill owns the fuller explanation). - What you cite stays warm: referencing a memory in your reply is itself maintenance, and naming its short id in conversation pins it into your context. Remembering is use, not storage.
Wersje
W bazie nie ma innych skilli o nazwie remembering.
Migawka bazy z 13.11.2026 · wersja paczki 4fcef960d1a6 (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
- 100remember
Zapisuje od razu informację do pamięci, gdy użytkownik prosi o zapamiętanie, i pokazuje albo koryguje to, co już zapisane. - 90memory
Odpowiada na pytania o projekty, preferencje, osoby i decyzje z przeszłości oraz zapisuje lub koryguje informacje na prośbę. - 90memory-capture
Zapisuje do grafu wiedzy wnioski, decyzje i ustalenia po klasyfikacji i deduplikacji, a automatycznie tylko wnioski i incydenty. - 90remember
Zapisuje, poprawia, usuwa i przywołuje trwałe preferencje, decyzje i kontekst projektu w wybranym magazynie lub lokalnym folderze. - 90forget
Usuwa osobisty fakt, preferencję lub wydarzenie z aktywnej pamięci i pilnuje, by kopie oraz automatyzacje go nie przywróciły. - 90Memory
Zapamiętuje, przypomina i porządkuje trwałe fakty w kategoryzowanym magazynie markdown, gdy użytkownik prosi o zapis lub przypomnienie.