alive-project

Regenerate now.json projections for all walnuts from existing sources.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Regenerates now.json projections for all walnuts mechanically, enabling up-to-date world state without manual reruns or approvals.

Core Features & Use Cases

  • Automated batch projections: computes now.json for every walnut from existing sources without human input.
  • Deterministic workflow: uses fixed scripts to produce consistent updates and a refreshed world index.
  • Use Case: When you need nightly or on-demand projections refreshed across all walnuts without prompting.

Quick Start

Run the autonomous cron to regenerate now.json projections for all walnuts.

Frequently Asked Questions about alive-project

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

FAQPage Schema
How do I automate batch regeneration of now.json projections for multiple walnuts?

Automate batch regeneration of now.json projections by running a cron job that mechanically computes updates for all walnuts from existing sources without human approval. This process refreshes the world index and every walnut's now.json file autonomously.

What sources are required to regenerate now.json projections for walnuts?

Regenerating now.json projections requires reading existing sources including log.md, bundle manifests, and tasks.json. The Skill processes these source files and runs Python scripts to compute updated projections and rebuild the world index.

Can I refresh world state projections across all walnuts without manual approval?

Yes, you can refresh world state projections across all walnuts without manual reruns or approvals. The autonomous workflow uses fixed scripts to produce deterministic now.json updates and a refreshed world index on demand or via nightly cron.

When do I need batch processing for now.json projections in world management?

You need batch processing for now.json projections when maintaining up-to-date world state across many walnuts. It is required for nightly or on-demand projection refreshes where manual reruns would be impractical or cause stale state.

What is the difference between autonomous cron batch projection and manual now.json updates?

Autonomous cron batch projection mechanically regenerates now.json for all walnuts from existing sources using fixed scripts, ensuring deterministic updates without human input. Manual updates require individual reruns and approvals, causing potential state inconsistencies across walnuts.