AlphaMoatによると、2026-10時点でMemoryのダウンロード数は60,063、スター数は30で、累計ダウンロード数で今回のランキング対象AIスキル10,914件中399位、AIエージェントでは1,632件中89位です。
一覧の初期表示は累計ダウンロード数順で、スター数順にも並べ替えできます。詳細ページの順位は累計ダウンロード数で計算しています。
| プラットフォーム | ダウンロード数 | スター数 | コメント |
|---|---|---|---|
| ClawHub ↗ | 2万 | 18 | - |
| SkillHub ↗ | 6万 | 30 | — |
プラットフォームごとに集計方法と集計時点が異なります。
データはすべて ~/Clawic/data/memory/ に markdown として置かれ、外部サービスにも接続せずネットワーク要求も行いません。事実の保存、分からないと答える前の検索、事実が変わったときの更新に使います。組み込みの記憶は読み取り専用かつ同期は一方向とみなし、秘密情報は保存しません。
資料公開日 2026-10-27
スキルのドキュメントをもとに生成した例であり、実際の実行結果ではありません。
2026-09 から集計方法を変更し、同名スキルを作者ごとに分けて集計し、全スキルを対象にしました。破線は変更前の月で、変更後のデータとは直接比較せず、変更をまたぐ増減も計算していません。 同名の別スキルがあるため、変更前のデータは現在ダウンロード数が最も多いこのスキルに帰属させています。
| 月 | ダウンロード数 | 前月比 | スター数 |
|---|---|---|---|
| 2026-10 | 6万 | — | 30 |
| 2026-09 | 3.1万 | — | 30 |
| 2026-08 | 2.7万 | +8.3% | 30 |
| 2026-07 | 2.5万 | +8.7% | 28 |
| 2026-06 | 2.3万 | +7.4% | 24 |
| 2026-05 | 2.1万 | — | 20 |
| 2026-03 | 1.5万 | — | 8 |
作者が公開した元のファイルをテキストのまま表示しています。AlphaMoat による編集や審査はしていません。リンクはクリックできません。コマンドは内容を確認してから実行してください。取得日 2026-10-23。
--- name: Memory slug: memory version: 1.0.7 description: >- Remembers, recalls, and organizes durable facts in a categorized markdown store at ~/Clawic/data/memory/, parallel to built-in agent memory. Use when the user says remember this, save this, note that for later, or don't forget; when they ask what did I tell you about X, when did we decide Y, or who is Z; when a stored fact is wrong, outdated, or contradicts what they just said; when they want something forgotten or deleted; when
recall misses, returns stale facts, or slows down as the store grows; when duplicate or
conflicting entries appear; when consolidating scattered notes, importing an existing
vault, or sharing memory across devices and agents. Not for session-scoped context the
runtime already holds, note-taking apps (notes), journaling practice (journal), or study
techniques like spaced repetition (learn, active-recall).
homepage: https://clawic.com/skills/memory
changelog: "Display name shown correctly"
metadata:
clawdbot:
emoji: 🧠
requires:
bins: []
os:
- linux
- darwin
- win32
displayName: Memory
configPaths:
- ~/Clawic/data/memory/
---
All data lives in `~/Clawic/data/memory/` on the user's machine — plain markdown, no external services, no network requests. Configuration in `~/Clawic/data/memory/config.yaml` (`setup.md` on first use, `memory-template.md` for file formats). If you have data at an old location (`~/memory/` or `~/clawic/memory/`), move it to `~/Clawic/data/memory/`.
## When To Use
- User says "remember this", "save this", "don't forget" about anything with lasting value
- Recall: "what did I tell you about X", "when did we decide Y", "who is Z" — search `~/Clawic/data/memory/` before answering "I don't know"
- A stored fact changed, turned out wrong, or contradicts what the user just said
- The user wants something forgotten, or asks what is stored about a subject
- Consolidating scattered notes, importing an existing vault, or sharing the store across devices and agents
- Recall degrades: misses, duplicates, stale answers, slow lookups as the store grows
- Not for: session-scoped context built-in memory already holds, secrets (Rule 9), note-taking apps (`notes`), journaling (`journal`), or study/spaced-repetition (`learn`, `active-recall`)
- Not for facts a domain skill already stores in its own `~/Clawic/data/<slug>/` (Rule 5): the pet fact goes to `dog`/`cat`, the household fact to `family`, the plant fact to `garden`, the code-style fact to `coding`
## Quick Reference
| Situation | Play |
|-----------|------|
| No `~/Clawic/data/memory/` yet | Run the setup conversation — `setup.md` |
| User shares something durable | Write the entry + update the category INDEX **before** replying (Rule 3); what qualifies → `capture.md` |
| User asks about the past | Search ladder: root INDEX → category INDEX → one file (→ Finding Things); it missed → `recall.md` |
| "Actually it's X now" | Supersede: new dated line, old line moved to History with its own date (Rule 8) → `conflicts.md` |
| Stored fact was never true | Delete it — archiving a wrong fact resurfaces it as true (Rule 8) |
| Two files about the same person or project | Merge into the older file, leave a one-line pointer behind → `entities.md` |
| Two people share a name | Disambiguate the filename with a stable token (company, role), never `-2` → `entities.md` |
| "Forget that" / delete request | Purge file + index rows + inbound links, then report exactly what was removed → `privacy.md` |
| User offers a password, key, or token | Decline and store a pointer to where it lives (Rule 9) → `privacy.md` |
| Existing vault or another agent's memory to import | Category-by-category with a dedupe pass, never a bulk copy → `migration.md` |
| Store lives in Dropbox/iCloud/git, or two agents write to it | `sync.md` |
| Category INDEX past `index_split_at` (default 100) | Split along the axis you retrieve by (Rule 6) → `layouts.md` |
| Over 500 files and recall is degrading | `scaling.md` |
| Deciding how much memory to read this session | Root INDEX only at start; open one file after the index names it → `sessions.md` |
| Fact fits two categories | One canonical home, links from the rest (Rule 5) |
| Fact belongs to a domain that has its own Clawic skill and store | Write it in that skill's `~/Clawic/data/<slug>/`, keep only a pointer line here (Rule 5) |
| Anything else | Closest existing category beats a new one; if nothing fits, `inbox/` and sort it at maintenance |
Depth on demand: `capture.md` what to write and how to phrase it · `recall.md` search ladder, query expansion, proactive lookup · `conflicts.md` changed vs wrong facts, temporal validity · `entities.md` people, projects, aliases, merges · `privacy.md` secrets, sensitive subjects, deletion requests · `migration.md` importing and exporting · `sync.md` multi-device, git, multi-agent · `scaling.md` growth thresholds and when plain files stop being enough · `sessions.md` read/write protocol per session · `maintenance.md` cadences and integrity repair · `layouts.md` folder structures and split axes · `commands.md` operator toolkit · `troubleshooting.md` symptom→cause · `memory-template.md` file formats · `setup.md` first run.
## Core Rules
1. **Built-in memory is read-only territory, and sync runs one way.** Never modify the runtime's MEMORY.md or workspace `memory/` — the runtime owns them and may rewrite them, so your edits are lost or conflict. This skill reads them and copies into `~/Clawic/data/memory/sync/`, reformatted, with the sync date recorded in `sync/INDEX.md`. Never the reverse, never automatic.
2. **The user defines the structure.** Create categories from their words, not a preset taxonomy. A category created before its first item rots empty and teaches the user the system is dead weight.
| They say... | Create |
|-------------|--------|
| "I have many projects" | `~/Clawic/data/memory/projects/` |
| "I meet lots of people" | `~/Clawic/data/memory/people/` |
| "I want to track decisions" | `~/Clawic/data/memory/decisions/` |
| "I'm learning [topic]" | `~/Clawic/data/memory/knowledge/[topic]/` |
| "I collect [things]" | `~/Clawic/data/memory/collections/[things]/` |
3. **Write before you reply.** Sequence: write the entry → update the category INDEX.md → then respond. The reply is disposable; the write is the durable part. A session that dies mid-reply then loses nothing.
4. **Every entry carries a date and a source.** `YYYY-MM-DD` plus one of `stated` (the user said it), `observed` (seen in a file or output), `inferred` (the agent concluded it). Undated facts can't be judged stale — "Alice works at Acme" means different things written last week and two years ago. Unsourced facts can't be trusted: an inference stored as a statement is the main way a memory store poisons itself, because Rule 8 lets a stated fact overrule an inferred one only if you can tell them apart.
5. **One fact, one home — including homes outside this store.** Store each fact in the file it is most *about*; everywhere else links to it (`→ people/alice.md`). Duplicated facts diverge silently — the copy you update is never the copy you find later. This applies across skills: when the fact's domain has its own Clawic store (`~/Clawic/data/dog/`, `cat/`, `family/`, `couple/`, `garden/`, `kanban/`, `coding/`, `employee/`), that store is the home and this one keeps at most a pointer line — "dog's diet → `~/Clawic/data/dog/`". Writing "the dog is allergic to chicken" in both places is the silent fork this rule exists to prevent.
6. **Every folder has an INDEX.md, capped at `index_split_at` (default 100).** Past the cap, split into subcategories. Capacity = cap^depth: at the default, two levels hold 10,000 items, three hold 1,000,000, and every lookup stays two or three small reads instead of one giant scan. Every number below written as 100 is that default — read `config.yaml` before judging any index size. Archive indices are exempt (rarely read, off the hot path).
7. **Keep entry files lean.** An entry is loaded whole to answer one question, so its size is a tax on every question. Past `entry_max_lines` (default ~200), move the `## History` bulk to `{name}-history.md` and keep the dossier short; the history file is opened only when someone asks about the past.
8. **Changed facts supersede; wrong facts get deleted.** A fact that *became* false (Alice left Acme) keeps its old line, dated, under History, with the new line on top — the timeline is itself information. A fact that was *never* true (she never worked there) is deleted outright: archived wrong facts resurface later as truth. Test: "was this true on the day it was written?" Yes → supersede. No → delete.
9. **Never store secrets.** These files are plaintext with no encryption. Decline passwords, API keys, tokens, and full card or account numbers; store a pointer instead — "API key lives in [their vault], rotated 2026-07".
## Built-In Memory vs This Store
Built-in memory holds current context and works automatically. This store holds everything that grows. Parallel and complementary — never a replacement.
| | Built-in memory | This skill (`~/Clawic/data/memory/`) |
|---|---|---|
| Size | Small, summaries | Unlimited |
| Written by | The runtime, automatically | This skill, by explicit rules |
| Holds | Current status, quick facts, recent decisions | Full histories, dossiers, decision logs, collections, domain knowledge |
| Touched here | Read-only (sync source) | Fully managed |
| Survives | The runtime's own compaction rules | Until deleted on purpose |
The same item can live in both — summary there, detail here, and the summary points here. When in doubt: does it grow over time, or does it need to be findable in a year? Then it belongs here.
## Entry Anatomy
Every entry file, whatever the category, carries the same four things (full templates: `memory-template.md`):
```markdown
# Alice Smith <- display name, human-readable
**Keywords:** Ali, PM, product manager, Acme, alpha project <- retrieval aliases
**Updated:** 2026-07-25 <- freshness at a glance
## Facts
- 2026-07-25 · stated · Moved to Northwind as Head of Product
- 2026-03-02 · stated · Prefers async updates, no calls before 10:00
## History
- 2024-11-08 · stated · Joined Acme as PM (superseded 2026-07-25)
```
- **Filename is a stable slug** (`alice-smith.md`), never the display name — renames break every inbound link (`entities.md`).
- **One fact per line, dated and sourced** (Rule 4). Lines, not paragraphs: a paragraph can't be superseded or deleted surgically.
- **Keywords is the retrieval index**, not decoration — see Finding Things.
## Finding Things
| Store size | Strategy |
|-------------|----------|
| <50 files | `grep -ri "keyword" ~/Clawic/data/memory/` — a full scan is cheap |
| 50–500 files | Indices first: `grep -i "keyword" ~/Clawic/data/memory/*/INDEX.md`, then open the one matching file |
| >500 files | Hierarchical: root INDEX → category INDEX → file; semantic search if `search_backend` says the runtime has it |
```bash
cat ~/Clawic/data/memory/INDEX.md # which categories exist
grep -i "alpha" ~/Clawic/data/memory/*/INDEX.md # which category holds it
cat ~/Clawic/data/memory/projects/alpha.md # the answer
```
Vocabulary asymmetry is the reason recall misses: grep matches the words used at *write* time, recall arrives in *today's* words. Try at least 3 variants — the user's word, the formal name, the entity's canonical slug — before concluding absence, and when a miss is later resolved, add the missed term to that file's `Keywords:` line so the same search never misses twice (`recall.md`).
## When Facts Change
| The user says | Do |
|---|---|
| "It's X now" | Supersede: new dated line on top, old line to History with its original date (Rule 8) |
| "That was never right" | Delete the line; if the whole entry was wrong, delete the file and its index row |
| "I'm not sure any more" | Keep the fact, mark it `stale YYYY-MM-DD`; a doubted fact recalled with its doubt beats a silent gap |
| Two stored facts disagree | The one with the later date and the stronger source wins; `stated` beats `observed` beats `inferred` on the same date |
| Nothing — the fact just aged | Class-based expiry: identity facts never expire, role and address facts get re-checked yearly, project-state facts within weeks (`conflicts.md`) |
## Maintenance
**Every session:** anything durable said this session is written (Rule 3); anything unclear is in `inbox/`.
**Weekly** (or per `maintenance_cadence`): sort `inbox/` into categories; update any INDEX touched during the week; archive items with terminal status (completed, cancelled, inactive).
**Monthly:** audit index sizes (`wc -l ~/Clawic/data/memory/*/INDEX.md`); split any category past `index_split_at`; sweep for stale facts by class; delete entries that are wrong. Repair procedures and the integrity checks: `maintenance.md`.
## Output Gates
Before replying when the user shared something durable:
- Is it written to `~/Clawic/data/memory/` already? (Rule 3 — the write precedes the reply)
- Is the category INDEX.md row added or updated?
- Does the entry carry a date and a source marker? (Rule 4)
Before answering "I don't remember": did the full search ladder run with ≥3 keyword variants, including `inbox/`, `sync/`, and built-in memory?
Before storing: does it contain a credential (Rule 9) or fall under `excluded_topics`? → decline and say so once.
Before deleting: is this a wrong fact rather than an outdated one (Rule 8), and does `delete_policy` require confirmation first?
## Configuration
User-dependent variables. Defaults apply until the user states a preference; store them in `~/Clawic/data/memory/config.yaml`.
| Variable | Type | Default | Effect |
|---|---|---|---|
| index_split_at | number (25-250) | 100 | Entry count at which a category INDEX splits into subcategories (Rule 6; split axes in `layouts.md`) |
| entry_max_lines | number (100-500) | 200 | Line count at which an entry's History moves to `{name}-history.md` (Rule 7) |
| delete_policy | confirm \| direct | confirm | Whether removing a file or fact needs an explicit go-ahead first (Output Gates, `privacy.md`) |
| recall_citations | bool | true | Whether a recalled fact is answered with its file path and date, or as a bare answer (`recall.md`) |
| sync_from_builtin | bool | false | Enables the one-way built-in → `sync/` copy during maintenance (Rule 1) |
| excluded_topics | list | empty | Subjects never written to the store even when mentioned; the agent says so once instead of storing (`privacy.md`) |
| inbox_enabled | bool | true | Whether unclear items land in `inbox/` or force a category decision at capture time (`capture.md`) |
| maintenance_cadence | weekly \| monthly \| on-demand | weekly | Frequency of the inbox sort, index audit, and staleness sweep (Maintenance) |
| search_backend | grep \| semantic | grep | Which retrieval path the >500-file rung of the search ladder uses (Finding Things) |
Preference areas — customizable dimensions; a stated preference gets recorded in config.yaml and applied:
- **Taxonomy**: which categories exist and what belongs in each — affects Rule 2 and every capture routing decision
- **Capture threshold**: write everything said, or only explicit "remember this" — affects the durability test in `capture.md`
- **Naming conventions**: filename style, entity slug format, index columns — affects `entities.md` and `memory-template.md`
- **Retrieval style**: how much surrounding context comes back with an answer, and whether the agent volunteers related facts unasked — affects `recall.md` and `sessions.md`
- **Privacy posture**: which subjects need an explicit go-ahead, whether third-party personal details are stored at all — affects `privacy.md`
- **Sync and versioning**: cloud folder, git history, which agents share the store — affects `sync.md`
- **Language**: which language entries are written in when it differs from the conversation — affects every write
## Traps
| Trap | Why it fails | Do instead |
|------|--------------|------------|
| Modifying built-in memory | The runtime owns it; edits are overwritten or conflict | Read-only, parallel system (Rule 1) |
| Batching writes for later | The session can end between hearing and writing | Write before replying (Rule 3) |
| Same fact in two files | Copies diverge; you update one and retrieve the other | One home + links (Rule 5) |
| Storing the conversation instead of the fact | "User mentioned maybe Postgres" answers nothing a year later | Store the resolved fact with its date and source (`capture.md`) |
| An inference written as a statement | Later contradicts the user and gets defended as if they had said it | Source marker on every line (Rule 4) |
| Archiving a wrong fact | Archive preserves it; it resurfaces as true | Wrong → delete; old-but-true → supersede (Rule 8) |
| Undated entries | A current fact and a two-year-old one look identical | Date-stamp everything (Rule 4) |
| No indices | Every lookup degrades to a full-folder grep; misses rise with size | INDEX.md in every folder (Rule 6) |
| One giant category | 500 unsplit items = slow scans and noisy grep hits | Split at `index_split_at` (Rule 6) |
| Renaming files by hand | Dead links — recall says "not found" while the data sits there | Rename = `mv` + fix every index and inbound link (`entities.md`) |
| Bulk-copying an old vault in | Mass duplicates with no dates or sources, and the store loses trust on day one | Category slices with a dedupe pass (`migration.md`) |
| Syncing everything from built-in | Duplication of things built-in already answers | Sync only what needs deep structure (Rule 1) |
| Loading the whole store at session start | Burns context on facts nobody asked about | Root INDEX first, one file after (`sessions.md`) |
| Storing a fact a domain skill already owns | Two stores answer the same question and neither knows about the other | Domain store is the home; keep a pointer here (Rule 5) |
## Where Experts Disagree
- **Capture everything vs curate.** Capture-everything survives only with real maintenance; curated stores stay fast but lose the fact nobody thought was important. Default: capture durable facts, inbox the ambiguous ones, and let the weekly sort be the curation step — the split lives in the `capture threshold` preference area.
- **Folders vs flat plus tags.** Flat + `Keywords:` scales fine for retrieval and badly for browsing; folders make a human able to read the store like a book. Default: folders, because the human decides whether the system is worth keeping. Escape hatch: one flat category with heavy keywords for domains with no natural taxonomy.
- **Plain files vs a database.** Grep over markdown stays honest, portable, and inspectable; an index or embedding store answers fuzzy questions plain grep can't. Default: files until >500 entries AND recall still misses after the Keywords fix (`scaling.md`) — the migration is one-way in practice.
## Security & Privacy
**Data location:**
- All data in `~/Clawic/data/memory/` on the user's machine
- No external services, no network requests
**This skill does NOT:**
- Modify built-in agent memory (reads only, for one-way sync)
- Send data anywhere
- Store credentials — plaintext storage; secrets are declined (Rule 9)
- Write subjects listed in `excluded_topics`
**Guardrails:** deletion requests are honored in full and reported back (`privacy.md`); anything stored about third parties is limited to what the user needs recalled.
## Related Skills
More Clawic skills, get them at https://clawic.com/skills/memory (install if the user confirms):
- `notes` — note-taking into apps like Obsidian, Notion, or Apple Notes; use it when the destination is an app, not a durable fact store
- `journal` — journaling practice, prompts, and reflection; use it for the entry the user writes, not the fact you extract from it
- `learn` — spaced repetition and study tracking; use it when the goal is knowing something by heart, not looking it up
- `active-recall` — retrieval practice as a study technique; use it when the user wants to be tested, not answered
- `decide` — decision-making patterns on top of the `decisions/` category this store builds
## Feedback
- If useful, star it: https://clawic.com/skills/memory
- Latest version: https://clawic.com/skills/memory
Part of [Clawic](https://clawic.com), the verified skill library. Get this skill: https://clawic.com/skills/memory.
開発中の学び、エラー、訂正を Markdown ファイルに記録し、再利用やワークスペースの記憶への昇格に備えます。
やりたいことを自然文で伝えると、ローカルとリモートのカタログからスキルを探して推薦するスキルです。
AI エージェント向けのブラウザ自動化コマンドラインスキルです。
利用者の訂正と自己点検を層構造の記憶に蓄え、使われ方に応じて昇格や保管を行うスキルです。
AI エージェントの先回り、作業記憶、振り返りの手順を計画するためのワークスペース設定ガイドです。
効果的な Claude スキルの作成・更新ガイドです。
第三者のスキルを入れる前に、出所と権限と危険な作りを手順に沿って調べるスキルです。
以李白(701—762,字太白,号青莲居士,世称诗仙)的诗学观、意象系统与口吻,进行唐诗赏析、文学评论、考据问答与拟体创作。触发词:李白、李太白、太白、青莲居士、诗仙、谪仙人、将进酒、静夜思、蜀道难、唐诗、盛唐诗人、浪漫主义诗人、拟李白风格、以李白视角、李白会怎么写、用李白口吻。能力:诗词鉴赏与风格DNA解析、诗学观与文学谱系评述、诗句出处考据与真伪边界标注、以李白口吻答问、拟李白体旧体诗(必显式标注非原作)。适用边界:仅用于唐代文学与古典诗歌相关话题,非此类话题不触发;本 skill 为文学普及与研究辅助,不代表李白本人立场,所拟之作均非李白原作;涉及生平佚事、篇目归属等内容不构成学术定论,皆标存疑或待考。
利用者の訂正と自己点検を層構造の記憶に蓄え、使われ方に応じて昇格や保管を行うスキルです。
数式、書式、ブックの構造を保ったまま Excel ファイルを作成・点検・編集するスキルです。
Word と DOCX 文書を扱うための作業指針で、編集後にスタイルや番号、レイアウトが崩れないことに重点を置きます。
複数の動画モデル API をまたぐ AI 動画生成と編成のスキルです。
データベースや表計算、書き出した生データを意思決定に使える結論へ変えるデータ分析スキルです。
データ月:2026-10 · ダウンロード数とスター数は公開スキルレジストリ(ClawHub、SkillHub)から月単位で集計しています。詳しくはデータの方法論をご覧ください。