Skip to content

Adonis0123/adonis-skills / skills/chrome-dev-mcp

chrome-dev-mcp

Verified

Use this skill when the user invokes /chrome-dev-mcp or asks for Chrome DevTools MCP, CDP, list_pages/select_page, UXC packaging for Chrome DevTools, DOM snapshots, Console, Network, Performance, Lighthouse, heap analysis, browser-internal debugging, connection recovery, or correct-Chrome validation across Claude Code, Codex, Grok Build/Grok002, Cursor CLI, Hermes, or WorkBuddy. Use it when the evidence is Chrome-specific (Lighthouse, a full trace, heap data) or the caller has no page session yet; a page already open in ego-browser keeps its own Console and request diagnosis. Also use it as the verification step right after the user or this session changes a web UI or asks to accept or check a page: collect a screenshot, Console, and Network evidence before calling it done. Do not use it for ordinary navigation, form filling, scraping, or desktop UI unless browser-internal signals or UI-change acceptance are required. A passing readiness or list_pages check proves the connection only, never the change.

scripts/test/readiness-envelope.test.mjs

View on GitHub
import { test } from "node:test";
import assert from "node:assert/strict";
import { execFileSync } from "node:child_process";
import { mkdtempSync, rmSync, writeFileSync } from "node:fs";
import { tmpdir } from "node:os";
import { dirname, join } from "node:path";
import { fileURLToPath } from "node:url";

const lib = join(
  dirname(fileURLToPath(import.meta.url)),
  "..",
  "lib",
  "readiness-envelope.zsh",
);

function classify(stdout, { stderr = "", exitCode = 0 } = {}) {
  const dir = mkdtempSync(join(tmpdir(), "cdm-envelope-"));
  try {
    const out = join(dir, "stdout");
    const err = join(dir, "stderr");
    writeFileSync(
      out,
      typeof stdout === "string" ? stdout : JSON.stringify(stdout),
    );
    writeFileSync(err, stderr);
    return execFileSync(
      "/bin/zsh",
      [
        "-c",
        'source "$1"; chrome_dev_mcp_classify_readiness "$2" "$3" "$4"',
        "classify",
        lib,
        out,
        err,
        String(exitCode),
      ],
      { encoding: "utf8" },
    ).trim();
  } finally {
    rmSync(dir, { recursive: true, force: true });
  }
}

const endpoint = "/opt/example/scripts/chrome-devtools-mcp-safe";
const envelope = (data, extra = {}) => ({
  ok: true,
  kind: "call_result",
  protocol: "mcp",
  endpoint,
  operation: "list_pages",
  data,
  ...extra,
});

test("healthy list_pages envelope is OK", () => {
  assert.equal(
    classify(
      envelope({
        content: [{ type: "text", text: "## Pages\n1: about:blank" }],
      }),
    ),
    "OK",
  );
});

test("ok=true with data.isError is not readiness", () => {
  const data = {
    content: [
      {
        type: "text",
        text: "Could not connect to Chrome. Check if Chrome is running.",
      },
    ],
    isError: true,
  };
  assert.equal(classify(envelope(data)), "chrome_unreachable");
});

test("other tool-level errors are tool_error, not wrapper_fail_closed", () => {
  assert.equal(
    classify(
      envelope({
        content: [{ type: "text", text: "Error: boom" }],
        isError: true,
      }),
    ),
    "tool_error",
  );
});

test("exclusive key conflict is classified separately", () => {
  const stdout = {
    ok: false,
    error: {
      code: "DAEMON",
      message:
        "Another MCP stdio session is currently using daemon exclusive key",
    },
  };
  assert.equal(classify(stdout, { exitCode: 1 }), "exclusive_key_busy");
});

test("wrong operation or non-zero exit is not OK", () => {
  assert.notEqual(
    classify(envelope({ content: [] }, { operation: "take_snapshot" })),
    "OK",
  );
  assert.notEqual(classify(envelope({ content: [] }), { exitCode: 2 }), "OK");
});

test("non-JSON output is parse_error", () => {
  assert.equal(classify("not json"), "parse_error");
});
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall