memory

johnlindquist/claude · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/johnlindquist/claude --skill memory
0 commentsdiscussion
summary

Store and retrieve knowledge across sessions using semantic search.

skill.md

Memory - Persistent Knowledge Storage

Store and retrieve knowledge across sessions using semantic search.

Prerequisites

Install basic-memory:

pip install basic-memory

CLI Reference

Write a Note

# Basic note
basic-memory tool write-note --title "Note Title" --content "Note content in markdown"

# With tags
basic-memory tool write-note --title "React Patterns" --content "# Content here" --tags "react,patterns,frontend"

# To specific folder
basic-memory tool write-note --title "Meeting Notes" --content "# Notes" --folder "meetings"

# With specific project
basic-memory tool write-note --title "Project Notes" --content "# Notes" --project myproject

Read a Note

# By identifier/permalink
basic-memory tool read-note "note-title"

# From specific project
basic-memory tool read-note "note-title" --project myproject

Search Memories

# Semantic search (query is positional)
basic-memory tool search-notes "your search query"

# Limit results
basic-memory tool search-notes "react hooks" --page-size 10

# Search by permalink
basic-memory tool search-notes "pattern" --permalink

# Search by title
basic-memory tool search-notes "meeting" --title

# Filter by date
basic-memory tool search-notes "feature" --after_date "7d"

# With specific project
basic-memory tool search-notes "authentication" --project myproject

Build Context for a Topic

# Get related notes for a URL/topic (URL is positional)
basic-memory tool build-context "memory://topic/authentication"

# With depth and timeframe
basic-memory tool build-context "memory://note/my-note" --depth 2 --timeframe 30d

# With specific project
basic-memory tool build-context "memory://topic/api" --project myproject

List Recent Activity

# Default (depth 1, 7 days)
basic-memory tool recent-activity

# With depth
basic-memory tool recent-activity --depth 3

# With timeframe
basic-memory tool recent-activity --timeframe 30d

# Combined
basic-memory tool recent-activity --depth 3 --timeframe 14d

Continue Conversation

# Get prompt to continue previous work
basic-memory tool continue-conversation "previous topic or context"

Sync Database

basic-memory sync

Check Status

basic-memory status

Note Format

Notes are stored as markdown with YAML frontmatter:

---
title: My Note
tags: [tag1, tag2]
created: 2024-01-15
---

# My Note

Content here in markdown format.

## Sections

More content...

Workflow Patterns

Save Learning

When you discover something useful:

basic-memory tool write-note \
  --title "TypeScript Utility Types" \
  --content "# Utility Types\n\n- Partial<T> - Makes all properties optional\n- Required<T> - Makes all properties required\n- Pick<T, K> - Picks specific properties" \
  --tags "typescript,types,reference"

Save Decision

When making an architectural decision:

basic-memory tool write-note \
  --title "Auth Strategy Decision" \
  --content "# Decision: Use JWT for API auth\n\n## Context\n...\n\n## Decision\n...\n\n## Consequences\n..." \
  --tags "architecture,auth,decision" \
  --folder "decisions"

Retrieve Context

Before starting related work:

# Search for relevant notes
basic-memory tool search-notes "authentication jwt tokens"

# Or build comprehensive context
basic-memory tool build-context "memory://topic/api-authentication"

Review Recent Work

basic-memory tool recent-activity --depth 5 --timeframe 7d

Use Cases

Personal Wiki

  • Store code snippets and patterns
  • Document project decisions
  • Keep reference material

Learning Log

  • Record things you learn
  • Tag by topic for later retrieval
  • Build knowledge over time

Project Context

  • Save project-specific knowledge
  • Retrieve relevant context at session start
  • Share knowledge across sessions

Best Practices

  1. Use meaningful titles - They become permalinks
  2. Add tags - Improves search and organization
  3. Use markdown - Full markdown support in content
  4. Organize with folders - Group related notes
  5. Search before writing - Check if knowledge already exists
  6. Keep notes focused - One topic per note
  7. Update, don't duplicate - Revise existing notes

Integration Pattern

Session Start

# Get context for today's work
basic-memory tool build-context "memory://topic/feature-youre-building"

During Work

# Save discoveries
basic-memory tool write-note --title "Discovery Title" --content "What I learned"

Session End

# Sync to ensure persistence
basic-memory sync
how to use memory

How to use memory on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add memory
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/johnlindquist/claude --skill memory

The skills CLI fetches memory from GitHub repository johnlindquist/claude and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/memory

Reload or restart Cursor to activate memory. Access the skill through slash commands (e.g., /memory) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.843 reviews
  • Evelyn Yang· Dec 12, 2024

    Keeps context tight: memory is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Benjamin Ndlovu· Dec 8, 2024

    memory has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Michael Perez· Nov 27, 2024

    Solid pick for teams standardizing on skills: memory is focused, and the summary matches what you get after install.

  • Rahul Santra· Nov 11, 2024

    Useful defaults in memory — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Zara Rahman· Nov 3, 2024

    memory is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Michael Farah· Oct 22, 2024

    memory reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Evelyn Dixit· Oct 18, 2024

    I recommend memory for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Pratham Ware· Oct 2, 2024

    Registry listing for memory matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Evelyn Menon· Sep 25, 2024

    Useful defaults in memory — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Yash Thakker· Sep 17, 2024

    Keeps context tight: memory is the kind of skill you can hand to a new teammate without a long onboarding doc.

showing 1-10 of 43

1 / 5