How do I install the Archive skill?

Run npx skillmds@latest add luokai0/archive in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Archive safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Archive?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Archive free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Archive?

luokai0 (@luokai0) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Archive by luokai0 — Agent Skill

Name: Archive
Rating: 4.5 (4 reviews)
Author: luokai0

Archive Skill

Capture, index, and reuse project knowledge across sessions.

When to Archive

After completing a significant task (deploy, migration, major feature)
After resolving a tricky debugging session
When the user says "archive this"
After any multi-step process with learnings worth preserving

When to Consult Archives

Before debugging infrastructure, deploy, or CI issues
Before repeating a process done in a past session
When encountering an error that may have been solved before

Search: grep -ri "keyword" .archive/ Index: .archive/MEMORY.md

Archive Workflow

Read .archive/MEMORY.md — check for related existing archives
Create .archive/YYYY-MM-DD/ directory if needed
Write markdown file with YAML frontmatter (see references/TEMPLATE.md)
Update .archive/MEMORY.md: add one-line entry under the right category
If related archives exist, add related field in frontmatter

Lookup Workflow

Read .archive/MEMORY.md to find relevant entries
Read the specific archive file for detailed context
Apply learnings to current task

Rules

.archive/ must be in .gitignore — local-only notes
Keep entries concise but reproducible
Focus on problems, fixes, and exact commands
Always update MEMORY.md after creating an archive
Use descriptive filenames (e.g., cloudwatch-logging.md not session.md)
Include YAML frontmatter with tags, category, and optional related

---name: archivedescription: Archive session learnings, debugging solutions, and deployment logs to .archive/yyyy-mm-dd/ as indexed markdown with searchable tags. Use when completing a significant task, resolving a tricky bug, deploying, or when the user says "archive this". Maintains .archive/MEMORY.md index for cross-session knowledge reuse.---# Archive SkillCapture, index, and reuse project knowledge across sessions.## When to Archive- After completing a significant task (deploy, migration, major feature)- After resolving a tricky debugging session- When the user says "archive this"- After any multi-step process with learnings worth preserving## When to Consult Archives- Before debugging infrastructure, deploy, or CI issues- Before repeating a process done in a past session- When encountering an error that may have been solved before**Search**: `grep -ri "keyword" .archive/`**Index**: `.archive/MEMORY.md`## Archive Workflow1. Read `.archive/MEMORY.md` — check for related existing archives2. Create `.archive/YYYY-MM-DD/` directory if needed3. Write markdown file with YAML frontmatter (see `references/TEMPLATE.md`)4. **Update `.archive/MEMORY.md`**: add one-line entry under the right category5. If related archives exist, add `related` field in frontmatter## Lookup Workflow1. Read `.archive/MEMORY.md` to find relevant entries2. Read the specific archive file for detailed context3. Apply learnings to current task## Categories- **infrastructure** — AWS, ECS, IAM, networking, secrets, CloudWatch- **release** — TestFlight, versioning, Git Flow, CHANGELOG- **debugging** — Bug fixes, error resolution, gotchas- **feature** — Feature design, implementation notes- **design** — UI/UX, icons, visual design## Rules- `.archive/` must be in `.gitignore` — local-only notes- Keep entries concise but reproducible- Focus on **problems, fixes, and exact commands**- Always update MEMORY.md after creating an archive- Use descriptive filenames (e.g., `cloudwatch-logging.md` not `session.md`)- Include YAML frontmatter with `tags`, `category`, and optional `related`

Frequently asked questions

Archive

File contents