Announcing OpenCode School!
A free, self-paced course that teaches you how to use OpenCode, the open-source AI coding agent.
No account required. No personal data collected. Free forever.
https://t.co/I6O2k1bXCn
@jamesqquick it creates the workflow files, guides you through creating cloudflare api tokens if needed, configures secrets on the repo with the gh cli, etc
It uses GitHub Actions and the GitHub Deployments API to automatically create preview deployments whenever you open a pull request, and tear them down when you merge or close the PR.This allows you to test your changes in a live environment before shipping them to production.
I made this a skill because there's some nuance to getting these workflows right, and I do it often enough that I want to make the process repeatable.
Try it out and let me know if you hit any snags!
This might help (in the Cloudflare Browser Run case, at least):
> WebMCP requires Chrome beta features. We have an experimental pool with browser instances running Chrome beta so you can test emerging browser features before they reach stable Chrome. To start a WebMCP session, add lab=true to your /devtools/browser request.
https://t.co/4UHb3VbapK
Any WebMCP experts out there?
I'm trying to get agents to reliably auto-detect the presence of WebMCP support in my app, but they generally don't notice or use it unless I specifically mention it in my user prompt like "... and use WebMCP pretty please."
I've added content to the page, adding a console.log message, screen reader notes, and of course populating the `document.modelContext` object, but those aren't doing the trick.
Any ideas?
@mattzcarey Haha you mean the CLI over MCP thing? Yeah. Hot take.
I'm just noticing personally that gh, glab, and a handful of skills are slowly taking over what used to be a config full of MCP servers.
CLI > MCP
This thing actually works, and it's noticeably faster!
Yank the old Chrome Devtools MCP config out of your agent's JSON file and use this instead:
npx skills add zeke/faster-chrome-devtools-skill --global --all --yes
⚡️🐌⚡️ The Faster Chrome DevTools Skill is now even faster.
Instead of using DevTools MCP and the Puppeteer runtime, it now bundles a dependency-free Node.js client that speaks Chrome DevTools Protocol (CDP) directly over WebSocket.
Thanks to @mattzcarey for this awesome improvement! 🧡
Check it: https://t.co/IO3XHhRIzN
⚡️🐌⚡️ The Faster Chrome DevTools Skill is now even faster.
Instead of using DevTools MCP and the Puppeteer runtime, it now bundles a dependency-free Node.js client that speaks Chrome DevTools Protocol (CDP) directly over WebSocket.
Thanks to @mattzcarey for this awesome improvement! 🧡
Check it: https://t.co/IO3XHhRIzN
Why a CLI instead of an MCP server?
1. Works anywhere. Any agent with a shell can use it. No MCP server to configure.
2. Full CDP protocol. MCP has high-level tools plus JS eval, but the CLI can call any Chrome DevTools method.
3. Leaner context. No more loading always-on tool schemas; the skill loads on demand and runs through your agent's shell.
4. No screenshot bloat. MCP inlines screenshots into model context, but the CLI writes them to a file and returns the path.
Notebook LM has gotten really good.
Dump a bunch of context into the chat, then generate a podcast, video, quiz, flash cards, etc.
And now there's a mobile app too.
And it's free.
https://t.co/f4Qfbu0vmE