create-memory

Writes persistent memory files as concise rule cards with strict frontmatter and formatting constraints.

Updated Sep 1, 2026
One-click install
npx skills add https://github.com/jpmoya/claude-agents --skill create-memory-jpmoya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-memory
Source: https://github.com/jpmoya/claude-agents/tree/main/skills/create-memory
Command: npx skills add https://github.com/jpmoya/claude-agents --skill create-memory-jpmoya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Memory files often become bloated session logs with inconsistent formats, making them hard to scan and reuse. This Skill enforces a single strict template so every memory is a short, imperative rule card that stays useful across sessions. ## Core Features & Use Cases - Strict Template Enforcement: Every memory file uses only name and type frontmatter with imperative bullet points, no headings or paragraphs. - Deduplication Guidance: Directs updates to existing memory files covering a topic instead of creating duplicates. - Index Maintenance: Requires adding a one-line entry to MEMORY.md after each write so memories stay discoverable. - Use Case: When a user says "remember this: never calculate Casa Verde prices manually", the Skill produces a kebab-case file like feedback-never-calculate-prices.md with typed frontmatter and under-100-word imperative bullets. ## Quick Start Ask the assistant to remember a rule or preference, and it will create a properly formatted memory file and index it in MEMORY.md.

Frequently Asked Questions about create-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save a persistent memory for an AI assistant?

Ask the assistant to remember the rule, and it writes a markdown file with name and type frontmatter plus imperative bullets. The file is then indexed with a one-line entry in MEMORY.md for discovery.

What format should an AI memory file use?

Memory files use frontmatter with only a kebab-case name and a type of user, feedback, project, or reference. The body contains imperative bullets under 100 words with no headings, paragraphs, dates, or session stories.

Can I update an existing memory instead of creating a new one?

Yes, the rule is one fact per file, so you update the existing file that covers the topic rather than adding a duplicate. This keeps the memory directory free of overlapping entries.

What are the limitations of rule-card memory files?

They cannot store session histories, bug narratives, timestamps, or reasoning context, since only rules, facts, and steps are allowed. Anything needing narrative detail belongs elsewhere, not in the memory directory.

Why does my memory file get rejected for extra frontmatter fields?

The template permits only name and type in frontmatter. Fields like description, originSessionId, metadata, or timestamps are explicitly disallowed to keep memory cards uniform and scannable.