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

Sdd Memory

by madebyaris in madebyaris/spec-kit-command-cursor

Recall and persist durable project knowledge (decisions, conventions, gotchas, architecture) across SDD sessions.

MITAuto-check passedDevelopment

Install Sdd Memory

skills CLI
$ npx skills add madebyaris/spec-kit-command-cursor --skill sdd-memory -a claude-code

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

GitHub CLI
$ gh skill install madebyaris/spec-kit-command-cursor sdd-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/madebyaris/spec-kit-command-cursor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/sdd-memory .claude/skills/sdd-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
sdd-memory
GitHub stars
198
Token cost
~862 tokens
SKILL.md length
377 words
Files
2 (incl. references)
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Recall and persist durable project knowledge (decisions, conventions, gotchas, architecture) across SDD sessions.

  • Works in 4 steps: Resolve Provider (always first) → Recall → Persist (what is worth remembering) → …
  • Development work in your project
  • SKILL.md covers When to Use, Step 0: Resolve Provider…, Step 1: Recall and Step 2: Persist (what is worth…, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Sdd Memory is an agent skill from madebyaris/spec-kit-command-cursor. Recall and persist durable project knowledge (decisions, conventions, gotchas, architecture) across SDD sessions. Provider-aware — supports standard (rules-only), Cursor native Memories, and mem0. Use at the start of planning/implementation to recall context, and at the end to persist discoveries.

Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/providers.md`).

It sits in Development. It works with Mem0. The repository describes itself as: SDD toolkit for Cursor IDE — /specify, /plan, /tasks to turn ideas into specs, plans, and actionable tasks. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/sdd-memory”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Resolve Provider (always first)
  2. Recall
  3. Persist (what is worth remembering)
  4. Hygiene

What it can do on your machine

Read from SKILL.md and the folder at commit 36b26f9. 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

    No scripts in the folder and no shell commands in SKILL.md.

    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

Sdd Memory loads about 862 tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 77 tokens; SKILL.md has 377 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~77
When it runs · the whole SKILL.md, loaded when a task matches
~862
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2k

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 madebyaris/spec-kit-command-cursor at commit 36b26f9, republished under its MIT licence (© madebyaris). 377 words, ~862 tokens.

Download SKILL.mdSave it as .claude/skills/sdd-memory/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
sdd-memory
description
Recall and persist durable project knowledge (decisions, conventions, gotchas, architecture) across SDD sessions. Provider-aware — supports standard (rules-only), Cursor native Memories, and mem0. Use at the start of planning/implementation to recall context, and at the end to persist discoveries.

SDD Memory Skill

Give SDD agents a configurable, optional long-term memory. The active backend is set in .sdd/config.json → memory.provider. This skill is a thin, provider-agnostic protocol: recall before you plan, persist after you learn.

When to Use

  • Recall — starting /brief, /research, /specify, /plan, or /implement: load relevant prior decisions, conventions, and gotchas before acting.
  • Persist — finishing a task or hitting a durable discovery: save facts worth remembering next time.
  • Manage — /sdd-memory configures, seeds, or disables the backend.

If memory.enabled is false or provider is standard, this skill is a no-op beyond reading .cursor/rules/ and specs/. Never block work waiting on memory.

Step 0: Resolve Provider (always first)

Read .sdd/config.json → memory. Branch on provider:

ProviderRecall sourcePersist target
standard.cursor/rules/ + specs/ onlynothing (write specs/rules instead)
cursor-nativeCursor-injected Memories + rules/specssurface durable facts as memory candidates (Cursor captures them)
mem0mem0 MCP search + rules/specsmem0 MCP add

Full per-provider read/write recipes: references/providers.md.

Step 1: Recall

  1. Derive 2–4 search intents from the task (e.g. "auth token storage decision", "API error-handling convention").
  2. Query the active provider (see references/providers.md). For standard, scan specs/ + rules.
  3. Summarize the top relevant memories into the working context. Cite the source. If a recalled memory conflicts with the current request, surface the conflict — do not silently follow stale memory.
Show full SKILL.md (163 more words)Show less

Step 2: Persist (what is worth remembering)

Save only durable, reusable, non-obvious facts in these categories (memory.scope):

  • decisions — chosen approach + the why (e.g. "Use Postgres over Mongo for relational integrity").
  • conventions — project rules an agent should follow (naming, structure, test style).
  • gotchas — traps, flaky areas, env quirks, "don't do X".
  • architecture — durable system shape (service boundaries, data flow).

Do not persist: transient state, secrets/tokens, full file contents, or anything already captured in a spec/rule.

Memory record shape
[category] <one-line fact> — <short why/context> (source: <task-id or file>)

Step 3: Hygiene

  • Prefer updating an existing memory over creating a near-duplicate.
  • When a decision is reversed, persist the reversal and mark the old one outdated (for cursor-native, tell the user it can be deleted in the UI; for mem0, update/delete the record).

Integration

  • Called by sdd-explorer, sdd-planner, and sdd-implementer (recall at start, persist at end).
  • Configured by /sdd-memory.
  • secrets are never stored — enforce this regardless of provider.

References

  • references/providers.md — exact recall/persist recipes for standard, cursor-native, and mem0 (incl. mem0 MCP tool calls and self-host notes).

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

Files

SKILL.md and 1 other file (references) in .cursor/skills/sdd-memory of madebyaris/spec-kit-command-cursor.

  • SKILL.md
  • references/providers.md

Open the folder on GitHubat commit 36b26f9

Compare with similar skills

Sdd 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.

Sdd Memory compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sdd Memory this skillmadebyaris/spec-kit-command-cursor198—~862Automated safety check: PassMIT
Mem0 Status Checkmem0ai/mem067k—~1.5kAutomated safety check: PassApache-2.0
ImportThinkfleetAI/memmesh420—~342Automated safety check: PassApache-2.0
Mem0 Integration Pipelinemem0ai/mem067k—~3.3kAutomated safety check: PassApache-2.0
Mem0 Platform SDKmem0ai/mem067k1 repos~2.2kAutomated safety check: PassApache-2.0
Mem0 CLI Memory Commandsmem0ai/mem067k—~2kAutomated safety check: NotesApache-2.0

Similar skills

  • Mem0 Status Check

    mem0ai/mem0

    Runs a four-part diagnostic on the mem0 plugin, checking the API key, identity resolution, memory search and memory write, then reports one pass-or-fail summary.

    67k GitHub stars~1.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Import

    ThinkfleetAI/memmesh

    Import memories into MemMesh from an exported file, a native MEMORY.md / CLAUDE.md, an ADR/decision log, or a mem0 export.

    420 GitHub stars~342 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Mem0 Integration Pipeline

    mem0ai/mem0

    Adds Mem0 memory to an existing repository with a test-first pipeline that detects the language, lets you choose Platform or open source, and leaves a local feature branch.

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

  • Mem0 Platform SDK

    mem0ai/mem0

    Adds persistent memory to AI apps with the Mem0 Python and TypeScript SDKs: store, search, update and delete user memories, with framework integrations.

    67k GitHub starsUsed in 1 repo~2.2k tokens
    AI & LLM EngineeringAuto-check passed

  • Mem0 CLI Memory Commands

    mem0ai/mem0

    Adds, searches, lists, updates and deletes memories on the Mem0 platform from the terminal with the mem0 command, including a JSON mode built for agents.

    67k GitHub stars~2k tokensUpdated today
    Agent WorkflowsAuto-check: notes

  • Mem0 Provider for Vercel AI SDK

    mem0ai/mem0

    Adds persistent memory to Vercel AI SDK apps with the Mem0 provider, using a wrapped model or standalone retrieve and store utilities.

    67k GitHub stars~2.3k tokensUpdated today
    AI & LLM EngineeringAuto-check passed

More from madebyaris/spec-kit-command-cursor

  • Sdd Evolve

    madebyaris/spec-kit-command-cursor

    Update specifications with discoveries made during development.

    198 GitHub stars~562 tokensUpdated 3 mo ago
    Auto-check passed

  • Sdd Implementation

    madebyaris/spec-kit-command-cursor

    Execute planned implementations following todo-lists systematically.

    198 GitHub stars~444 tokensUpdated 3 mo ago
    Auto-check passed

  • Sdd Research

    madebyaris/spec-kit-command-cursor

    Pattern investigation and technical research before specification.

    198 GitHub stars~1.3k tokensUpdated 3 mo ago
    Auto-check passed

  • Sdd Audit

    madebyaris/spec-kit-command-cursor

    Compare implementation against specifications, identify gaps and issues.

    198 GitHub stars~405 tokensUpdated 3 mo ago
    Auto-check passed

  • Sdd Planning

    madebyaris/spec-kit-command-cursor

    Generate technical plans from specifications. An agent skill from madebyaris/spec-kit-command-cursor.

    198 GitHub stars~499 tokensUpdated 3 mo ago
    Auto-check passed

Works with

Categories

Questions about Sdd Memory

What does Sdd Memory do?

Recall and persist durable project knowledge (decisions, conventions, gotchas, architecture) across SDD sessions. Sdd Memory is an agent skill from madebyaris/spec-kit-command-cursor. Recall and persist durable project knowledge (decisions, conventions, gotchas, architecture) across SDD sessions.

When should I use Sdd Memory?

Sdd Memory fits situations like: development work in your project.

How do I install Sdd Memory in Claude Code?

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

How do I install Sdd Memory in Codex?

Run `npx skills add madebyaris/spec-kit-command-cursor --skill sdd-memory -a codex`. Or copy the skill folder (.cursor/skills/sdd-memory in madebyaris/spec-kit-command-cursor) into .agents/skills/sdd-memory in your project. Codex loads it when a task matches its description.

Can I use Sdd 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 madebyaris/spec-kit-command-cursor --skill sdd-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/sdd-memory, .gemini/skills/sdd-memory, .github/skills/sdd-memory and .opencode/skills/sdd-memory in your project.

What does Sdd Memory need to run?

SKILL.md names no scripts, command-line tools or credentials: Sdd Memory is instructions for the agent only.

Does Sdd 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 Sdd 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 Sdd Memory use?

Sdd 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 Sdd Memory use?

About 862 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.

What are the alternatives to Sdd Memory?

Skills that share tags, products or a category with Sdd Memory: Mem0 Status Check (mem0ai/mem0, 67k stars), Import (ThinkfleetAI/memmesh, 420 stars), Mem0 Integration Pipeline (mem0ai/mem0, 67k stars) and Mem0 Platform SDK (mem0ai/mem0, 67k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sdd Memory?

madebyaris (a GitHub user) maintains it in madebyaris/spec-kit-command-cursor, which has 198 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on June 22, 2026.

Source: madebyaris/spec-kit-command-cursor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.