alive-prune

Identify and propose weekly maintenance actions for walnut logs, insights, and bundles.

124|7|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/alivecontext/alive --skill alive-prune
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: alive-prune
Source: https://github.com/alivecontext/alive/tree/main/hermes/cron-templates/alive-prune
Command: npx skills add https://github.com/alivecontext/alive --skill alive-prune

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly prune helps maintain walnut knowledge bases by proposing maintenance actions to keep logs tidy, insights relevant, and bundles current.

Core Features & Use Cases

  • Schedules weekly reviews of each walnut's log and insights to surface candidates for synthesis or archiving.
  • Suggests concrete actions to maintain readability, relevance, and historical integrity of entries.
  • Use Case: A maintainer runs the weekly prune to receive a prioritized list of actions for stale logs, unreferenced insights, and draft bundles.

Quick Start

Run the weekly prune job to review all walnuts and generate actionable maintenance recommendations.

Frequently Asked Questions about alive-prune

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate weekly log maintenance and prune stale insights for walnuts?

Weekly log maintenance for walnuts is automated by a scheduled prune job that scans all walnuts weekly to detect oversized logs and stale insights, then outputs non-destructive recommendations for review. It validates inputs and respects draft statuses before presenting actions.

What is the best way to identify stale bundles and oversized logs across multiple walnuts?

Identifying stale bundles and oversized logs across multiple walnuts is handled by a weekly review process that evaluates each walnut's entries to surface candidates for archiving or synthesis, presenting a prioritized list of maintenance actions to keep knowledge bases healthy.

Can I use a scheduled prune job to suggest maintenance actions without deleting data?

A scheduled prune job suggests maintenance actions without deleting data by operating non-destructively, proposing guided actions for review rather than executing them. It validates all inputs and respects draft statuses to ensure historical integrity of logs and insights.

Does the weekly prune process support draft statuses and validate inputs before recommending actions?

The weekly prune process supports draft statuses and validates inputs before recommending actions. It respects draft statuses to avoid premature archiving and validates all input data to ensure maintenance recommendations are accurate and safe for each walnut's logs and insights.

When do I need to run a prune job for walnut logs and insights?

You need to run a prune job for walnut logs and insights when maintenance is required to keep entries current and readable. The weekly schedule detects oversized logs, unreferenced insights, and stale bundles, surfacing them as actionable candidates for synthesis or archiving.