Github|...

Grok Bot template recipe

Create a public Sp00ky Grok Bot template using source material in apps/grok-bot.

The monorepo keeps Grok Bot template source material under apps/grok-bot. Use it to create a public Bot template that helps people build and operate Sp00ky (@spooky-sync) apps.

This folder is not a runtime npm library or an automatically importable bundle. It holds a profile draft, reference facts, and skills to add to a Bot. Learned memory is not part of the shared template configuration.

Who it is for

  • App builders starting a Sp00ky project (schema → codegen → Solid clients → SSP)
  • Operators running Sp00ky in production (doctor/verify, allowlists, SSP/scheduler health, incident triage)
  • Contributors working in this monorepo

What ships in the recipe

Skills live under apps/grok-bot/skills/*/SKILL.md:

Skill folderUse when
sp00ky-onboardingFirst import, explain Sp00ky, pick app vs prod vs monorepo track
sp00ky-schema-codegenSchema edits, spky generate, spky doctor, allowlists, @crdt / @parent
sp00ky-solid-appSolid providers, queries/mutations, Solid 2 bindings
sp00ky-debug-mcpStale queries, sync stalls, live schema/data via DevTools MCP
sp00ky-prod-opsProduction health, deploys, drift, backups — diagnose before changing anything
sp00ky-monorepoContributing here: docs-sync, version bumps, PR hygiene

Profile copy and sharing notes live in apps/grok-bot/BOT.md.

Share as a public Grok Bot template

  1. Keep the drafts aligned with real CLI behavior (spky generate, spky doctor, spky recipe, spky agents init, sp00ky.yml).
  2. Create a Bot in Grok Bot. Use BOT.md for its profile, save and enable the relevant skills, and put essential facts from memories/profile.md in the description or skills.
  3. Open Share → Create template, choose Public link, then check View template details. Remove secrets, private paths, and customer data before copying the link.

See Grok Bot’s sharing guide for the current controls and what the recipient receives.

DevTools MCP needs separate setup

A shared Bot template does not provision Sp00ky’s local DevTools MCP server. Developers using a compatible MCP client can configure it separately:

{
  "mcpServers": {
    "spooky-devtools": {
      "command": "npx",
      "args": ["-y", "@spooky-sync/devtools-mcp"]
    }
  }
}

Or from an app: spky mcp. See AI coding agents and MCP server for how DevTools MCP relates to cloud and scheduler admin MCP.

Verify in the monorepo

find apps/grok-bot -type f | sort

After docs edits, build the site:

cd apps/landing-page && pnpm build

Next steps