alive-health

Flags non-archive walnuts overdue on configured cadence using timestamp data from _kernel/now.json and _kernel/key.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flag walnuts that are past their rhythm so the system can alert and address aging walnuts before they impact performance.

Core Features & Use Cases

  • Monitors walnuts against their rhythm using _kernel/key.md rhythm and _kernel/now.json updated timestamps.
  • Generates health signals: active, quiet, waiting; and outputs a concise health report.
  • Skips archives and inbox walnuts and excludes people walnuts; suitable for automated maintenance workflows.

Quick Start

Configure the cron using the provided schedule, then run the job to flag overdue walnuts on the next cycle.

Frequently Asked Questions about alive-health

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

FAQPage Schema
How do I automate health checks to flag walnuts past their rhythm?

Automate walnut rhythm health checks by comparing last update timestamps from _kernel/now.json against configured cadence values in _kernel/key.md, generating a health report with categories like active, quiet, and waiting.

What is a walnut rhythm health check and how does it work?

A walnut rhythm health check compares last update timestamps to configured cadence values to flag overdue walnuts. It reads rhythm values from _kernel/key.md and updated times from _kernel/now.json to output a categorized health report.

How do I schedule automated monitoring for walnut health on a cron?

Schedule walnut health monitoring using the cron-based schedule defined in the skill metadata. Configure the cron, run the job, and overdue walnuts will be flagged on the next automated cycle.

Does walnut rhythm monitoring check archives and inbox items?

Walnut rhythm monitoring skips archives and inbox walnuts, and it excludes people walnuts entirely. It only checks non-archive walnuts to guide attention toward active maintenance workflows.

What do the active, quiet, and waiting categories mean in a walnut health report?

Active, quiet, and waiting are health signals in the walnut health report that categorize walnuts based on their rhythm status. These categories guide attention toward overdue items that need maintenance.

Can I use cron scheduling for walnut health checks without additional dependencies?

Yes, walnut health checks support a cron-based schedule defined in the skill metadata with no external dependencies required. Configure the schedule and run the job to flag overdue walnuts automatically.