archive-curator
SolidUSE WHEN the user asks to organize, clean up, audit, or restructure their personal archive, or asks to complete gaps in the archive-root CLAUDE.md profile. Scans first, proposes changes, requires confirmation before archive mutations, and updates CLAUDE.md conversationally.
Install
Quality Score: 80/100
Skill Content
Details
- Author
- hesorchen
- Repository
- hesorchen/muselab
- Created
- 2 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
archive
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-strategy
Design the archive layer that keeps current workspaces lean without losing history — what moves, when, to where, findable-by-search, with the project-close ritual that makes archiving automatic instead of aspirational. Use when asked set up an archiving system, our workspace is drowning in old projects, when should things get archived, or make history findable without cluttering today. Produces the archive triggers, the destination structure, the findability rules, and the close-out ritual.
curate
Power-user audit of Wenlan's pending surfaces: accept or dismiss pending revisions (conflicts/merges), or audit unconfirmed captures. Most users want `/brief` for revisions; that handles the daily flow. Use `/curate` only for explicit deep-walk audits after bulk imports, or to walk the full queue rather than the top 3 shown in /brief. Invoked as `/curate captures` or `/curate revisions`.