Create deno.yml

[LVLUP-tech]

📕 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 the PR — and for taking an interest in the repo!

I have to decline this one, and here's the honest reason: GrokBotDev is an Astro + npm site, not a Deno project, so a Deno CI workflow has nothing to run against. Concretely:

• No deno.json / deno.lock, no Deno dependencies, no *_test.ts files anywhere in the tree — deno lint and deno test -A would both fail on every push, giving us a permanently red check.
• CI is already covered by .github/workflows/ci.yml (validate + build + link/contrast/keyword gates) and merge-gate.yml, which is what actually protects main.

This is also GitHub's stock deno.yml starter template verbatim rather than something adapted to this codebase, and none of the checklist boxes are ticked — so it reads like an accidental or exploratory PR rather than an intended change. Totally fine either way, it just isn't mergeable as-is.

If you'd like to contribute, the good path is a listing: a plugin, a use case, or (via the /submit/ form) a Shareable Bot template. CONTRIBUTING.md walks through every field and the quality bar, and a real entry — a bot you built and actually use — is exactly what we're here for. Happy to review that.