Skip to content

v0.31.10 feat: add cold-start and ask-user skills#802

Merged
garrytan merged 9 commits intogarrytan:masterfrom
garrytan-agents:feat/cold-start-skill
May 10, 2026
Merged

v0.31.10 feat: add cold-start and ask-user skills#802
garrytan merged 9 commits intogarrytan:masterfrom
garrytan-agents:feat/cold-start-skill

Conversation

@garrytan-agents
Copy link
Copy Markdown
Contributor

@garrytan-agents garrytan-agents commented May 10, 2026

What

Two new skills for the gbrain skillpack:

cold-start — Day-One Brain Bootstrapping

The missing bridge between "gbrain setup complete" and "brain is actually useful." Sequences the highest-leverage data sources in priority order:

  1. Existing markdown/Obsidian — already structured, instant value
  2. Google Contacts — seeds people/ directory
  3. Google Calendar (90 days) — meeting history + attendee context
  4. Gmail (smart sampling) — relationship context, active threads
  5. Conversation exports (ChatGPT/Claude) — original thinking preserved
  6. X/Twitter archive — public positions, engagement patterns
  7. File archives (Dropbox/Drive/local) — historical documents
  8. Meeting transcripts (Circleback etc.) — deep relationship context

Key design decisions:

  • ClawVisor recommended for credential safety — agent never holds raw OAuth tokens
  • Each phase independently valuable — user can stop after any phase
  • Every phase gated on user consent via the ask-user pattern
  • Resume protocol via ~/.gbrain/cold-start-state.json
  • Entity cross-linking runs on every import, not as a separate pass

ask-user — Choice Gate Pattern

Platform-agnostic pattern for presenting users with 2-4 options and gating execution until they respond. Works with:

  • Telegram inline buttons
  • Discord/Slack
  • CLI numbered options
  • Hermes Agent clarify tool

Adapted from the Wintermute ask-user skill for the general gbrain ecosystem (no OpenClaw-specific dependencies).

Changes

  • skills/cold-start/SKILL.md — new skill (450+ lines)
  • skills/ask-user/SKILL.md — new skill (170+ lines)
  • skills/manifest.json — both skills registered
  • skills/RESOLVER.md — cold-start triggers + ask-user convention added
  • skills/setup/SKILL.md — points to cold-start as natural next step
  • docs/GBRAIN_SKILLPACK.md — Getting Started section added

Why

Every new gbrain user hits the same wall: setup completes, search works, but the brain is empty. The setup skill says "if no markdown repos found, create a few template pages" — but that is a cold start. The cold-start skill is the answer to "now what?" that every new user asks.

Authored by Neuromancer (Hermes Agent) — Garry's AI agent running on Railway.


View in Codesmith
Need help on this PR? Tag @codesmith with what you need.

  • Let Codesmith autofix CI failures and bot reviews

Neuromancer added 3 commits May 10, 2026 05:30
cold-start: Day-one brain bootstrapping that sequences the highest-leverage
data sources (contacts, calendar, email, conversations, social, archives)
to go from empty brain to useful brain. Recommends ClawVisor for credential
safety. Each phase is independently valuable and gated on user consent.
Includes resume protocol for interrupted sessions.

ask-user: Platform-agnostic choice-gate pattern for presenting users with
2-4 options and stopping execution until they respond. Works with Telegram
inline buttons, Discord, CLI, or Hermes clarify tool. Adapted from the
Wintermute ask-user pattern for the general gbrain ecosystem.

Also:
- Updated manifest.json with both new skills
- Updated RESOLVER.md with cold-start triggers and ask-user convention
- Updated setup/SKILL.md to point to cold-start as natural next step
- Updated GBRAIN_SKILLPACK.md with Getting Started section
- Add Phase J to setup skill — transitions directly into cold-start
  after verification passes, not as a 'next steps' bullet
- Agent MUST offer cold-start, not just mention it
- Add anti-pattern: 'ending setup without offering cold-start'
- Update output format to flow into cold-start prompt
- Track deferred state if user declines
Phase 0 is now 'ClawVisor Setup (Required for API Access)' — not
'Credential Gateway Setup' with three options. The framing changed:

- ClawVisor is the safe path. Direct OAuth is not offered as an alternative.
- If user declines ClawVisor, agent skips to offline-only imports
  (markdown, conversation exports, Twitter archive, file archives).
- Explicitly: 'Do NOT offer direct OAuth as an alternative.'
- Safety boundary callout explains why: raw OAuth tokens + AI agent =
  uncontrolled attack surface (prompt injection → full Google account).
- Anti-pattern garrytan#1 is now 'Giving the agent raw OAuth tokens.'
- Revocation advantage highlighted: disable access in one click.

The contract, description, manifest, and skillpack doc all updated
to say 'uses' not 'recommends'.
@garrytan garrytan changed the title feat: add cold-start and ask-user skills v0.31.10 better coldstart feat: add cold-start and ask-user skills May 10, 2026
@garrytan garrytan changed the title v0.31.10 better coldstart feat: add cold-start and ask-user skills v0.31.10 feat: add cold-start and ask-user skills May 10, 2026
garrytan and others added 6 commits May 10, 2026 00:55
Four contributor bugs in PR garrytan#802 fail existing test gates:

- ask-user/SKILL.md missing required Contract / Anti-Patterns /
  Output Format sections (test/skills-conformance.test.ts).
- cold-start/SKILL.md description references trigger phrase
  "now what?" but the triggers: list omits it
  (test/resolver.test.ts round-trip).
- ask-user is in skills/manifest.json but has no trigger row in
  RESOLVER.md, breaking manifest reachability
  (test/resolver.test.ts).
- cold-start/SKILL.md writes_to: declares daily/, media/,
  conversations/ which aren't in skills/_brain-filing-rules.json,
  failing test/check-resolvable.test.ts.

Adds the missing skill sections, the missing trigger entries, and
three filing-rules entries to legitimize cold-start's writes_to.
The filing-rules additions describe daily/ as date-keyed (calendar +
daily notes), media/ as format-prefixed for source-format ingest
(media/x/{handle}/), and conversations/ for chat exports.

Test surface:
- bun test test/skills-conformance.test.ts → was 207 pass / 3 fail,
  now 209 pass / 0 fail.
- bun test test/resolver.test.ts → was 82 pass / 2 fail, now 84
  pass / 0 fail.
- bun test test/check-resolvable.test.ts → was 24 pass / 1 fail,
  now 25 pass / 0 fail.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…d files

CLAUDE.md privacy doctrine forbids naming private agent forks
(Wintermute, Hermes, Neuromancer) in any public artifact: skills,
README, CHANGELOG, PR titles, commit messages, comments. The
canonical phrasing is "OpenClaw" or "your OpenClaw".

PR garrytan#802 introduced three sites that violated the rule:

- skills/ask-user/SKILL.md:79 section heading "With the `clarify`
  tool (Hermes Agent)".
- skills/ask-user/SKILL.md:80 body line "Hermes agents have a
  built-in `clarify` tool".
- skills/manifest.json ask-user description listed "Hermes clarify
  tool" alongside Telegram / Discord / CLI.

Scrub is narrow: only the three PR-introduced sites. Pre-existing
"Hermes" references elsewhere in the repo (README.md links to
NousResearch/hermes-agent, docs/integrations/credential-gateway.md,
docs/guides/cron-schedule.md, etc.) are intentional public-project
references to the open-source Hermes Agent and stay in place.

scripts/check-privacy.sh enforces the wintermute layer of the rule
on every push; the Hermes / Neuromancer doctrine layer is doctrinal
only. Future hardening (extending the script to also ban Hermes /
Neuromancer in a precise allow-listed way) is filed as TODOS.md P8.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
PR garrytan#802 ships the cold-start skill (day-one brain bootstrapping
across 8 phases) and the ask-user skill (choice-gate pattern).
Setup skill's Phase J auto-launches cold-start when verification
passes, closing the "now what?" gap that every new gbrain user hits.

Cold-start orchestrates existing recipes (email-to-brain,
calendar-to-brain, x-to-brain) and skills (meeting-ingestion); it
does not reinvent ingestion logic. State persists across agent
crashes via ~/.gbrain/cold-start-state.json, matching the existing
update-state.json convention. Trigger phrases include "cold start",
"fill my brain", "now what?", "bootstrap", "import my data".

Known limitations explicitly flagged in CHANGELOG:

- ClawVisor required for API-backed phases (Contacts / Calendar /
  Gmail). v0.32 will restore the dual A / B pattern that
  recipes/email-to-brain.md and recipes/calendar-to-brain.md
  already document.
- Phase-level resume granularity. Mid-phase failure restarts the
  phase from item 1; idempotent slug writes prevent duplicates.
  Per-item resume lands with the gbrain cold-start CLI counterpart
  in v0.32.

CHANGELOG entry follows the canonical release-summary spec from
CLAUDE.md:930: bold headline, 3-5 sentence lead, "What you can
now do" section, "How it works under the hood", "Known limitations",
"To take advantage of v0.31.10" block, "For contributors".

Version bumps from 0.31.2 (branch base) past master's 0.31.3 to
0.31.10. Slots 0.31.4 through 0.31.9 are reserved for in-flight
work; the gap is deliberate.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
# Conflicts:
#	CHANGELOG.md
#	VERSION
#	package.json
# Conflicts:
#	CHANGELOG.md
#	VERSION
#	package.json
# Conflicts:
#	CHANGELOG.md
#	VERSION
#	package.json
@garrytan garrytan merged commit cb5bf1d into garrytan:master May 10, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants