chrome-devtools-mcp launcher — a single bash script that resolves Playwright's bundled Chrome-for-Testing and Node.js directly through Nix. See repo README for usage, override mechanisms, and version compatibility.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
Drop-in launcher for the Chrome DevTools MCP server. Self-contained — bin/serve resolves all inputs via nix build / nix shell.
Full docs in the repo README.
This skill primitive exists for APM's deployment convention — it ensures bin/serve lands at .agents/skills/nix-chrome-devtools-mcp/bin/serve in the consumer's working tree (per APM's skills convergence path), which keeps the launcher available even before apm install runs on a fresh clone. The package is mechanically a "skill" in APM's primitive vocabulary; semantically it's a tool.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Reference for the `odu` runner — how to invoke a full pipeline, a single recipe, or a platform-pinned node, and how to attach to a live run, from a project whose CI odu runs. Trigger when the user asks to "run CI", "run the pipeline", "re-run a check", or names a specific recipe by `<recipe>@<platform>`.
The English summary is being prepared. Showing the original description.
Review code for quality, simplicity, and common mistakes before declaring work complete.
The English summary is being prepared. Showing the original description.
Do a task end-to-end — implement, PR, CI loop, ship. ONLY invoke when the user explicitly types `/do` or `$do`; never auto-select from a natural-language request, even one that sounds like an end-to-end task.
The English summary is being prepared. Showing the original description.
Iteratively study and apply elegant coding patterns. Each iteration - understand the code, research what simple and elegant code looks like, apply learnings, verify with CI. Use as a standalone refactoring pass or when the user asks to make code more elegant, simple, or idiomatic.
The English summary is being prepared. Showing the original description.
Audit code for correctness and rigor — logic errors, silent error swallowing, wishful thinking, and unjustified fallbacks. This is not a style review; it's a logic review. Use when you want a focused correctness audit separate from the full code-police pass.
The English summary is being prepared. Showing the original description.
Write engaging PR titles and descriptions for any forge (GitHub today; Bitbucket planned). Use when creating or updating PRs. Leads with narrative paragraphs and reaches for lists, tables, and diagrams when content is genuinely structured.
The English summary is being prepared. Showing the original description.