An inspectable, bilingual marketplace for Grok Bot and OpenMausBot extensions.
Bot Extensions puts bots and plugins in one searchable catalog without hiding the differences between their ecosystems. Every record shows its platform, publisher, provenance, capabilities, dependencies, and current source before sending visitors elsewhere.
Browse the marketplace · 中文说明 · Architecture · Contributing
- 5,000+ normalized Grok Bot records and the current plugin catalog
- English and Simplified Chinese routes
- official-first ordering with deterministic trust signals
- search and filters for platform, type, category, publisher, and provenance
- file-native OpenMausBot schemas for bots, plugins, Skills, and attachments
- static Astro output for Cloudflare Workers Static Assets
- JSON Schema validation, type checks, unit tests, and browser tests in CI
The first release is intentionally browse-only. It does not provide accounts, ratings, installation, artifact distribution, uploads, presets, or public version history.
corepack enable
pnpm install
pnpm validate
pnpm devBuild the production artifact with pnpm build. Run pnpm test for unit coverage and pnpm test:e2e after installing Playwright Chromium.
All canonical extension resources live under extensions/<platform>/, with bots/ and plugins/ directories for each platform. Full Grok Bot recipes and templates, plus complete public plugin records, live in extensions/grok-bot/; plugin implementation repositories remain upstream and are linked from each record. extensions/openmausbot/ keeps Skill references, scripts, assets, and other attachments as real files. The build generates src/data/catalog.json, validated against centralized schemas in schemas/. Fetch scripts, failed exports, logs, and redundant catalog snapshots are excluded.
There is one current state per extension. Update it in place through a pull request; Git preserves the history.
GitHub Actions validates every pull request and main-branch update. A successful push to main deploys the same tested dist/ artifact to Cloudflare Workers Static Assets, followed by production smoke checks. Pull requests never deploy.
Configure the repository secret CLOUDFLARE_API_TOKEN and variable CLOUDFLARE_ACCOUNT_ID. Use an account-owned token with Individual Workers Editor access to bot-extensions only; no KV, R2, D1, or zone permissions are required. See deployment and token rotation.
wrangler.jsonc defines the static site. For a manual deployment, run pnpm build && pnpm run deploy with appropriate Cloudflare credentials.
Start with CONTRIBUTING.md. Pull requests should contain only the extension files, normalized catalog changes when applicable, and relevant tests or documentation—never raw export logs, temporary snapshots, credentials, or scraping output.