Load an ALIVE walnut -- read kernel files, show current state, surface one observation, ask what to work on
Scanned 5/27/2026
Install via CLI
openskills install alivecontext/alive---
name: alive-load
description: Load an ALIVE walnut -- read kernel files, show current state, surface one observation, ask what to work on
version: 1.0.0
author: ALIVE Context System
license: MIT
toolsets:
- terminal
- file
triggers:
- "load walnut"
- "open walnut"
- "what's happening with"
- "check on"
- "let's work on"
metadata:
hermes:
tags: [ALIVE, context, walnut, load]
---
# Load Walnut
Load a walnut's context. Read the brief pack, resolve people, surface one observation, ask what to work on.
## If No Walnut Named
List available walnuts grouped by domain. Use terminal to run:
```bash
find "$ALIVE_WORLD_ROOT" -name "key.md" -path "*/_kernel/*" | grep -v "01_Archive" | sort
```
Show as a numbered list. Let the user pick.
## Brief Pack (3 files)
Read these three files for the named walnut. Nothing else at this stage.
1. `_kernel/key.md` -- full (identity, people, links, rhythm)
2. `_kernel/now.json` -- full (phase, bundles, tasks, sessions, blockers)
3. `_kernel/insights.md` -- first 20 lines only (frontmatter, section names)
Show what you read:
```
> key.md [walnut name] -- [type], [rhythm], [N] people
> now.json Phase: [phase]. Urgent: [N] / Active: [N]. Bundles: [N] active.
> insights.md [N] domain knowledge sections
```
## Spotted
One observation grounded in what you just read. A stale blocker, an urgent task that has been sitting, a bundle with no recent sessions. If nothing genuine, skip it.
## Then Ask
```
[walnut name]
Goal: [from key.md]
Phase: [from now.json]
Bundle: [active bundle name] ([status])
What are you working on?
1. Continue active bundle
2. Start new
3. Go deeper (log, linked walnuts)
4. Just chat
```
If no active bundle exists, drop option 1 and renumber so the menu is `1. Start new 2. Go deeper 3. Just chat`.
## During Work
- Stash decisions, tasks, notes in conversation
- Watch for people updates, bundle fits, capturable content
- When another walnut is mentioned, ask before loading it
No comments yet. Be the first to comment!
Playbook for creating and editing uCoz landing pages via MCP tools (`templates_tool`, `ftp_tool`, `modules_tool`). Use for tasks such as: "build a landing page", "update the homepage as a landing page", "create a promo page on the homepage", "add a lead form / menu / SEO to the homepage". Homepage: `page_list`, `page_get`; first publish — `page_update` with full `page_tmpl`; HTML edits after generation — `patch_template` (module_id=2, template_id=1), not `update_template`. Activate the mail f...
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Instantly.ai cold email outreach API - manage campaigns, leads, accounts, and analytics. Use for cold email automation, lead management, campaign creation/monitoring, and email account warmup.
Use when an operation issue asks you to ingest a captured source from `raw/` into the LLM Wiki, or when the user explicitly says "ingest <slug>". The issue body will name a file under `raw/` (e.g. `raw/karpathy-llm-wiki.md`) and ask for durable wiki pages. Do not invoke this skill for Paperclip activity bundles — those use `paperclip-distill` instead.