Scaffold a new walnut -- venture, experiment, person, life area, project
Scanned 5/27/2026
Install via CLI
openskills install alivecontext/alive---
name: alive-create
description: Scaffold a new walnut -- venture, experiment, person, life area, project
version: 1.0.0
author: ALIVE Context System
license: MIT
toolsets:
- terminal
- file
triggers:
- "create walnut"
- "new walnut"
- "new project"
- "new experiment"
- "new person"
metadata:
hermes:
tags: [ALIVE, context, create, walnut]
---
# Create Walnut
Something new is emerging. It needs its own walnut.
## Ask
```
What kind of walnut?
1. Venture (04_Ventures/) -- revenue intent
2. Experiment (05_Experiments/) -- testing grounds
3. Person (02_Life/people/) -- someone entering the orbit
4. Life area (02_Life/) -- personal goal or domain
5. Project (nested under existing walnut)
```
Then ask:
- **Name:** kebab-case (e.g., `nova-station`)
- **Goal:** one sentence
- **Rhythm:** daily / weekly / biweekly / monthly
## Scaffold
Create via terminal:
```bash
WALNUT_PATH="$ALIVE_WORLD_ROOT/[domain]/[name]"
mkdir -p "$WALNUT_PATH/_kernel"
```
Write three kernel files:
### key.md
```markdown
---
type: [venture/experiment/person/life/project]
goal: [one sentence]
created: [today]
rhythm: [rhythm]
people: []
tags: []
links: []
---
[Brief description of what this walnut is about.]
```
### log.md
```markdown
---
walnut: [name]
created: [today]
last-entry: [today]
entry-count: 1
summary: Walnut created.
---
## [today] -- squirrel:[session_id]
**Type:** creation
Walnut created. [Goal]. [Any initial context from conversation.]
signed: squirrel:[session_id]
```
### insights.md
```markdown
---
walnut: [name]
updated: [today]
squirrel: [session_id]
sections: []
---
```
### tasks.json + completed.json
```bash
echo '{"tasks": []}' > "$WALNUT_PATH/_kernel/tasks.json"
echo '{"completed": []}' > "$WALNUT_PATH/_kernel/completed.json"
```
### Run projection
```bash
python3 "$ALIVE_WORLD_ROOT/.alive/scripts/project.py" --walnut "[relative_path]"
```
## After Creation
- If this walnut is a sub-walnut, add `parent: [[parent]]` to key.md
- Add `[[name]]` to parent's key.md links
- Offer to create the first bundle
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.
Run a single Terminal-Bench problem through Paperclip in a bounded, human-in-the-loop improvement cycle until the smoke passes, the board rejects the next fix, the iteration budget is exhausted, or a real blocker is named. Each iteration runs a bounded smoke against an isolated Paperclip App worktree, captures artifacts, diagnoses the exact stop point with `/diagnose-why-work-stopped`, requests board confirmation before any product fix, then reruns against the same worktree. Use whenever an i...