When to invoke
Invoke after the generic kickoff completes on an OpenClaw host, or when the user says "finish kickoff for OpenClaw", "set up OpenClaw for goc", or initiates OpenClaw-specific GoC setup that the generic kickoff intentionally skipped.
Finish kickoff on OpenClaw
The generic kickoff skill is host-agnostic: it introduces GoC, runs the
persona dialog, asks about the AGENTS.md merge, and runs goc install to
scaffold .game-of-cards/. This complement handles everything OpenClaw-specific
that the generic kickoff intentionally leaves alone:
- the ClawHub / npm install + update cadence,
- the
openclaw plugins inspect/openclaw plugins doctorsanity check, - explicitly confirming that OpenClaw needs no permission grant and has
no host-specific private-notes file (so the user does not go looking
for a
CLAUDE.local.mdanalog that does not exist).
Run this skill after the generic kickoff returns. Re-running is safe: every stage detects existing on-disk state before asking.
Stage 0 — state detection sweep
Confirm the GoC plugin is registered with OpenClaw:
openclaw plugins listshould showgame-of-cardsas enabled.openclaw plugins inspect game-of-cardsshould listgocundercontracts.toolsAND undertoolNames(the latter is the runtime registration; if it is empty whilecontracts.toolslistsgoc, the plugin'sregister()callback never fired — re-install or runopenclaw plugins doctor).python3 --versionshould report 3.10 or newer; the plugin bundles the goc engine but expectspython3on the host PATH.
Hold the detected flags in mind through the rest of the flow. The
generic kickoff has already run, so .game-of-cards/deck/ exists,
AGENTS.md has been handled, and the goc tool is callable.
Stage 1 — install / update cadence note
Skip this stage if openclaw plugins list already shows game-of-cards
in the active session.
Otherwise, deliver this note to the user:
The Game of Cards OpenClaw plugin ships skills, lifecycle hooks, and the bundled
gocengine. To install (one-time per host):openclaw plugins install game-of-cardsOr via npm directly:
npm install -g game-of-cards openclaw plugins install game-of-cardsWhen updating later, run
openclaw plugins update game-of-cards(oropenclaw skills update --allif only skill payloads changed). If the post-update plugin behaves unexpectedly, runopenclaw plugins doctorto surface load errors andopenclaw plugins inspect game-of-cardsto confirm thegoctool registered.
The plugin's only consumer prerequisite is python3 (3.10+) on PATH.
No uv, no pipx, no venv materialization.
Stage 2 — confirm what OpenClaw does NOT need
State the two non-instructions explicitly so the user does not go hunting for a Claude Code-style analog:
No permission grant required. Claude Code gates
Bash(goc:*)behind a per-project allowlist. OpenClaw exposesgocas a registered tool through the plugin sandbox — once the plugin is installed and enabled, the tool is callable with no further opt-in.No host-specific private-notes file. Claude Code conventions include
CLAUDE.local.mdfor project-local notes Claude reads but Git ignores. OpenClaw has no equivalent convention; project-local notes can live anywhere the user prefers (or inAGENTS.md, which the generic kickoff already handled).No
CLAUDE.mdeither. Run from the OpenClaw plugin,goc installrecognizes the host and scaffolds a no-harness layout —.game-of-cards/plus theAGENTS.mdbriefing — and never writes aCLAUDE.md. The dry-run plan readsagents: none; that is correct on OpenClaw, not a missed harness.
Stage 3 — confirm ready
If .game-of-cards/config.yaml records autonomy: as loop, cron
or action, first show the user that mode's entry from § Reference:
autonomy recipes — kickoff recorded the choice, nothing has wired it.
Report to the user:
OpenClaw-specific kickoff is complete. All GoC skills are live through
the plugin; the `goc` tool is callable from any GoC repo on this host.
What should the first card be?
The deck is now live. The agent can invoke any GoC skill (scan-deck,
create-card, pull-card, …) immediately — no further kickoff needed.
Reference: autonomy recipes
One entry per mode kickoff Stage 6 records. Each recipe starts one
pull-card run per tick and leaves the repetition to the scheduler.
loop— in the chat,/loop 30m Run the pull-card skill once.(OpenClaw 2026.8.1 or later; owner-only)./loop stopends it.cron— an automation runs a fresh isolated agent turn on a schedule inside the Gateway, which must stay running:openclaw automations create "*/30 * * * *" "Run the pull-card skill once." --name pull-card --agent <agent>The turn works in its agent's workspace, so pick an agent whose workspace is this repo:
openclaw agents add <agent> --workspace /path/to/repo. A run past the scheduler's 60-minute watchdog is killed mid-card unless--timeout-secondsraises it.action— no recipe ships: OpenClaw has no official GitHub Action, and whether thegoctool loads under the headlessopenclaw agent execis unverified.
