Create, manage, and graduate bundles -- the unit of focused work within a walnut
Scanned 5/27/2026
Install via CLI
openskills install alivecontext/alive---
name: alive-bundle
description: Create, manage, and graduate bundles -- the unit of focused work within a walnut
version: 1.0.0
author: ALIVE Context System
license: MIT
toolsets:
- terminal
- file
triggers:
- "create bundle"
- "new bundle"
- "bundle"
- "start a bundle"
- "graduate bundle"
metadata:
hermes:
tags: [ALIVE, context, bundle, work]
---
# Bundle Management
Bundles are self-contained units of work inside a walnut. Any folder with a `context.manifest.yaml` is a bundle.
## Create
```
What's this bundle for?
1. Outcome -- produces something specific (deliverable, has a done state)
2. Evergreen -- accumulates context over time (collection, ongoing)
```
Ask for:
- **Name:** kebab-case (e.g., `website-rebuild`)
- **Goal:** one sentence describing the deliverable or collection
Scaffold:
```bash
BUNDLE_PATH="$WALNUT_PATH/[bundle-name]"
mkdir -p "$BUNDLE_PATH/raw"
```
Write `context.manifest.yaml`:
```yaml
goal: "[goal]"
status: draft
version: v0.1
sensitivity: private
pii: false
created: [today]
updated: [today]
context: |
Bundle created. [Initial context from conversation.]
sources: []
linked_bundles: []
tags: []
squirrels: [[session_id]]
active_sessions:
- session: [session_id]
engine: hermes-agent
started: [now]
working_on: "Initial setup"
```
Write `tasks.json`:
```json
{"tasks": []}
```
## Status Lifecycle
```
draft -> prototype -> published -> done
```
- **draft** -- actively worked on, markdown only
- **prototype** -- has a visual (HTML), maybe shared with 1-2 people
- **published** -- shared externally
- **done** -- outputs complete, bundle stays as historical record
## Graduate
When a `*-v1.md` or `*-v1.html` file exists:
```
v1 exists. Graduate this bundle?
1. Yes, mark as done
2. Yes, mark as published
3. Not yet
```
Flip `status:` in manifest. Bundle folder stays where it is.
## Routing
When content arrives:
- Same goal -> same bundle
- Related but different goal -> new bundle, link to existing
- Ambiguous -> ask once
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...