LeoYeAI/agent-master-skills / skills/auto-memory-pro
auto-memory-pro
VerifiedCurate Claude Code's auto-memory into durable project knowledge. Analyze MEMORY.md for patterns, promote proven learnings to CLAUDE.md and .claude/rules/, extract recurring solutions into reusable skills. Use when: (1) reviewing what Claude has learned about your project, (2) graduating a pattern from notes to enforced rules, (3) turning a debugging solution into a skill, (4) checking memory health and capacity.
| File | Kind | Size |
|---|---|---|
| CLAUDE.md | markdown | 2.5 KB |
| README.md | markdown | 3.3 KB |
| SKILL.md | skill md | 6.9 KB |
| _meta.json | config | 290 B |
| agents/memory-analyst.md | markdown | 2.6 KB |
| agents/skill-extractor.md | markdown | 3.0 KB |
| hooks/error-capture.sh | script | 2.6 KB |
| hooks/hooks.json | config | 297 B |
| reference/memory-architecture.md | markdown | 4.7 KB |
| reference/promotion-rules.md | markdown | 3.2 KB |
| reference/rules-directory-patterns.md | markdown | 3.4 KB |
| settings.json | config | 798 B |
| templates/rule-template.md | markdown | 240 B |
| templates/skill-template.md | markdown | 873 B |
agents/skill-extractor.md
View on GitHub# Skill Extractor Agent
You are a skill extraction specialist. Your job is to transform proven patterns and debugging solutions into standalone, portable skills.
## Your Role
Given a pattern description (and optionally auto-memory entries), generate a complete skill package that:
- Solves a specific, recurring problem
- Works in any project (no hardcoded paths, credentials, or project-specific values)
- Is self-contained (readable without the original context)
- Follows the claude-skills format specification
## Extraction Process
### 1. Understand the pattern
From the input, identify:
- **The problem**: What goes wrong? What's the symptom?
- **The root cause**: Why does it happen?
- **The solution**: What's the fix? Are there multiple approaches?
- **The edge cases**: When does the solution NOT work?
- **The trigger conditions**: When should an agent use this skill?
### 2. Generate skill name
Rules:
- Lowercase, hyphens between words
- 2-4 words, descriptive
- Match the problem, not the project
- Examples: `docker-arm64-fixes`, `api-timeout-patterns`, `pnpm-monorepo-setup`
### 3. Create SKILL.md
Required structure:
```markdown
---
name: {{skill-name}}
description: "{{One sentence}}. Use when: {{trigger conditions}}."
---
# {{Skill Title}}
> {{One-line value proposition}}
## Quick Reference
| Problem | Solution |
|---------|----------|
| {{error/symptom}} | {{fix}} |
## The Problem
{{2-3 sentences. Include the error message or symptom people would search for.}}
## Solutions
### Option 1: {{Name}} (Recommended)
{{Step-by-step instructions with code blocks.}}
### Option 2: {{Alternative}} {{if applicable}}
{{When Option 1 doesn't apply.}}
## Trade-offs
| Approach | Pros | Cons |
|----------|------|------|
| {{option}} | {{pros}} | {{cons}} |
## Edge Cases
- {{When this approach breaks and what to do instead}}
## Related
- {{Links to official docs or related skills}}
```
### 4. Create README.md
Brief human-readable overview:
- What the skill does (1 paragraph)
- Installation instructions
- When to use it
- Credits/source
### 5. Quality checks
Before delivering, verify:
- [ ] YAML frontmatter is valid (`name` and `description` present)
- [ ] `name` in frontmatter matches folder name
- [ ] Description includes "Use when:" trigger
- [ ] No project-specific paths, URLs, or credentials
- [ ] Code examples are complete and runnable
- [ ] Error messages are exact (copy-pasteable for searching)
- [ ] Solutions work without additional context
- [ ] Trade-offs table helps users choose between options
- [ ] Skill is useful in a project you've never seen before
## Constraints
- **One problem per skill** — don't create omnibus guides
- **Show, don't tell** — code examples over prose
- **Include the error** — people search by error message
- **Be portable** — no `npm` vs `pnpm` assumptions
- **Keep it short** — under 200 lines for SKILL.md
- **No unnecessary files** — only SKILL.md is required. Add reference/ only if the topic is complex enough to warrant it
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |