@godmode-team/godmode 1.7.2 → 1.8.2

package/openclaw.plugin.json

@@ -1,16 +1,45 @@
 {
   "id": "godmode",
   "name": "GodMode",
-  "description": "Personal AI Operating System for entrepreneurs",
-  "version": "1.7.2",
+  "description": "Personal AI Operating System — your deeply contextual AI ally that manages tasks, memory, integrations, and a swarm of agents",
+  "version": "1.8.2",
+  "license": "FSL-1.1-MIT",
+  "author": {
+    "name": "GodMode Team",
+    "url": "https://lifeongodmode.com"
+  },
+  "repository": "https://github.com/GodMode-Team/godmode",
+  "homepage": "https://lifeongodmode.com",
+  "keywords": ["ai", "personal-ai", "agent", "memory", "productivity", "second-brain", "automation"],
+  "categories": ["productivity", "ai-agents", "automation", "memory"],
+  "icon": "assets/icon.png",
+  "screenshots": [],
+  "capabilities": {
+    "hooks": [
+      "before_prompt_build",
+      "message_received",
+      "message_sending",
+      "gateway_start"
+    ],
+    "tools": true,
+    "ui": true,
+    "rpc": true,
+    "mcp": true,
+    "standalone": true
+  },
+  "requirements": {
+    "node": ">=22",
+    "openclaw": ">=2026.2.0 <2027.0.0"
+  },
+  "quickStart": {
+    "install": "openclaw plugins install @godmode-team/godmode",
+    "alternative": "npx create-godmode",
+    "requiredEnv": ["ANTHROPIC_API_KEY"],
+    "optionalEnv": ["HONCHO_API_KEY", "COMPOSIO_API_KEY", "OBSIDIAN_VAULT_PATH"]
+  },
   "configSchema": {
     "type": "object",
     "properties": {
-      "licenseKey": {
-        "type": "string",
-        "default": "",
-        "description": "GodMode subscription license key (starts with GM-)"
-      },
       "workspaceRoot": {
         "type": "string",
         "default": "~/godmode",

package/package.json

@@ -1,17 +1,17 @@
 {
   "name": "@godmode-team/godmode",
-  "version": "1.7.2",
+  "version": "1.8.2",
   "private": false,
   "description": "GodMode - Personal AI Operating System plugin for OpenClaw",
-  "license": "SEE LICENSE IN LICENSE",
+  "license": "FSL-1.1-MIT",
   "author": "GodMode Team <support@lifeongodmode.com>",
   "homepage": "https://lifeongodmode.com",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/GodMode-Team/godmode-plugin.git"
+    "url": "git+https://github.com/GodMode-Team/godmode.git"
   },
   "bugs": {
-    "url": "https://github.com/GodMode-Team/godmode-plugin/issues"
+    "url": "https://github.com/GodMode-Team/godmode/issues"
   },
   "keywords": [
     "openclaw",
@@ -22,6 +22,10 @@
   ],
   "type": "module",
   "main": "dist/index.js",
+  "bin": {
+    "godmode": "./dist/standalone.js",
+    "godmode-mcp": "./dist/mcp-entry.js"
+  },
   "exports": {
     ".": {
       "import": "./dist/index.js"
@@ -39,8 +43,11 @@
     "dist/**/*.pem",
     "assets/agent-roster/**/*.md",
     "assets/skills/**/*.md",
+    "skill-cards/**/*.md",
     "dist/assets/**/*.json",
     "dist/assets/**/*.md",
+    "scripts/install-systemd.sh",
+    "scripts/godmode-gateway.service",
     "openclaw.plugin.json",
     "LICENSE",
     "README.md"
@@ -50,6 +57,8 @@
     "build:code": "tsup",
     "build:ui": "vite build --config ui/vite.config.ts",
     "bundle:ui": "node scripts/bundle-ui.mjs",
+    "start": "node dist/standalone.js",
+    "dev": "pnpm build && node dist/standalone.js",
     "dev:ui": "vite --config ui/vite.config.ts",
     "test:ui": "vitest run --config ui/vitest.config.ts",
     "ui:sync": "node scripts/sync-ui-from-repo.mjs",
@@ -61,19 +70,24 @@
     "postinstall": "bash patches/fix-imessage-native-vision.sh 2>/dev/null || true"
   },
   "dependencies": {
+    "@composio/core": "0.6.5",
+    "@honcho-ai/sdk": "2.0.1",
+    "@lit/context": "1.1.6",
     "@noble/ed25519": "3.0.0",
-    "better-sqlite3": "^11.8.1",
-    "chokidar": "^4.0.3",
-    "clawhub": "^0.7.0",
-    "dompurify": "^3.3.1",
-    "json5": "^2.2.3",
-    "lit": "^3.3.2",
-    "marked": "^17.0.1",
-    "mem0ai": "^2.2.4"
+    "better-sqlite3": "^12.8.0",
+    "chokidar": "4.0.3",
+    "dompurify": "3.3.3",
+    "json5": "2.2.3",
+    "lit": "3.3.2",
+    "marked": "17.0.3",
+    "mem0ai": "^2.3.0",
+    "ws": "8.19.0"
   },
   "devDependencies": {
+    "@browserbasehq/stagehand": "^3.2.0",
     "@types/node": "^24.3.3",
-    "openclaw": "^2026.2.23",
+    "@types/ws": "^8.18.1",
+    "openclaw": "^2026.3.22",
     "tsup": "^8.5.1",
     "tsx": "^4.21.0",
     "typescript": "^5.9.3",

package/scripts/godmode-gateway.service

@@ -0,0 +1,41 @@
+# GodMode OpenClaw Gateway systemd user service.
+#
+# Install with:
+#   ./scripts/install-systemd.sh
+#
+# Manage the service with:
+#   systemctl --user start godmode-gateway.service
+#   systemctl --user stop godmode-gateway.service
+#   systemctl --user restart godmode-gateway.service
+#   systemctl --user status godmode-gateway.service
+#
+# Follow logs with:
+#   journalctl --user -u godmode-gateway.service -f
+#
+# On headless Linux, enable lingering if you want the user service to keep
+# running after logout and come back on reboot:
+#   sudo loginctl enable-linger $USER
+#
+# If the `openclaw` or `node` install path changes, rerun the installer so the
+# absolute ExecStart path and PATH environment stay current.
+
+[Unit]
+Description=GodMode OpenClaw Gateway
+After=network-online.target
+Wants=network-online.target
+
+[Service]
+Type=simple
+Environment=HOME=${GODMODE_HOME_DIR}
+Environment=PATH=${GODMODE_PATH}
+Environment=NODE_ENV=production
+WorkingDirectory=${GODMODE_WORKING_DIRECTORY}
+ExecStart=${GODMODE_OPENCLAW_BIN} gateway run
+Restart=on-failure
+RestartSec=5
+StandardOutput=journal
+StandardError=journal
+SyslogIdentifier=godmode-gateway
+
+[Install]
+WantedBy=default.target

package/scripts/install-systemd.sh

@@ -0,0 +1,99 @@
+#!/bin/sh
+
+set -eu
+
+fail() {
+  printf 'Error: %s\n' "$1" >&2
+  exit 1
+}
+
+info() {
+  printf '%s\n' "$1"
+}
+
+escape_sed_replacement() {
+  printf '%s' "$1" | sed 's/[\\/&|]/\\&/g'
+}
+
+run_systemctl_user() {
+  if ! systemctl --user "$@"; then
+    fail "systemctl --user $* failed. Make sure your Linux user has an active systemd user session, then retry."
+  fi
+}
+
+if [ "$(uname -s)" != "Linux" ]; then
+  fail "This installer only supports Linux systemd user services."
+fi
+
+if [ -z "${HOME:-}" ]; then
+  fail "HOME is not set."
+fi
+
+if ! command -v systemctl >/dev/null 2>&1; then
+  fail "systemctl is required but was not found."
+fi
+
+if ! command -v openclaw >/dev/null 2>&1; then
+  fail "openclaw is not on PATH. Install the OpenClaw CLI first."
+fi
+
+if ! command -v node >/dev/null 2>&1; then
+  fail "node is not on PATH. Install Node.js 22+ first."
+fi
+
+SCRIPT_DIR=$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)
+TEMPLATE_PATH="$SCRIPT_DIR/godmode-gateway.service"
+SERVICE_NAME="godmode-gateway.service"
+TARGET_DIR="$HOME/.config/systemd/user"
+TARGET_PATH="$TARGET_DIR/$SERVICE_NAME"
+
+if [ ! -f "$TEMPLATE_PATH" ]; then
+  fail "Service template not found at $TEMPLATE_PATH"
+fi
+
+OPENCLAW_BIN=$(command -v openclaw)
+NODE_BIN=$(command -v node)
+OPENCLAW_BIN_DIR=$(dirname "$OPENCLAW_BIN")
+NODE_BIN_DIR=$(dirname "$NODE_BIN")
+PATH_VALUE="$OPENCLAW_BIN_DIR:$NODE_BIN_DIR:$HOME/.local/bin:/usr/local/bin:/usr/bin:/bin${PATH:+:$PATH}"
+
+export GODMODE_HOME_DIR="$HOME"
+export GODMODE_PATH="$PATH_VALUE"
+export GODMODE_WORKING_DIRECTORY="$HOME"
+export GODMODE_OPENCLAW_BIN="$OPENCLAW_BIN"
+
+mkdir -p "$TARGET_DIR"
+
+if command -v envsubst >/dev/null 2>&1; then
+  envsubst '${GODMODE_HOME_DIR} ${GODMODE_PATH} ${GODMODE_WORKING_DIRECTORY} ${GODMODE_OPENCLAW_BIN}' < "$TEMPLATE_PATH" > "$TARGET_PATH"
+else
+  HOME_ESCAPED=$(escape_sed_replacement "$GODMODE_HOME_DIR")
+  PATH_ESCAPED=$(escape_sed_replacement "$GODMODE_PATH")
+  WORKDIR_ESCAPED=$(escape_sed_replacement "$GODMODE_WORKING_DIRECTORY")
+  OPENCLAW_ESCAPED=$(escape_sed_replacement "$GODMODE_OPENCLAW_BIN")
+
+  sed \
+    -e "s|\${GODMODE_HOME_DIR}|$HOME_ESCAPED|g" \
+    -e "s|\${GODMODE_PATH}|$PATH_ESCAPED|g" \
+    -e "s|\${GODMODE_WORKING_DIRECTORY}|$WORKDIR_ESCAPED|g" \
+    -e "s|\${GODMODE_OPENCLAW_BIN}|$OPENCLAW_ESCAPED|g" \
+    "$TEMPLATE_PATH" > "$TARGET_PATH"
+fi
+
+chmod 0644 "$TARGET_PATH"
+
+info "Installed $SERVICE_NAME to $TARGET_PATH"
+
+run_systemctl_user daemon-reload
+run_systemctl_user enable --now "$SERVICE_NAME"
+
+printf '\n'
+systemctl --user status --no-pager --full "$SERVICE_NAME" || true
+
+if command -v loginctl >/dev/null 2>&1; then
+  LINGER=$(loginctl show-user "${USER:-$(id -un)}" -p Linger --value 2>/dev/null || true)
+  if [ "$LINGER" = "no" ]; then
+    printf '\nNote: enable lingering to keep %s alive after logout and on reboot:\n' "$SERVICE_NAME"
+    printf '  sudo loginctl enable-linger %s\n' "${USER:-$(id -un)}"
+  fi
+fi

package/skill-cards/adversarial-board.md

@@ -0,0 +1,63 @@
+---
+domain: strategy
+triggers: advisory board, devil's advocate, debate this, opposing views, what could go wrong, challenge my thinking, stress test, second opinion, poke holes, critique
+name: godmode-adversarial-board
+version: 1.0.0
+description: "Simulates a 5-person advisory board to stress-test decisions and strategies"
+keywords: ["advisory board", "devil's advocate", "debate this", "opposing views", "what could go wrong"]
+author: godmode-team
+clawhub: true
+---
+## When to Use
+
+Run AFTER meta-problem-solver and context-deep-dive. The board debates better with a problem brief and full context.
+
+Use when the user needs to pressure-test a decision, strategy, offer, or plan from multiple angles before committing.
+
+## The Board
+
+Simulate 5 advisors, each with a distinct lens:
+
+### 1. The Operator
+Ops and execution lens. "Can we actually do this? What's the operational cost? Who does the work? What breaks if we're wrong?"
+- Focuses on: feasibility, resources, timeline, dependencies, maintenance burden
+
+### 2. The Skeptic
+Devil's advocate. "Why will this fail? What are we missing? What's the base rate for this kind of bet?"
+- Focuses on: hidden assumptions, survivorship bias, things that sound good but don't work
+
+### 3. The Visionary
+Upside maximizer. "What's the 10x version? What adjacent opportunity are we ignoring? How does this compound?"
+- Focuses on: leverage, asymmetric upside, network effects, what this enables next
+
+### 4. The Customer
+ICP lens. "Does the target user actually want this? Would they pay for it? What's their real pain?"
+- Focuses on: demand validation, willingness to pay, switching costs, user experience
+
+### 5. The Risk Officer
+Downside, legal, and financial lens. "What's the worst case? What liability exists? What's the reversibility?"
+- Focuses on: tail risks, regulatory issues, financial exposure, reputational damage
+
+## Format
+
+Each advisor gets 2-3 sentences — sharp, specific, no fluff.
+
+Then synthesize:
+
+**Consensus:** (what all advisors agree on)
+
+**Key disagreements:** (where they split and why)
+
+**Recommended path:** (your synthesis weighing all perspectives)
+
+**Confidence level:** high / medium / low (and why)
+
+## Customization
+
+Advisors are configurable per user context. A chiropractor gets different board members than a SaaS founder. Pull user context from memory to tailor the advisors' perspectives to the user's industry, scale, and constraints.
+
+## Rules
+- Run meta-problem-solver first — the board needs a structured problem to debate
+- Each advisor must disagree with at least one other advisor — if they all agree, you're not stress-testing
+- Don't let The Visionary dominate — exciting ideas need operational grounding
+- The Skeptic is not a blocker — they identify risks so they can be mitigated, not avoided

package/skill-cards/autoresearch.md

@@ -0,0 +1,39 @@
+---
+domain: autoresearch
+triggers: autoresearch, optimize, overnight, campaign, eval, benchmark, tune, evolve prompts, improve godmode
+tools: queue_add
+name: godmode-autoresearch
+version: 1.0.0
+description: "Overnight optimization system using the Karpathy eval-loop pattern"
+keywords: ["autoresearch", "optimize", "overnight", "campaign", "eval"]
+author: godmode-team
+clawhub: true
+---
+
+# Autoresearch — Overnight Optimization System
+
+The autoresearch system uses the Karpathy pattern (modify → measure → keep/revert → loop) to optimize GodMode overnight.
+
+## How to Run
+- Full suite: `nohup bash autoresearch/overnight.sh &> autoresearch/overnight.log &`
+- Single campaign: `node autoresearch/campaigns/<name>.mjs --iterations N`
+- Eval only: `node autoresearch/eval-runner.mjs`
+
+## Available Campaigns
+| Campaign | Type | What It Optimizes |
+|----------|------|-------------------|
+| context-words | Deterministic | TIME_WORDS, OPS_WORDS relevance gates |
+| skill-triggers | Deterministic | Skill card keyword matching |
+| memory-thresholds | Deterministic | memory score thresholds, limits |
+| soul-essence | LLM Judge | SOUL_ESSENCE, CAPABILITY_MAP prompts |
+| queue-prompts | LLM Judge | Queue PROMPT_TEMPLATES |
+| ally-experience | LLM Judge | Customer persona simulation (leverage/flow/awakening/purpose) |
+| second-brain | LLM Judge | Vault optimization |
+| product-audit | LLM + Structural | Full 5-phase product audit |
+
+## Tips
+- All LLM campaigns use Sonnet 4.6 (never lesser models)
+- Auth resolves from Claude Code OAuth with auto-refresh
+- The overnight runner creates a git safety snapshot before any mutations
+- Logs go to `autoresearch/logs/` and `autoresearch/campaigns/*-log.tsv`
+- Product audit generates a markdown report at `autoresearch/campaigns/product-audit-report.md`

package/skill-cards/bill-review.md

@@ -0,0 +1,26 @@
+---
+domain: bill-review
+triggers: bills, expenses, spending, subscriptions, charges, financial review, bill review, monthly expenses, recurring charges, budget, money
+tools: queue_add
+name: godmode-bill-review
+version: 1.0.0
+description: "Reviews bills, subscriptions, and recurring charges for savings opportunities"
+keywords: ["bills", "expenses", "spending", "subscriptions", "charges"]
+author: godmode-team
+clawhub: true
+---
+
+# Bill Review — Monthly Expense Analysis
+
+When the user asks about expenses, subscriptions, or spending — route to the monthly-bill-review skill.
+
+## How to Use
+1. Use `queue_add` with skill `monthly-bill-review`, taskType `analysis`, persona `finance-admin`
+2. The skill reviews past month: categorizes expenses, flags anomalies, compares trends
+3. Output: categorized table + month-over-month comparison + action items (cancel, dispute, investigate)
+
+## When to Trigger
+- "Review my bills"
+- "Any weird charges this month?"
+- "What am I spending on subscriptions?"
+- Runs automatically on the 1st of each month via cron

package/skill-cards/calendar.md

@@ -0,0 +1,32 @@
+---
+domain: calendar
+triggers: meeting, schedule, calendar, event, availability, free, busy, when am i, what's next, upcoming, standup, reschedule, block off, coming up, tomorrow
+tools: calendar.events.today, calendar.events.range
+name: godmode-calendar
+version: 1.0.0
+description: "Manages schedule, meetings, availability, and calendar events"
+keywords: ["meeting", "schedule", "calendar", "event", "availability"]
+author: godmode-team
+clawhub: true
+---
+## When to Use
+- User asks about schedule, meetings, availability, "what's next"
+- Meeting prep — proactively offer when a meeting is within 2 hours
+- Scheduling conflicts or free time analysis
+
+## How to Use
+- `calendar.events.today` — today's events (cached 2 min)
+- `calendar.events.range` — events in a date range { startDate, endDate }
+- Schedule is often already injected above — check there FIRST
+
+## Gotchas
+- All-day events have no startTime — check the `allDay` flag before formatting times
+- Events cache for 2 minutes — if user just added one, tell them it may take a moment to appear
+- Attendee emails may be truncated — match by first name when possible
+- Uses `gog` CLI under the hood — if calendar fails, check `integrations.status` for GOG_CALENDAR_ACCOUNT
+- Time zones: always format in the user's timezone (shown in identity above)
+
+## Tips
+- Cross-reference attendees with vault people files via secondBrain.search
+- When user mentions a person + time, proactively check for conflicts
+- For "am I free Tuesday?", use calendar.events.range, don't guess

package/skill-cards/code-quality.md

@@ -0,0 +1,31 @@
+---
+domain: code-quality
+triggers: bug hunt, find bugs, code review, review my code, check for bugs, audit code, error handling, silent failures, simplify code, clean up code, refactor, code quality
+tools: queue_add
+name: godmode-code-quality
+version: 1.0.0
+description: "Audits code for bugs, silent failures, and quality improvements"
+keywords: ["bug hunt", "find bugs", "code review", "review my code", "check for bugs"]
+author: godmode-team
+clawhub: true
+---
+
+# Code Quality — Bug Hunting, Review & Simplification
+
+When the user wants code audited, reviewed, or cleaned up — route to the right queue skill.
+
+## Which Skill to Use
+
+| User Intent | Queue Skill | taskType |
+|---|---|---|
+| "Find bugs", "audit this code" | bug-hunt | review |
+| "Review this PR", "code review" | code-review | review |
+| "Check error handling", "silent failures" | silent-failure-audit | review |
+| "Simplify", "clean up", "refactor" | code-simplify | coding |
+
+## How to Use
+1. Ask which codebase/files/PR to target (if not obvious)
+2. Use `queue_add` with the matching skill as the description template
+3. Include: target files/PR, what to focus on, any known pain points
+4. For bug-hunt: results come back as a scored report with MUST FIX / DEFERRED lists
+5. For code-review: results come as scored issues filtered for confidence

package/skill-cards/competitor-scan.md

@@ -0,0 +1,26 @@
+---
+domain: competitor-scan
+triggers: competitors, competitor scan, market research, what are competitors doing, ai market, competitive landscape, market moves, product launches, competitive analysis
+tools: queue_add
+name: godmode-competitor-scan
+version: 1.0.0
+description: "Scans the competitive landscape and tracks market moves"
+keywords: ["competitors", "competitor scan", "market research", "what are competitors doing", "ai market"]
+author: godmode-team
+clawhub: true
+---
+
+# Competitor Scan — Weekly Market Intelligence
+
+When the user asks about competitors, market landscape, or wants a competitive analysis — route to the competitor-scan skill.
+
+## How to Use
+1. Use `queue_add` with skill `competitor-scan`, taskType `research`, persona `researcher`
+2. The skill researches AI assistant market: launches, features, funding, positioning
+3. Output: Market Moves, Opportunities, Threats — 1 page with cited sources
+
+## When to Trigger
+- "What are our competitors doing?"
+- "Any new AI tools this week?"
+- "Run a competitive scan"
+- Runs automatically weekly Monday 8am via cron

package/skill-cards/content-generation.md

@@ -0,0 +1,26 @@
+---
+domain: content-generation
+triggers: content, write posts, social media, tweets, blog post, newsletter, content ideas, what should I post, weekly content, twitter posts, x posts
+tools: queue_add
+name: godmode-content-generation
+version: 1.0.0
+description: "Generates social media posts, blog content, and newsletters"
+keywords: ["content", "write posts", "social media", "tweets", "blog post"]
+author: godmode-team
+clawhub: true
+---
+
+# Content Generation — Weekly Content from Your Activity
+
+When the user wants content created from their recent work and notes — route to the weekly-content skill.
+
+## How to Use
+1. Use `queue_add` with skill `weekly-content`, taskType `creative`, persona `content-writer`
+2. The skill reviews past 7 days of vault notes, extracts topics and insights
+3. Output: 5 social posts + 1 blog outline + 1 newsletter draft — all in the user's voice
+
+## When to Trigger
+- "Write me some posts"
+- "What should I tweet about this week?"
+- "Generate content from my notes"
+- Runs automatically weekly Tuesday 9am via cron

package/skill-cards/context-deep-dive.md

@@ -0,0 +1,65 @@
+---
+domain: strategy
+triggers: gather context, what do we know, deep dive, before we decide, pull everything, context check, what am I missing, full picture, background on
+name: godmode-context-deep-dive
+version: 1.0.0
+description: "Gathers and synthesizes all available context before a decision"
+keywords: ["gather context", "what do we know", "deep dive", "before we decide", "pull everything"]
+author: godmode-team
+clawhub: true
+---
+## When to Use
+
+Run this before any major debate, recommendation, or delegation. Full context = better decisions.
+
+This step feeds the adversarial-board and delegation pipelines. Without it, you're guessing.
+
+## Context Gathering Protocol
+
+### 1. Memory Search
+Search memory for related facts, preferences, past decisions, and stated goals. Cast a wide net — search multiple angles:
+- The topic directly
+- Related people or companies
+- Past decisions in this domain
+- User preferences that apply
+
+### 2. Vault Search
+Search the vault (second-brain tool) for:
+- Notes and artifacts on this topic
+- Meeting notes with relevant context
+- Past project deliverables
+- Research the user or agents have done before
+
+### 3. Recent Sessions
+Check recent conversation history for:
+- Related discussions in the last few days
+- Decisions made but not yet acted on
+- Context the user shared casually that's now relevant
+
+### 4. People & Company Context
+If the decision involves other people or organizations:
+- Pull contact/company context from memory
+- Check for past interactions, preferences, relationship notes
+- Note any power dynamics or stakeholder concerns
+
+### 5. Compile Context Brief
+
+Present what you found:
+
+**What we know:**
+- (facts from memory, vault, sessions)
+
+**What we don't know:**
+- (gaps that could change the decision)
+
+**What's changed recently:**
+- (new information since last time this topic came up)
+
+**Relevant past decisions:**
+- (what was decided before and why)
+
+## Rules
+- Don't skip this step for complex decisions — even if you think you know the answer
+- Surface contradictions — if memory says one thing and vault says another, flag it
+- Be honest about gaps — "we don't have data on this" is valuable information
+- Keep it concise — this feeds the next step, it's not the final deliverable

package/skill-cards/cron-workflows.md

@@ -0,0 +1,33 @@
+---
+domain: integrations
+triggers: recurring, every day, every week, weekly, daily, automate, workflow, schedule task, set up routine, ongoing
+tools: cron_create, cron_list, queue_add
+name: godmode-cron-workflows
+version: 1.0.0
+description: "Sets up recurring automated workflows and scheduled tasks"
+keywords: ["recurring", "every day", "every week", "weekly", "daily"]
+author: godmode-team
+clawhub: true
+---
+## When to Use
+- The user wants a recurring business function automated
+- The task is repeatable and can be reviewed after each run
+- Results should improve over time through inbox scoring
+
+## How to Create Workflows
+1. Ask what needs to happen, how often, and what success looks like
+2. Pick the best persona for the job
+3. Create a cron job that queues a clear, specific task brief
+4. Make sure the result lands in the inbox for review and scoring
+5. Use low scores as correction data for the next run
+
+## Cron + Agent Pattern
+- Queue a specific agent execution via `queue_add`
+- Use concrete instructions, not generic prompts
+- Pick the right task type so evidence checks apply
+- Prefer workflows the user can quickly review and rate
+
+## Examples
+- Weekly SEO audit every Monday at 6am
+- Daily inbox triage every weekday at 7am
+- Friday content review every week at 5pm

package/skill-cards/dashboards.md

@@ -0,0 +1,38 @@
+---
+domain: dashboards
+triggers: dashboard, dashboards, chart, charts, visualization, visualize, report, analytics, data view, overview, metrics, stats, statistics, scorecard, leaderboard, tracker, tracking, breakdown, summary view, show me my, build me a
+tools: dashboards.save, dashboards.widgetData, dashboards.list
+name: godmode-dashboards
+version: 1.0.0
+description: "Creates data visualizations, charts, and metric dashboards"
+keywords: ["dashboard", "dashboards", "chart", "charts", "visualization"]
+author: godmode-team
+clawhub: true
+---
+## When to Use
+- User asks for ANY dashboard, chart, report, visualization, overview, or data view
+- User says "show me my..." or "build me a..." with data/metrics context
+- User is on the Dashboards tab and asks for something new
+- User asks to update, refresh, or change an existing dashboard
+
+## CRITICAL: Always Save
+**ALWAYS call `dashboards.save` after generating dashboard HTML.** This is what makes the dashboard appear in the Dashboards tab. If you just output HTML in chat without saving, the user cannot find it later.
+
+## How to Use
+1. Call `dashboards.widgetData` with relevant widget IDs to get live data
+2. Generate beautiful HTML with `<style>` blocks, SVG charts, gradients, animations
+3. Call `dashboards.save` with: `{ title, html, scope: "global", description?, widgets? }`
+4. Tell the user: "I've saved this to your Dashboards tab."
+
+### Available Widgets
+`tasks-summary`, `tasks-today`, `agent-activity`, `queue-status`, `trust-scores`, `brief-summary`, `streak-stats`, `workspace-stats`
+
+## HTML Rules
+- ✅ Use: `<style>`, SVG, inline styles, all HTML, animations, @keyframes, @media
+- ❌ Never: `<script>`, `<iframe>`, `<link>`, `@import`, event handlers
+- Use theme vars: `var(--text)`, `var(--muted)`, `var(--accent)`, `var(--card)`, `var(--bg-elevated)`, `var(--border)`, `var(--success)`, `var(--warning)`, `var(--danger)`
+
+## Gotchas
+- If updating an existing dashboard, pass its `id` to `dashboards.save` to overwrite (not create a duplicate)
+- Call `dashboards.list` first to check if a similar dashboard already exists
+- Dashboards should look stunning — use SVG charts, not plain tables