recall-promote
npx machina-cli add skill Speedy0000007/claude-tandem/recall-promote --openclawRecall Promote
Review ~/.tandem/state/recurrence.json and the project MEMORY.md.
For each theme with count >= 3:
- Check if MEMORY.md already covers it
- If not, draft a [P1] entry with (observed: first_seen_date) capturing the theme's meaning
- Present proposed entries for user approval
- After approval, append to MEMORY.md
Output format
For each theme that needs promotion:
Theme: <slug> (count: N, first seen: YYYY-MM-DD)
Status: [already covered | needs promotion]
Proposed entry: [P1] <description> (observed: YYYY-MM-DD)
If all themes are already covered, report: "All recurring themes are represented in MEMORY.md."
Notes
- Only promote themes, never demote existing [P1] entries
- Use the theme slug's natural language form in the entry (e.g., "error-handling" becomes "error handling")
- The (observed: date) should use the theme's first_seen date from recurrence.json
Source
git clone https://github.com/Speedy0000007/claude-tandem/blob/main/plugins/tandem/skills/recall-promote/SKILL.mdView on GitHub Overview
Recall Promote identifies recurring themes from recurrence data and flags those that aren’t yet captured in MEMORY.md. It drafts concise P1 entries for user review, helping convert patterns into permanent knowledge.
How This Skill Works
The skill reviews ~/.tandem/state/recurrence.json and the project MEMORY.md for themes with count >= 3. For each theme, it checks if MEMORY.md already covers it; if not, it drafts a [P1] entry describing the theme’s meaning and observed first_seen_date, then presents the proposal for user approval. Once approved, it appends the new entry to MEMORY.md.
When to Use It
- You notice a theme recurring across multiple conversations or logs (count >= 3).
- You want to convert user-reported recurring issues into permanent knowledge entries.
- A new domain theme emerges repeatedly and deserves a stable definition.
- You’re building onboarding content and want persistent themes documented.
- You’re preparing a release note or knowledge base update that includes high-priority recurring topics.
Quick Start
- Step 1: Review ~/.tandem/state/recurrence.json and MEMORY.md to identify themes with count >= 3.
- Step 2: For each theme not covered by MEMORY.md, draft a [P1] entry capturing its meaning and observed first_seen_date.
- Step 3: Present the proposed entries to the user for approval and, after consent, append them to MEMORY.md.
Best Practices
- Verify the theme count is at least 3 before proposing promotion.
- Check MEMORY.md to ensure the theme isn’t already covered.
- Convert the theme slug to a natural language title (e.g., 'error-handling' → 'error handling').
- Record the first_seen_date from recurrence.json as the observation timestamp.
- Only draft P1 entries and require explicit approval before appending.
Example Use Cases
- Recurring theme 'timeout handling' reaches count 4 and is promoted after confirming MEMORY.md lacks an entry.
- Theme 'api rate limits' hits count 3 and becomes a proposed P1 entry.
- Frequent 'data serialization' issue is identified and prepared as a P1 memory draft.
- Repeated 'authentication retry' observations lead to a new MEMORY.md entry.
- Several mentions of 'network flakiness' trigger a P1 draft for durable memory.
