catalan-adobe/memory-triage
Review Claude Code auto memory accumulated during a task and promote valuable findings to shared project config (CLAUDE.md, .claude/rules/, or global CLAUDE.md). Use this skill when finishing a branch, completing a task, wrapping up work, or anytime you want to review what Claude learned and decide what the team should know. Also use when the Stop hook reminds you about pending memory entries. Triggers on "triage memory", "review memory", "promote memory", "memory triage", "what did we learn", "clean up memory", "share learnings", "anything worth keeping", or when the user asks about knowledge accumulated during a session.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly articulates what the skill does (review and promote Claude Code auto memory to shared configs), when to use it (task completion, branch finishing, explicit memory-related requests), and includes comprehensive trigger terms. The description uses proper third-person voice and provides enough specificity to distinguish it from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Review Claude Code auto memory', 'promote valuable findings to shared project config', and specifies exact destinations (CLAUDE.md, .claude/rules/, global CLAUDE.md). | 3 / 3 |
Completeness | Clearly answers both what (review auto memory and promote to shared config) and when (explicit 'Use this skill when...' clause with multiple scenarios plus 'Triggers on...' with specific phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'triage memory', 'review memory', 'promote memory', 'what did we learn', 'clean up memory', 'share learnings', 'anything worth keeping', plus contextual triggers like 'finishing a branch' and 'completing a task'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on Claude Code's auto memory feature and memory triage workflow. The specific terminology ('auto memory', 'promote', 'Stop hook', 'pending memory entries') creates clear boundaries unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that demonstrates strong technical writing. It provides a clear, actionable workflow for memory triage with appropriate validation steps, handles edge cases explicitly, and uses progressive disclosure effectively by referencing detailed examples in separate files. The Important Notes section adds valuable constraints without bloating the main workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, assuming Claude's competence with file operations, git commands, and markdown parsing. No unnecessary explanations of basic concepts; every section serves a clear purpose. | 3 / 3 |
Actionability | Provides concrete, executable guidance: specific shell commands for path resolution, exact file paths, clear encoding algorithm, and specific patterns for secret detection. The workflow is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence with explicit validation checkpoints (Step 1 has early exit, Step 3 has redaction before presentation, Step 5 has read-before-write). Includes feedback loops for user decisions and batch operation support. | 3 / 3 |
Progressive Disclosure | Well-structured overview with appropriate references to external files for detailed examples (CLASSIFICATION.md, OUTPUT-FORMATS.md). References are one level deep and clearly signaled with descriptive link text. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents