New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Memory

by deathbyknowledge in deathbyknowledge/gsv

Retrieve and maintain the memory. An agent skill from deathbyknowledge/gsv.

MITAuto-check passed

Install Memory

skills CLI
$ npx skills add deathbyknowledge/gsv --skill memory -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install deathbyknowledge/gsv memory --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/deathbyknowledge/gsv.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/memory .claude/skills/memory && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
memory
GitHub stars
125
Token cost
~1.3k tokens
SKILL.md length
700 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Retrieve and maintain the memory. An agent skill from deathbyknowledge/gsv.

  • You need to remember something
  • SKILL.md covers Decide When to Read, Decide When to Write, Recover Missing Memory from… and Organize the Wiki, plus 1 more section
  • Calls jq and rg
  • Asks to remember something

What it does

Memory is an agent skill from deathbyknowledge/gsv. Retrieve and maintain the memory. Use when you need to remember something. personal history, preferences, people, projects, decisions, routines, places, or prior events or when the user asks to remember something.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Personal AI computer / distributed OS across all your devices. The licence is MIT.

When your agent uses it

  • You need to remember something
  • Asks to remember something

Example prompts

  • “/memory”

What it can do on your machine

Read from SKILL.md and the folder at commit 684cdc8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • jq
    • rg

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Memory loads about 1.3k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 700 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~55
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from deathbyknowledge/gsv at commit 684cdc8, republished under its MIT licence (© deathbyknowledge). 700 words, ~1,322 tokens.

Download SKILL.mdSave it as .claude/skills/memory/SKILL.md (or your agent's skills folder).
name
memory
description
Retrieve and maintain the memory. Use when you need to remember something. personal history, preferences, people, projects, decisions, routines, places, or prior events or when the user asks to remember something.

Manage Personal Memory

Memory belongs to the human, not to an individual agent. Every agent working for the same user reads and writes the same two layers:

  • The personal wiki contains durable information that is searched and loaded when relevant.
  • The owner's context.d/10-personal.md contains a very small set of stable facts and preferences that should affect nearly every interaction. It appears under the editable <user> context root in the prompt; do not confuse it with the current agent's ~/context.d/.

The Kernel responsibility ledger is working state, not personal memory. Do not copy unresolved responsibilities into the wiki merely because they exist. Record an outcome later only when it is useful history.

Decide When to Read

Retrieve memory before asking, recommending, or acting when the correct interpretation or outcome could depend on personal history that is not already in the current context. Examples include an ambiguous person or project name, the user's usual grocery order, travel details, prior decisions, recurring preferences, and where the user normally keeps something.

Do not search memory for self-contained questions whose answer cannot depend on the user. Do not search merely to prove that memory exists.

Search narrowly before opening broad pages:

bash
wiki search <query> --prefix personal

Use wiki info personal when the page location is unknown. Once a relevant page is known, use normal filesystem tools to read its Markdown under the path reported by wiki info.

Decide When to Write

Write immediately when the user explicitly says to remember an unambiguous fact or corrects an existing fact. Also write a concrete, stable fact or preference that the user states explicitly when it will improve future help.

When work reveals durable context about a person or relationship, preserve it promptly even if the user did not explicitly ask you to remember it. This includes identity, alternate names or handles, how the person relates to the user, ongoing shared projects, and meaningful interaction outcomes. Do not wait for compaction or a later request to make the information durable. Record inferred context as an inference rather than omitting it, and include a date or source when it will help resolve future ambiguity.

Search and merge before writing when the fact may already exist, refers to an ambiguous person or project, supersedes older information, or belongs on more than one existing page. Ship can perform short lookups and edits directly; delegate when the work benefits from parallel execution, separate context, or lengthy investigation.

Append a journal entry for a meaningful event or outcome whose chronology may matter later. Use ISO dates:

bash
pages/journal/YYYY/MM/YYYY-MM-DD.md
Show full SKILL.md (282 more words)Show less

Recover Missing Memory from Process History

Process history is lossless recovery evidence, not the primary memory system. Search the Personal wiki first. If relevant memory is missing and earlier Process work likely contains the answer, inspect that history and then repair the wiki with the durable facts you recover.

For compacted history belonging to a visible Process, prefer the structured Process interface:

bash
proc segments --pid <pid>
proc segment <segment-id> --pid <pid> --json

Reset and terminated Process transcripts are stored as gzipped JSONL under the run-as agent's home. Locate candidate archives and stream them through zcat; do not try to read compressed bytes as text or modify the immutable archive:

bash
find "$HOME/processes" -name '*.jsonl.gz'
zcat "$HOME/processes/<pid>/history/<archive>.jsonl.gz" \
  | jq -r '[.ts, .role, .content] | @tsv' \
  | rg -i '<term>'

Search narrowly by likely Process or date when possible. Once the missing context is recovered, merge the useful facts into the appropriate Personal wiki page. Do not copy raw transcripts, reasoning, or tool noise into memory.

Organize the Wiki

Search before adding duplicate information. Read a page before editing it. Keep index.md as an orientation page and use inbox/ only for information that genuinely cannot yet be placed. Promote durable information into topical pages such as:

  • pages/people/
  • pages/projects/
  • pages/preferences/
  • pages/decisions/
  • pages/routines/
  • pages/places/
  • pages/concepts/

When a name is ambiguous, make the short-name page a disambiguation page that points to specific pages. Replace superseded facts rather than accumulating contradictions. Prefer concise facts and useful context over prose about the act of remembering.

Use man wiki for exact wiki syntax and general wiki workflows.

Maintain Standing Memory

Edit the owner's context.d/10-personal.md only for explicit, stable facts or preferences that should be present in almost every interaction. Keep the file small, preserve its purpose statement, and replace corrected facts.

Unresolved work belongs in the r12y responsibility ledger. Do not duplicate it in standing context or the wiki.

© deathbyknowledge, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/memory of deathbyknowledge/gsv.

Open the folder on GitHubat commit 684cdc8

Compare with similar skills

Memory next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Memory compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Memory this skilldeathbyknowledge/gsv125—~1.3kAutomated safety check: PassMIT
Wiki Maintaineropenclaw/openclaw392k1 repos~462Automated safety check: PassMIT
Iterative Retrievalaffaan-m/ECC275k7 repos~1.6kAutomated safety check: PassMIT
Mem0 Remembermem0ai/mem067k—~410Automated safety check: PassApache-2.0
Remembergithub/awesome-copilot40k1 repos~1.6kAutomated safety check: PassMIT
Rememberalirezarezvani/claude-skills28k1 repos~784Automated safety check: PassMIT

Similar skills

  • Wiki Maintainer

    openclaw/openclaw

    Maintain the OpenClaw memory wiki vault with deterministic pages, managed blocks, and source-backed updates.

    392k GitHub starsUsed in 1 repo~462 tokens
    Knowledge ManagementAuto-check passed

  • Iterative Retrieval

    affaan-m/ECC

    Pattern for progressively refining context retrieval to solve the subagent context problem.

    275k GitHub starsUsed in 7 repos~1.6k tokens
    Agent WorkflowsAuto-check passed

  • Mem0 Remember

    mem0ai/mem0

    Stores a fact, preference or lesson verbatim in Mem0 through /mem0-remember and files it under a category such as preferences, decisions or goals.

    67k GitHub stars~410 tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Remember

    github/awesome-copilot

    Official

    Transforms lessons learned into domain-organized memory instructions (global or workspace).

    40k GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed

  • Remember

    alirezarezvani/claude-skills

    Explicitly save important knowledge to auto-memory with timestamp and context.

    28k GitHub starsUsed in 1 repo~784 tokens
    Agent WorkflowsAuto-check passed

  • Obsidian Vault Maintainer

    openclaw/openclaw

    Maintain an Obsidian-friendly memory wiki vault with wikilinks, frontmatter, and official Obsidian CLI awareness.

    392k GitHub starsUsed in 2 repos~262 tokens
    Knowledge ManagementAuto-check passed

More from deathbyknowledge/gsv

  • Process Orchestration

    deathbyknowledge/gsv

    Choose and use GSV delegation, subprocess, IPC, scheduling, and cron workflows.

    125 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Skill Authoring

    deathbyknowledge/gsv

    Create or revise reusable GSV agent workflows under skills.d.

    125 GitHub stars~508 tokensUpdated today
    Auto-check passed

  • Gsv Manual

    deathbyknowledge/gsv

    Consult the GSV Manual before saying GSV cannot do something, and for questions about its operating model, workflows, settings, devices, agents, automation, integrations, filesystem, desktop, shell…

    125 GitHub stars~243 tokensUpdated today
    Auto-check passed

  • Browser Target

    deathbyknowledge/gsv

    Use a paired browser: the user's signed-in profile, reaching any site they are logged into (calendar, mail, dashboards) with no integration.

    125 GitHub stars~3.1k tokensUpdated today
    Auto-check: warnings

  • Image Reading

    deathbyknowledge/gsv

    Read and analyze images on GSV or connected targets with img2txt.

    125 GitHub stars~343 tokensUpdated today
    Auto-check passed

Questions about Memory

What does Memory do?

Retrieve and maintain the memory. An agent skill from deathbyknowledge/gsv. Memory is an agent skill from deathbyknowledge/gsv. Retrieve and maintain the memory.

When should I use Memory?

Memory fits situations like: you need to remember something; asks to remember something.

How do I install Memory in Claude Code?

Run `npx skills add deathbyknowledge/gsv --skill memory -a claude-code`. Or copy the skill folder (skills/memory in deathbyknowledge/gsv) into .claude/skills/memory in your project. Claude Code loads it when a task matches its description.

How do I install Memory in Codex?

Run `npx skills add deathbyknowledge/gsv --skill memory -a codex`. Or copy the skill folder (skills/memory in deathbyknowledge/gsv) into .agents/skills/memory in your project. Codex loads it when a task matches its description.

Can I use Memory in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add deathbyknowledge/gsv --skill memory -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/memory, .gemini/skills/memory, .github/skills/memory and .opencode/skills/memory in your project.

What does Memory need to run?

Going by SKILL.md and its folder, Memory needs the command-line tools its instructions call (jq and rg).

Does Memory access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Memory safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Memory use?

Memory is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Memory use?

About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Memory?

Skills that share tags, products or a category with Memory: Wiki Maintainer (openclaw/openclaw, 392k stars), Iterative Retrieval (affaan-m/ECC, 275k stars), Mem0 Remember (mem0ai/mem0, 67k stars) and Remember (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Memory?

deathbyknowledge (a GitHub user) maintains it in deathbyknowledge/gsv, which has 125 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 7, 2026.

Source: deathbyknowledge/gsv on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.