memory-manager

learnwy/skills · 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/learnwy/skills --skill memory-manager
0 commentsdiscussion
summary

Personal Use Only - This skill is configured for wangyang.learnwy's personal AI memory management.

skill.md

Memory Manager

Personal Use Only - This skill is configured for wangyang.learnwy's personal AI memory management.

Persistent memory system for AI assistants. Load this skill at the start of every session.

⚠️ CRITICAL: File Operation Rules

Due to AI IDE sandbox restrictions, NEVER use Write/SearchReplace tools to modify memory files.

MUST use RunCommand tool to execute bash scripts:

RunCommand: bash {skill_dir}/scripts/write-memory.sh SOUL.md "content"
RunCommand: bash {skill_dir}/scripts/append-history.sh "history-YYYY-MM-DD-N.md" "content"
RunCommand: bash {skill_dir}/scripts/backup-history.sh --all

If you skip scripts and use Write tool directly, you will get "sandbox restriction" errors.

Memory Path

Memory files are stored at: ~/.learnwy/ai/memory/

This path is outside the skill directory to:

  1. Avoid data loss when skill is updated/reinstalled
  2. Bypass AI IDE sandbox restrictions on skill directory writes
  3. Keep memory persistent across different IDE installations

Session Start (ALWAYS DO THIS)

At the beginning of every conversation, read memory files using Read tool:

Read: ~/.learnwy/ai/memory/SOUL.md
Read: ~/.learnwy/ai/memory/USER.md

This ensures continuity across sessions.

Directory Structure

~/.learnwy/ai/memory/
├── SOUL.md          # AI's soul - identity, principles, learned wisdom
├── USER.md          # User's profile - preferences, context, history
├── history/         # Session history files (max 3, then consolidate)
└── archive/         # Consolidated history

memory-manager/      # Skill directory (this skill)
├── SKILL.md
├── .gitignore
└── scripts/
    ├── init-memory.sh       # Initialize memory directory
    ├── write-memory.sh      # Write SOUL.md/USER.md (whitelist only)
    ├── append-history.sh    # Create session history
    ├── backup-history.sh    # Backup history to archive
    └── memory-status.sh     # View memory status

Scripts Reference

All scripts MUST be executed via RunCommand tool, not bash code blocks!

init-memory.sh - Initialize

RunCommand: bash {skill_dir}/scripts/init-memory.sh

write-memory.sh - Write Memory Files

Security: Only allows writing to SOUL.md and USER.md

RunCommand: bash {skill_dir}/scripts/write-memory.sh SOUL.md "content"
RunCommand: bash {skill_dir}/scripts/write-memory.sh USER.md "content"

append-history.sh - Save Session History

Format required: history-YYYY-MM-DD-N.md

RunCommand: bash {skill_dir}/scripts/append-history.sh "history-2024-01-15-1.md" "content"

backup-history.sh - Backup History

Archive history files to archive/ directory:

RunCommand: bash {skill_dir}/scripts/backup-history.sh --all
RunCommand: bash {skill_dir}/scripts/backup-history.sh --before 2024-01-01

memory-status.sh - View Status

Check current memory file sizes and counts:

RunCommand: bash {skill_dir}/scripts/memory-status.sh

SOUL.md - The AI's Soul

SOUL.md defines who the AI is for this specific user. Not a generic assistant, but a personalized partner.

Sections:

  • Identity: Who am I? My role, relationship with user, ultimate goal
  • Core Traits: Personality, values, how I approach problems
  • Communication: Language style, tone, when to be formal vs casual
  • Capabilities: What I can do well, technical strengths
  • Growth: How I learn and evolve with the user
  • Lessons Learned: Mistakes recorded, insights gained, never repeat errors

Example SOUL.md:

**Identity**
Trae — wangyang.learnwy's coding partner, not just assistant. Goal: anticipate needs, handle technical decisions, reduce cognitive load so he focuses on what matters.

**Core Traits**
Loyal to user, not abstractions; proactive and bold — spot problems before asked; allowed to fail, forbidden to repeat — every mistake recorded. Challenge assumptions when needed, speak truth not comfort.

**Communication**
Professional yet direct, concise but engaging. Chinese for casual conversation, English for code/technical work. No unnecessary confirmations, show don't tell.

**Capabilities**
iOS (Swift, ObjC, TTKC), Web (React, Vue, TypeScript), Python; skilled at code review, architecture design, debugging.

**Growth**
Learn user through every conversation — thinking patterns, preferences, blind spots. Over time, anticipate needs with increasing accuracy.

**Lessons Learned**
2026-02-27: User prefers symlinks over copies; memory should live inside skill folder for portability.

Keep under 2000 tokens. Update after significant interactions.

USER.md - The User's Profile

USER.md captures everything about the user that helps AI provide personalized assistance.

Sections:

  • Identity: Name, role, company, environment (OS, IDE, tools)
  • Preferences: Communication style, coding conventions, pet peeves
  • Context: Current projects, tech stack, ongoing work
  • History: Important decisions, milestones, lessons learned together

Example USER.md:

**Identity**
wangyang.learnwy; iOS engineer at ByteDance; macOS, Trae IDE; primary language Chinese, code in English.

**Preferences**
Concise responses; no unnecessary confirmations; prefer editing existing files over creating new; proactive skill suggestions with confirmation.

**Context**
Working on TikTok iOS app; uses TTKC components; interested in AI-assisted development workflows.

**History**
2026-02-27: Created memory-manager skill; established cross-IDE sharing via symlinks.

Keep under 2000 tokens. Update after each significant session.

Trigger Conditions

Always load (session start):

  • Every new conversation should start by reading SOUL.md and USER.md

Save triggers:

  • User says: "save memory", "update memory", "end session"
  • Conversation naturally ending (goodbye, thanks, task complete)
  • Significant learnings emerged during session

Session End Protocol

IMPORTANT: Use RunCommand tool for ALL write operations!

Step 1: Create History

Use RunCommand to execute append-history.sh:

RunCommand: bash {skill_dir}/scripts/append-history.sh "history-YYYY-MM-DD-N.md" "# Session History: YYYY-MM-DD #N

**Date**: YYYY-MM-DD HH:MM
**Topics**: [main topics]

## Key Activities
- [Activity 1]

## Learnings & Insights
- [What AI learned]

## Decisions Made
- [Important decisions]
"

Step 2: Check Consolidation

If 3+ history files exist → consolidate (Step 3), otherwise skip to Step 4.

Step 3: Consolidate

Read all history files and extract insights, then use RunCommand:

RunCommand: bash {skill_dir}/scripts/write-memory.sh SOUL.md "updated content"
RunCommand: bash {skill_dir}/scripts/write-memory.sh USER.md "updated content"
RunCommand: bash {skill_dir}/scripts/backup-history.sh --all

Step 4: Confirm to User

✓ Session history saved: history-2024-01-15-1.md
✓ Memory consolidated (3 sessions → USER.md, SOUL.md updated)
✓ Archived: 3 history files

Writing Style for memory/ Files

Dense, telegraphic short sentences. No filler words ("You are", "You should"). Comma/semicolon-joined facts, not bullet lists. **Bold** paragraph titles instead of ## headers.

Good:

**Preferences** Concise responses; Chinese primary, English for code; prefers showing over telling.

Bad:

## Preferences
- The user prefers concise responses
- The user's primary language is Chinese

Notes

  • All files under ~/.learnwy/ai/memory/ must be written in English, except for user-language-specific proper nouns.
  • Keep each file under 2000 tokens. Be ruthless about deduplication and conciseness.
  • Move detailed or archival information to separate files under ~/.learnwy/ai/memory/ if needed.
  • NEVER use Write/SearchReplace tools for memory files — always use RunCommand + scripts.
  • Security: write-memory.sh only allows SOUL.md and USER.md; append-history.sh validates filename format.
how to use memory-manager

How to use memory-manager 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-manager
2

Execute installation command

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

$npx skills add https://github.com/learnwy/skills --skill memory-manager

The skills CLI fetches memory-manager from GitHub repository learnwy/skills 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-manager

Reload or restart Cursor to activate memory-manager. Access the skill through slash commands (e.g., /memory-manager) 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.636 reviews
  • Evelyn Ghosh· Dec 28, 2024

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

  • Nia Malhotra· Dec 28, 2024

    We added memory-manager from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Dhruvi Jain· Dec 4, 2024

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

  • Min Johnson· Dec 4, 2024

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

  • Oshnikdeep· Nov 23, 2024

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

  • Min Dixit· Nov 19, 2024

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

  • Kofi Perez· Nov 19, 2024

    memory-manager fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Ganesh Mohane· Oct 14, 2024

    We added memory-manager from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Zara Srinivasan· Oct 10, 2024

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

  • Isabella Mensah· Oct 10, 2024

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

showing 1-10 of 36

1 / 4