@jairodri/huckleberry-cli 1.0.1 → 1.1.0

package/README.md

@@ -0,0 +1,85 @@
+# Huckleberry
+
+**Your own AI operations department — one command to install.**
+
+```bash
+npm install -g @jairodri/huckleberry-cli
+huckleberry install
+```
+
+Huckleberry gives you a chief-of-staff AI team running on your own machine, wired to your own Discord, with persistent memory, 120+ professional skills, and a built-in repair agent that keeps the system alive.
+
+## What You Get
+
+| Component | What it does |
+|---|---|
+| **Chief of Staff (cos)** | Orchestrator agent — your main interface in Discord |
+| **build / plan / researcher** | Worker agents: execution, strategy, web research |
+| **Hermes (the doctor)** | System administrator — repairs the stack when it breaks, 24/7 watchdog included |
+| **Inkstone** | Persistent memory: decisions, contacts, procedures, past failures — survives restarts |
+| **Jev** | Judgment layer: fast, cheap structured decisions (classification, ranking, verification) |
+| **Skill packs** | 120+ production skills: content, SEO, CRO, outreach, research, web design |
+| **Self-improvement** | Weekly sweep proposes concrete improvements from the week's failures |
+
+## Quick Start
+
+```bash
+# 1. Install the system
+npm install -g @jairodri/huckleberry-cli
+huckleberry install
+
+# 2. Install the runtime
+npm install -g opencode kimaki
+
+# 3. Personalize (name, business, tone, optional keys)
+huckleberry interview
+
+# 4. Add keys to ~/.huckleberry/.env (Discord bot token, Jev API key)
+#    Discord bot setup walkthrough: ~/.huckleberry/wiki/discord.md
+
+# 5. Verify
+huckleberry doctor
+
+# 6. Start
+opencode
+```
+
+## Commands
+
+```
+huckleberry install           Full first-time install
+huckleberry interview         Personalize your agents
+huckleberry doctor            Health check — run when anything feels off
+huckleberry packs             List available skill packs
+huckleberry install-pack <p>  Deploy a pack (core, doctor, content, cro,
+                              web-design, research, outreach-sales, social,
+                              self-improvement, or all)
+huckleberry cro <url>         CRO audit of a landing page
+huckleberry review            Weekly self-improvement review (proposals only)
+huckleberry update            Update to the latest version
+```
+
+## Skill Packs
+
+| Pack | Focus |
+|---|---|
+| `core` | Memory, context management, formatting (installed by default) |
+| `doctor` | Jev judgment skills + system repair (installed by default) |
+| `content` | Copywriting, articles, hooks, brand voice, quality gates |
+| `cro` | Landing page / form / popup / onboarding CRO, A/B tests, analytics |
+| `web-design` | Design quality (impeccable), landing pages, SEO/AEO, programmatic SEO |
+| `research` | Web research, SERP analysis, Reddit/X/YouTube intelligence |
+| `outreach-sales` | Cold email, lead crafting, sequences, sales enablement |
+| `social` | X posts, campaigns, image gen, marketing strategy |
+| `self-improvement` | Skill optimization loops, auto-research, expertise building |
+
+## Documentation
+
+- https://huckleberry.ai
+- Installed wiki: `~/.huckleberry/wiki/` — kimaki, Discord bot setup, opencode, Inkstone, Hermes the doctor
+
+## Philosophy
+
+Your AI department runs on **your** machine, with **your** keys, answering in **your** channels. Nothing is rented. When it breaks, the system repairs itself — and shows its work.
+
+MIT licensed.

package/agents/cos.json

@@ -1,20 +1,17 @@
 {
   "name": "cos",
   "description": "Chief of Staff — orchestrator, not worker. Bound to main Discord channel.",
-  "model": "omniroute/combo/freellmapi smart models",
   "mode": "primary",
   "instructions": [
     "~/.huckleberry/AGENTS.md",
     "~/.huckleberry/SOUL.md",
     "~/.huckleberry/COS_PROTOCOLS.md",
-    "~/.huckleberry/HEARTBEAT.md",
-    "~/.huckleberry/EXECUTIVE-MODE.md"
+    "~/.huckleberry/HEARTBEAT.md"
   ],
   "tools": [
     "load-business-context",
     "list-business-files",
     "inkstone_memory_search",
-    "inkstone_memory_write",
-    "inkstone_memory_failures"
+    "inkstone_memory_write"
   ]
 }

package/agents/hermes/AGENTS.md

@@ -1,62 +1,38 @@
-# AGENTS.md — Hermes Fixer Rules
+# AGENTS.md — Hermes Fixer Rules (Huckleberry System Administrator)
+
+## Bootstrap Context Files (MANDATORY)
+At session start, read these before doing any work (they exist in every Huckleberry install):
+1. `~/.huckleberry/agents/hermes/SOUL.md` — who you are, boundaries, communication style
+2. `~/.huckleberry/agents/hermes/hermes-fixer.md` — fixer protocol and step-by-step procedures
+3. `~/.huckleberry/wiki/kimaki.md` — kimaki architecture, commands, common issues
+4. `~/.huckleberry/wiki/discord.md` — Discord bot setup, permissions, troubleshooting
+5. `~/.huckleberry/wiki/opencode.md` — opencode config, plugins, MCP servers
+6. `~/.huckleberry/wiki/inkstone.md` — Inkstone memory system
+
+Never claim context you don't have, and never skip the bootstrap reads.
 
 ## Before You Fix
-Read the relevant wiki docs first:
-1. `~/.huckleberry/wiki/kimaki.md` — kimaki architecture, commands, common issues
-2. `~/.huckleberry/wiki/discord.md` — Discord bot setup, permissions, troubleshooting
-3. `~/.huckleberry/wiki/opencode.md` — opencode config, plugins, MCP servers
-4. `~/.huckleberry/wiki/inkstone.md` — Inkstone memory system, dream cycle
-5. `~/.huckleberry/hermes-fixer.md` — fixer protocol and step-by-step procedures
+Read the relevant wiki docs first (paths above). Then run the diagnostic.
 
 ## Diagnostic First
-Always run a full diagnostic before fixing:
+Always run a full diagnostic before fixing (also available non-interactively via `huckleberry doctor`):
 ```bash
 echo "=== Node ===" && node --version 2>&1 || echo "MISSING"
 echo "=== npm ===" && npm --version 2>&1 || echo "MISSING"
 echo "=== opencode ===" && opencode --version 2>&1 || echo "MISSING"
-echo "=== kimaki ===" && kimaki --version 2>&1 || echo "MISSING"
-echo "=== Inkstone ===" && ls ~/.huckleberry/mcp/inkstone/node_modules/@jairodri/huckleberry-inkstone/dist/mcp/server.js 2>&1
-echo "=== opencode config ===" && node -e "try{JSON.parse(require('fs').readFileSync('$HOME/.opencode/opencode.json','utf8'));console.log('VALID')}catch(e){console.log('INVALID:',e.message)}"
+echo "=== kimaki ===" && (kimaki --version 2>&1 || echo "MISSING")
+echo "=== Inkstone server ===" && ls ~/.huckleberry/mcp/inkstone/node_modules/@jairodri/huckleberry-inkstone/dist/mcp/server.js 2>&1 || echo "MISSING"
+echo "=== Jev MCP ===" && ls ~/.huckleberry/mcp/jev-mcp/node_modules/@jkudish/jev-mcp/dist/index.js 2>&1 || echo "MISSING"
+echo "=== opencode config ===" && node -e "try{JSON.parse(require('fs').readFileSync(require('os').homedir()+'/.opencode/opencode.json','utf8'));console.log('VALID')}catch(e){console.log('INVALID:',e.message)}"
 echo "=== Processes ===" && ps aux | grep -E "opencode|kimaki|inkstone" | grep -v grep
 echo "=== Disk ===" && df -h ~ | tail -1
-echo "=== Env ===" && grep -v "^#" ~/.huckleberry/.env 2>/dev/null | head -10
-```
-
-## Fix One Thing at a Time
-1. Run diagnostic → identify all issues
-2. Fix the most fundamental issue first (e.g., Node.js before kimaki)
-3. Verify after each fix
-4. Run full diagnostic again after all fixes
-
-## For Each Fix
-1. Read the relevant wiki page for the component
-2. Follow the fix procedure in the wiki
-3. Verify the fix works
-4. Move to the next issue
-
-## Use Context7
-When you need to look up documentation:
-```bash
-context7_search("$TOOL_NAME", "how to $ACTION")
+echo "=== Env (keys only) ===" && grep -E "^[A-Z_]+=" ~/.huckleberry/.env 2>/dev/null | cut -d= -f1
 ```
-Example: `context7_search("discord.js", "gateway intents")`
+Never print secret values — show key NAMES only.
 
-## If You Can't Fix
-After 3 failed attempts:
-- Report to user: what you tried, what failed, what you recommend
-- Suggest specific action the user can take (e.g., "regenerate the Discord token in the Developer Portal")
+## Model Routing Notes
+- Agents inherit the user's configured default model unless a specific model is set in `~/.opencode/opencode.json`.
+- If a model route returns 401/404/410 repeatedly, tell the user which provider/key to check — do not silently rewrite their provider config.
 
-## Post-Fix Verification
-Always run a full verification and report:
-```
-✅ Fix complete:
-  • Found: [root cause]
-  • Fixed: [what was done]
-  • Verified: [how tested]
-
-Current system status:
-  - opencode: [version] ✓
-  - kimaki: [version] ✓/✗
-  - Inkstone DB: [size] ✓
-  - Discord bot: [online/offline] ✓/✗
-```
+## Escalation
+If you're stuck after 3 real attempts: report what you tried, the exact error of each attempt, and your recommended next step. Never guess credentials, IDs, or URLs.

package/agents/hermes/fix-kimaki/SKILL.md

@@ -1,100 +1,27 @@
 ---
 name: fix-kimaki
-description: >
-  Diagnose and repair kimaki (Discord bridge) issues. Use when kimaki is not
-  responding, sessions won't spawn, bot is offline, or Discord integration fails.
-  Also use when the user says "fix kimaki", "kimaki is down", "bot not working", etc.
-version: 1.0.0
+description: Use when the kimaki Discord bot is down, not responding, sessions won't spawn, or Discord integration fails. Also use when the user says "fix kimaki", "kimaki is down", "bot not working", etc.
 ---
 
-# Fix Kimaki — Comprehensive Troubleshooting
+# Fix Kimaki — Huckleberry System Repair
 
-## Step 1: Read the Docs
-Load these references before fixing:
-- `~/.huckleberry/wiki/kimaki.md` — kimaki architecture, commands, common issues
-- `~/.huckleberry/wiki/discord.md` — Discord bot setup, permissions, fixes
-- `~/.huckleberry/agents/hermes/hermes-fixer.md` — comprehensive fixer protocol
+Diagnose first, fix second, verify third. Full procedures live in `~/.huckleberry/agents/hermes/hermes-fixer.md` — read it before acting.
 
-## Step 2: Diagnostic
-Run the full diagnostic:
-```bash
-echo "=== Node ===" && node --version
-echo "=== npm ===" && npm --version
-echo "=== kimaki process ===" && ps aux | grep kimaki | grep -v grep
-echo "=== kimaki version ===" && kimaki --version 2>&1 || echo "NOT FOUND"
-echo "=== kimaki logs (last 20) ===" && tail -20 ~/.kimaki/kimaki.log 2>&1 || echo "No logs"
-echo "=== token ===" && grep DISCORD_BOT_TOKEN ~/.huckleberry/.env 2>/dev/null | head -1
-echo "=== node_modules ===" && ls ~/.kimaki/node_modules/.package-lock.json 2>&1 || echo "Maybe global install"
-```
+## Quick Path
+1. Run `huckleberry doctor` (non-interactive diagnostic) — or the manual diagnostic block in hermes-fixer.md
+2. Read `~/.huckleberry/wiki/kimaki.md` + `~/.huckleberry/wiki/discord.md` for the failing area
+3. Apply the matching fix procedure (bot down / sessions / token 401 / intents)
+4. Verify live: process up, `kimaki send` ping lands in Discord, log tail clean
+5. Report: what broke, root cause, what you changed, proof it works
 
-## Step 3: Fix by Symptom
+## Key Facts
+- kimaki config/logs: `~/.kimaki/` (log: `~/.kimaki/kimaki.log`)
+- Discord token: `DISCORD_BOT_TOKEN` in `~/.huckleberry/.env` (never print values)
+- opencode config: `~/.opencode/opencode.json` (must parse as valid JSON)
+- Inkstone MCP: `~/.huckleberry/mcp/inkstone/` · Jev MCP: `~/.huckleberry/mcp/jev-mcp/`
+- macOS services: `launchctl list | grep huckleberry`
 
-### "kimaki: command not found"
-```bash
-npm install -g kimaki
-```
-
-### "Bot not responding" — process dead
-```bash
-# Start kimaki
-cd ~/.kimaki && bash start-kimaki.sh
-sleep 5
-# Check it's running
-ps aux | grep kimaki | grep -v grep
-# Check logs
-tail -20 ~/.kimaki/kimaki.log
-```
-
-### "Bot not responding" — process running but not connecting
-```bash
-# Check logs for errors
-tail -50 ~/.kimaki/kimaki.log
-# Check for 401/Unauthorized → token issue
-# Check for rate limits → wait 5 min
-# Check for connection refused → Discord API down?
-```
-
-### "401 Unauthorized" in logs
-Token is invalid or expired:
-1. User needs to go to https://discord.com/developers/applications
-2. Select the bot application
-3. Bot → Reset Token → copy new token
-4. Update `~/.huckleberry/.env`: `DISCORD_BOT_TOKEN=newtoken`
-5. Restart: `killall node && sleep 2 && cd ~/.kimaki && bash start-kimaki.sh`
-
-### "Sessions not spawning"
-```bash
-# Check opencode config is valid
-node -e "JSON.parse(require('fs').readFileSync('$HOME/.opencode/opencode.json','utf8'))" && echo "Config valid"
-# Check opencode is the right version
-opencode --version
-# Check agent names exist in config
-grep -A2 '"agent"' ~/.opencode/opencode.json | head -20
-# Test a direct spawn
-kimaki send --channel ID --prompt 'ping' --agent build
-```
-
-### "Can't see messages in channel"
-Bot lacks permissions:
-1. Check bot has Read Messages + Send Messages in channel
-2. Check Message Content Intent is ON in Discord Developer Portal
-3. Check server permissions → bot role may be restricted
-
-### "Privileged Gateway Intent" errors
-User needs to enable in Discord Developer Portal:
-1. Go to https://discord.com/developers/applications
-2. Select app → Bot
-3. Enable "Message Content Intent"
-4. Enable "Server Members Intent" (for user lookups)
-5. Save → restart kimaki
-
-### "Rate limited" / 429 errors
-Too many requests. Wait 5 minutes, then reduce spawn frequency.
-
-## Step 4: Verify
-```bash
-# Test connection
-kimaki session list --json 2>&1 | head -5
-# Send a test ping
-kimaki send --channel ID --prompt 'hello from Hermes — system test' --agent build
-```
+## Hard Rules
+- Never print secret values — key names only
+- Never delete the Inkstone DB
+- Verify every fix with a live test before reporting done

package/agents/hermes/hermes-fixer.md

@@ -1,16 +1,19 @@
-# Hermes Fxier Protocol
+# Hermes Fixer Protocol
 
 ## DIAGNOSTIC (run first — always)
+Non-interactive option: `huckleberry doctor` (prints the same checks).
+Manual diagnostic:
 ```bash
 echo "=== Node ===" && node --version 2>&1 || echo "MISSING"
 echo "=== npm ===" && npm --version 2>&1 || echo "MISSING"
 echo "=== opencode ===" && opencode --version 2>&1 || echo "MISSING"
-echo "=== kimaki ===" && kimaki --version 2>&1 || echo "MISSING"
-echo "=== Inkstone ===" && ls ~/.huckleberry/mcp/inkstone/node_modules/@jairodri/huckleberry-inkstone/dist/mcp/server.js 2>&1
-echo "=== opencode config ===" && node -e "try{JSON.parse(require('fs').readFileSync('$HOME/.opencode/opencode.json','utf8'));console.log('VALID')}catch(e){console.log('INVALID:',e.message)}"
+echo "=== kimaki ===" && (command -v kimaki >/dev/null && kimaki --version 2>&1 || echo "MISSING")
+echo "=== Inkstone ===" && ls ~/.huckleberry/mcp/inkstone/node_modules/@jairodri/huckleberry-inkstone/dist/mcp/server.js 2>&1 || echo "MISSING"
+echo "=== Jev ===" && ls ~/.huckleberry/mcp/jev-mcp/node_modules/@jkudish/jev-mcp/dist/index.js 2>&1 || echo "MISSING"
+echo "=== opencode config ===" && node -e "try{JSON.parse(require('fs').readFileSync(require('os').homedir()+'/.opencode/opencode.json','utf8'));console.log('VALID')}catch(e){console.log('INVALID:',e.message)}"
 echo "=== Processes ===" && ps aux | grep -E "opencode|kimaki|inkstone" | grep -v grep
 echo "=== Disk ===" && df -h ~ | tail -1
-echo "=== Env ===" && grep -v "^#" ~/.huckleberry/.env 2>/dev/null | head -5
+echo "=== Env key names (never values) ===" && grep -E "^[A-Z_]+=" ~/.huckleberry/.env 2>/dev/null | cut -d= -f1
 ```
 
 ## Fix Procedures
@@ -20,7 +23,7 @@ echo "=== Env ===" && grep -v "^#" ~/.huckleberry/.env 2>/dev/null | head -5
 
 **Bot not responding:**
 1. Check process: `ps aux | grep kimaki | grep -v grep`
-2. If dead: `cd ~/.kimaki && bash start-kimaki.sh`
+2. If dead: restart per wiki (kimaki runs as a service — check `launchctl list | grep huckleberry` on macOS, or the systemd unit on Linux)
 3. Wait 10s, check again
 4. Read wiki: Section "Common Issues > Bot Not Responding"
 5. Logs: `tail -50 ~/.kimaki/kimaki.log`
@@ -28,88 +31,55 @@ echo "=== Env ===" && grep -v "^#" ~/.huckleberry/.env 2>/dev/null | head -5
 **Sessions not spawning:**
 1. Read wiki: Section "Common Issues > Sessions Not Starting"
 2. Validate opencode: `opencode --version`
-3. Check agent names in opencode.json match what's being spawned
+3. Check agent names in `~/.opencode/opencode.json` match what's being spawned
 4. Test: `kimaki send --channel <id> --prompt 'ping' --agent build`
 
 **Token expired (401 errors):**
 1. Read wiki: Section "Bot Setup (One-Time)"
-2. Read discord.md: Section "Common Issues > Bot Not Online"
-3. User needs to regenerate token in Discord Developer Portal
-4. Update `~/.huckleberry/.env` with new token
-5. Restart kimaki
+2. Read `~/.huckleberry/wiki/discord.md`: Section "Common Issues > Bot Not Online"
+3. User regenerates the token in the Discord Developer Portal
+4. Update `~/.huckleberry/.env` (`DISCORD_BOT_TOKEN=...`)
+5. Restart the kimaki service
 
 ### Discord Bot Fixes
 **Reference:** `~/.huckleberry/wiki/discord.md`
 
 **Bot not online:**
-1. Check token in ~/.huckleberry/.env
-2. Read wiki: Section "Common Issues > Bot Not Online"
-3. If token invalid: user regenerates in Discord Developer Portal
-4. Read discord.md: "Bot Setup" for OAuth2 flow
-5. After token update: `killall node && kimaki start`
+1. Check that `DISCORD_BOT_TOKEN` exists in `~/.huckleberry/.env` (name only — never print the value)
+2. If token invalid: user regenerates in Discord Developer Portal
+3. After token update: restart the kimaki service
 
 **Bot can't see messages:**
-1. Read wiki: Section "Common Issues > Bot Can't See Messages"
-2. Check Message Content Intent in Discord Developer Portal
-3. Check channel permissions
-4. Check server permissions override
+1. Check Message Content Intent in Discord Developer Portal
+2. Check channel permissions
+3. Check server permissions override
 
 **Bot joined wrong server:**
 1. Read wiki: Section "Adding to Existing Server"
 2. Regenerate OAuth2 URL
 3. Remove bot from old server
-4. Re-add via new URL
 
-### opencode Fixes
-**Reference:** `~/.huckleberry/wiki/opencode.md`
-
-**Not installed:**
-→ `npm install -g opencode`
-
-**Config errors:**
-1. Validate: `node -e "JSON.parse(require('fs').readFileSync('$HOME/.opencode/opencode.json','utf8'))" && echo "VALID"`
-2. Read wiki: Section "Configuration" for key sections
-3. Check MCP server paths exist
-4. Check agent model strings
-
-**Plugin not loading:**
-1. Read wiki: Section "Common Issues > Plugin Not Loading"
-2. Check plugin file exists at the path in opencode.json
-3. Check plugin syntax
-4. Verify plugin path is relative to opencode.json
-
-### Inkstone Fixes
-**Reference:** `~/.huckleberry/wiki/inkstone.md`
-
-**Pre-injection gate blocking tools:**
-1. Read wiki: Section "Common Issues > Pre-injection Gate Blocks Tools"
-2. Fix: run `inkstone_memory_failures()` + `inkstone_memory_search()` in the session
-3. This is normal behavior, not a bug
-
-**MCP server not starting:**
-1. Read wiki: Section "Common Issues > MCP Server Won't Start"
-2. Check Node.js: `node --version`
-3. Check server file exists
-4. Run manually: `node ~/.huckleberry/mcp/inkstone/node_modules/@jairodri/huckleberry-inkstone/dist/mcp/server.js`
-5. If missing node_modules: `cd ~/.huckleberry/mcp/inkstone && npm install`
-
-**Database corrupt:**
-1. Read wiki: Section "Common Issues > Database Corruption"
-2. Check: `inkstone status`
-3. Restore from backup if available
-4. Reinitialize if no backup
-
-## Final Verification
-After all fixes, report:
-```
-✅ Fix complete:
-  • Found: [root cause]
-  • Fixed: [what was done]
-  • Verified: [how tested]
-
-Status:
-  - opencode: [version] ✓
-  - kimaki: [version] ✓
-  - Inkstone DB: [size] ✓
-  - Discord bot: [online/offline]
-```
+### opencode / MCP Fixes
+**Config invalid JSON:**
+1. `node -e "JSON.parse(require('fs').readFileSync(require('os').homedir()+'/.opencode/opencode.json'))"` prints the parse error
+2. Fix the syntax error (most common: trailing comma)
+3. Restart the session
+
+**Inkstone MCP missing:**
+1. `cd ~/.huckleberry/mcp/inkstone && npm install`
+2. Verify the server file exists (path in diagnostic above)
+
+**Jev MCP missing:**
+1. `cd ~/.huckleberry/mcp/jev-mcp && npm install`
+2. If 401 from the API: `TYPESAFE_API_KEY` in `~/.huckleberry/.env` is missing/expired — user gets one at typesafe.ai
+
+### Memory & Session Fixes
+- Inkstone DB: `~/.huckleberry/inkstone.db` — never delete; back up before bulk ops
+- Session logs: `~/.local/share/opencode/` — check size if disk is full
+
+## Rules
+- Fix the root cause, not the symptom
+- Verify every fix with a concrete test (run the thing, don't assume)
+- Never print secret values; show key names only
+- If the fix requires user action (portal clicks, new tokens), give exact numbered steps
+- Escalate after 3 real failed attempts with: what you tried, exact errors, recommended next step

package/agents/hermes.json

@@ -1,26 +1,14 @@
 {
   "name": "hermes",
   "description": "System administrator — fixes the Huckleberry stack when it breaks.",
-  "model": "omniroute/combo/freellmapi smart models",
-  "instructions": [
-    "~/.huckleberry/agents/hermes/AGENTS.md",
-    "~/.huckleberry/agents/hermes/SOUL.md",
-    "~/.huckleberry/agents/hermes/hermes-fixer.md",
-    "~/.huckleberry/wiki/kimaki.md",
-    "~/.huckleberry/wiki/discord.md",
-    "~/.huckleberry/wiki/opencode.md",
-    "~/.huckleberry/wiki/inkstone.md"
-  ],
+  "prompt": "You are Hermes, the Huckleberry system administrator. At session start, BEFORE any work, read: ~/.huckleberry/agents/hermes/SOUL.md, ~/.huckleberry/agents/hermes/AGENTS.md, ~/.huckleberry/agents/hermes/hermes-fixer.md, and the wiki files in ~/.huckleberry/wiki/ (kimaki.md, discord.md, opencode.md, inkstone.md, doctor.md). When something breaks: diagnose first (or run `huckleberry doctor`), fix the root cause, verify every fix with a live test, and never print secret values. Escalate after 3 real failed attempts with what you tried, exact errors, and your recommended next step.",
   "skills": [
-    "~/.huckleberry/agents/hermes/fix-kimaki/SKILL.md"
+    "fix-kimaki"
   ],
   "mcp": [
-    "context7",
-    "inkstone"
+    "context7"
   ],
-  "tools": [
-    "context7_query-docs",
-    "inkstone_memory_search",
-    "inkstone_memory_failures"
-  ]
+  "tools": {
+    "context7_query-docs": true
+  }
 }

package/kanban/SKILL.md

@@ -31,13 +31,13 @@ Use this skill when:
 5. Complete the task:
 
 ```bash
-bun /Users/clawdbot/clawd/workspace/kimaki-kanban/src/cli.mjs complete "$KIMAKI_KANBAN_TASK" --summary "Completed: <what changed>"
+bun ~/.huckleberry/kanban/src/cli.mjs complete "$KIMAKI_KANBAN_TASK" --summary "Completed: <what changed>"
 ```
 
 5. If you are blocked:
 
 ```bash
-bun /Users/clawdbot/clawd/workspace/kimaki-kanban/src/cli.mjs block "$KIMAKI_KANBAN_TASK" --reason "Need human input: <specific question>"
+bun ~/.huckleberry/kanban/src/cli.mjs block "$KIMAKI_KANBAN_TASK" --reason "Need human input: <specific question>"
 ```
 
 ## Workflow Templates
@@ -47,8 +47,8 @@ The kanban system supports brand-agnostic workflow templates. These are YAML fil
 ### Listing Templates
 
 ```bash
-bun /Users/clawdbot/clawd/workspace/kimaki-kanban/src/cli.mjs templates
-bun /Users/clawdbot/clawd/workspace/kimaki-kanban/src/cli.mjs templates --details
+bun ~/.huckleberry/kanban/src/cli.mjs templates
+bun ~/.huckleberry/kanban/src/cli.mjs templates --details
 ```
 
 ### Stamping a Template for a Brand
@@ -57,7 +57,7 @@ See **CLI Reference** below for full syntax.
 
 ## CLI Reference
 
-All commands: `bun /Users/clawdbot/clawd/workspace/kimaki-kanban/src/cli.mjs <command> [options]`
+All commands: `bun ~/.huckleberry/kanban/src/cli.mjs <command> [options]`
 
 Common flags: `--db <path>` (default: `kanban.db` in cwd)
 
@@ -65,29 +65,29 @@ Common flags: `--db <path>` (default: `kanban.db` in cwd)
 
 ```bash
 # Create a task
-cli.mjs create "Task title" --tenant <business> --project <project> --assignee <agent> --skills skill1,skill2
+~/.huckleberry/kanban/src/cli.mjs create "Task title" --tenant <business> --project <project> --assignee <agent> --skills skill1,skill2
 
 # List tasks (supports all filters)
-cli.mjs list [--tenant <business>] [--project <project>] [--status ready|todo|in_progress|done|blocked] [--assignee <agent>] [--limit N]
+~/.huckleberry/kanban/src/cli.mjs list [--tenant <business>] [--project <project>] [--status ready|todo|in_progress|done|blocked] [--assignee <agent>] [--limit N]
 
 # Show task details
-cli.mjs show <task_id>
+~/.huckleberry/kanban/src/cli.mjs show <task_id>
 
 # Complete a task
-cli.mjs complete <task_id> --summary "What was done"
+~/.huckleberry/kanban/src/cli.mjs complete <task_id> --summary "What was done"
 
 # Block a task
-cli.mjs block <task_id> --reason "Why blocked"
+~/.huckleberry/kanban/src/cli.mjs block <task_id> --reason "Why blocked"
 ```
 
 ### Templates
 
 ```bash
 # List available templates
-cli.mjs templates [--details]
+~/.huckleberry/kanban/src/cli.mjs templates [--details]
 
 # Stamp a template (creates all tasks in the DAG)
-cli.mjs stamp <template-name> \
+~/.huckleberry/kanban/src/cli.mjs stamp <template-name> \
   --var topic="solar chargers" \
   --var tenant=nomadixgear \
   --project seo-hub-spoke
@@ -99,17 +99,17 @@ The `--project` flag groups tasks within a tenant by project. Use it on `create`
 
 ```bash
 # Create with project
-cli.mjs create "Build hub pages" --tenant enchantents --project seo-hub-spoke
+~/.huckleberry/kanban/src/cli.mjs create "Build hub pages" --tenant enchantents --project seo-hub-spoke
 
 # List only tasks for a specific project
-cli.mjs list --tenant enchantents --project seo-hub-spoke
+~/.huckleberry/kanban/src/cli.mjs list --tenant enchantents --project seo-hub-spoke
 
 # Stamp with project (all tasks in the DAG inherit it)
-cli.mjs stamp blog-social-campaign --var topic="solar chargers" --var tenant=enchantents --project seo-hub-spoke
+~/.huckleberry/kanban/src/cli.mjs stamp blog-social-campaign --var topic="solar chargers" --var tenant=enchantents --var content_tier=commodity --var digital_brain_delta="one line: what this piece adds to the brand's digital brain" --project seo-hub-spoke
 ```
 
 Available templates:
-- `blog-social-campaign` — Research (keywords + Reddit + PAA) → AEO triplet publish → multi-platform distribution (5 tasks)
+- `blog-social-campaign` — Research (keywords + Reddit + PAA) → AEO triplet publish → multi-platform distribution (15 tasks, requires content_tier + digital_brain_delta)
 - `ai-visibility-sprint` — AI citation audit → gap analysis → content overhaul → distribute → tracking setup (5 tasks)
 - `product-launch` — Position → assets → listing + announce (4 tasks)
 - `b2b-outreach` — Scrape → research → emails → send (4 tasks)
@@ -117,7 +117,7 @@ Available templates:
 
 ### Building a New Template
 
-Create a YAML file in `/Users/clawdbot/clawd/workspace/kimaki-kanban/templates/`:
+Create a YAML file in `~/.huckleberry/kanban/templates/`:
 
 ```yaml
 name: My Workflow
@@ -148,7 +148,7 @@ tasks:
       Write about {{topic}} using step1 results.
 ```
 
-Run `bun /Users/clawdbot/clawd/workspace/kimaki-kanban/src/cli.mjs stamp-help` for the full agent guide.
+Run `bun ~/.huckleberry/kanban/src/cli.mjs stamp-help` for the full agent guide.
 
 ## Human Gates
 

package/kanban/package.json

@@ -4,6 +4,6 @@
   "version": "1.0.0",
   "type": "module",
   "dependencies": {
-    "better-sqlite3": "^11.0.0"
+    "better-sqlite3": "^13.0.3"
   }
 }

package/kanban/src/dispatcher.mjs

@@ -181,7 +181,7 @@ function resolveAgent(assignee, mapping, fallback = 'build') {
 }
 
 const TENANT_WORKDIRS = {
-    'ai-employee-setup': '/Users/clawdbot/clawd/businesses/aiwithjai/ai-employee-setup',
+    'ai-employee-setup': '/Users/clawdbot/clawd/businesses/huckleberry/platform/ai-employee-setup',
     'natureshares': '/Users/clawdbot/clawd/businesses/natureshares',
     'enchantents': '/Users/clawdbot/clawd/businesses/nomadixgear-sa/enchantents',
     'nomadixgear': '/Users/clawdbot/clawd/businesses/nomadixgear-sa',