Weekly -- suggest log entries for chapter synthesis, flag stale insights
Scanned 5/27/2026
Install to Claude Code
npx -y skills add alivecontext/alive --skill alive-prune --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Alive Prune?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/alivecontext-alive-prune)More formats (shields.io, HTML) on the badges page.
---
name: alive-prune
description: Weekly -- suggest log entries for chapter synthesis, flag stale insights
version: 1.0.0
author: ALIVE Context System
license: MIT
toolsets:
- terminal
- file
metadata:
hermes:
tags: [ALIVE, cron, pruning, maintenance]
cron_schedule: "0 3 * * 0"
cron_deliver: "telegram"
---
# Weekly Prune
Suggest maintenance actions for log and insight hygiene.
## Process
### Log Chapter Synthesis
For each walnut, check `_kernel/log.md`:
- Count entries (## headings after frontmatter)
- If 50+ entries, suggest chapter synthesis
```
[walnut] log has [N] entries.
Suggest synthesizing older entries into _kernel/history/chapter-[nn].md?
1. Yes, synthesize
2. Not yet
```
### Stale Insights
For each walnut, check `_kernel/insights.md`:
- Read each section
- Flag sections not referenced in recent log entries (last 30 days)
```
[walnut] insights:
"[section name]" -- not referenced in 45 days
1. Keep (still relevant)
2. Archive (move to bottom)
3. Remove
```
### Stale Bundles
Find bundles in draft status older than 30 days:
```
[walnut]/[bundle] -- draft for 42 days
1. Advance (prototype)
2. Archive (done)
3. Kill (delete)
4. Leave
```
## Output
If nothing needs attention: `[SILENT]`
If issues found, present one category at a time. Keep actionable.
## Rules
- This is weekly, not urgent. Present calmly.
- Never auto-prune. Always suggest and wait.
- Chapter synthesis preserves full entries -- it's summarization, not deletion.
No comments yet. Be the first to comment!