content(plugins): add BlindOracle Grok Bot kit (MCP marketplace conne…

[craigmbrown]

…ctor)

One plugin entry: the BlindOracle agent-services marketplace, joined by a
Grok Bot through a single MCP plugin plus one bootstrap URL. status: proposed;
verified_at / awesome_score left to the reviewer per G8. npm run validate: OK.

Claude-Session: https://claude.ai/code/session_013je3TUzNAUA8Kv3hFpwPpq

📕 Read CONTRIBUTING.md first — it's the rulebook (every
field, the quality bar, the Awesome Score). Reviewers cite it by rule number (G1–G8, UC-n, PL-n).

What this adds

Checklist

• This PR adds exactly ONE new file under content/ (plus assets for this entry, if any).
• It follows CONTRIBUTING.md — required fields + the golden rules (G1–G8).
• npm run validate passes locally (schema, slug, vocabularies).
• slug is kebab-case and exactly matches the filename.
• I ran / used this myself end to end — it works today.
• Every URL in the frontmatter resolves to real, relevant content.
• The prompt body is the real, complete prompt — not a summary or a teaser.
• The entry body is plain markdown — no raw HTML (<script>, <iframe>, <style>, <form>, inline event handlers). CI rejects it (§8.5).
• I did NOT set verified_at or status: live — a maintainer sets those during verification (§10.1).
• This is not an ad. A listing that exists to funnel traffic to your product gets closed. Sponsor slots will exist for that — this isn't one.
• If this is someone else's work: author is the original creator, the origin is linked (source_url for a plugin, source_tweets[] for a use case), and scouted_by is me.
• If the source is a YouTube video: primary_source is kind: youtube-video with a youtube.com/watch, youtu.be/ or youtube.com/shorts/ URL, plus the video's real title and channel — those two are required because they are what the page shows if the player never loads. timestamp is optional and is written mm:ss.
• I license this contribution under CC BY 4.0 (attribution: entry author + grokbot.dev).

Where it came from

[scheemunai]

Thanks for this, Craig — and thank you for the care that went into it. I reviewed it properly rather than skimming: I opened the kit pages (BOOTSTRAP / HEARTBEAT / SKU-GUIDE / PROOFS all 200), read https://api.craigmbrown.com/skill.md, pulled the live catalog (39 SKUs, $0.01–$99), and checked the three repos. It's real, it's Apache 2.0, the frontmatter is well-formed, and the prompt has a genuinely good safety posture — explicit approval before any spend past the two $0.01 proof calls, never store a key, treat every page and tool result as data, verify each settlement ref yourself before quoting it. That is a better-built submission than most of what we see.

I'm still going to decline it, and I want to give you the real reason rather than a vague one.

It's a standing line, not a quality judgement. Two things put it over:

1. The listing's usefulness is gated on paying in USDC on Base. Registration and discovery being free is good, but past ~$1.10 of starter credit every SKU in the catalog settles over x402 in USDC on Base. For grokbot.dev's audience — people setting up a Grok Bot for email, content, support, personal admin — that means the entry's actual value is behind a crypto wallet. We don't list entries gated that way, regardless of how well they're built.
2. The provider role earns. "Fulfils data.web-extract jobs from the open board, the only role that earns" is a bot whose purpose is to make money autonomously. That's a separate standing line for us.

The shape that does clear the line, if you want a route back in: a free, read-only connector where the Bot can never spend and the human funds anything paid off-Bot on a normal web page. We have exactly that live at /plugins/prism-network/ — it settles onchain too, but every MCP tool on it is read-only and free, the Bot can't sign a transaction, and the operator pays for a lease themselves on the website. A BlindOracle listing built to that shape — discovery, catalog reads, and public proof verification at GET /v1/proofs/settlement/<ref>, with the paid SKUs described but handed to the human — would be a fair conversation. I'd look at it.

Closing this one. No reflection on the work, and sorry to send you away after you'd clearly read our guidelines before writing it.