browser-testing-with-devtools SKILL.md skillB

browser-testing-with-devtools from nota-america/forgecat-agent-profiles is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add nota-america/forgecat-agent-profiles/browser-testing-with-devtools@git:20260916.3a6b22e

Pins git:20260916.3a6b22e in mdr.lock. Pin the fingerprint instead.

Audit grade

B, 16 of 17 checks passed

Kind

SKILL.md skill

Repository

nota-america/forgecat-agent-profiles

Path

profiles/addyosmani/agent-skills/for-codex/.agents/skills/browser-testing-with-devtools/SKILL.md

Versions recorded

2

Latest version

git:20260916.3a6b22e, committed Sep 16, 2026

First version recorded

Jun 10, 2026

Size

14,539 bytes

Repository stars

93

License

Apache-2.0

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Browser Testing with DevTools

## Overview

Use Chrome DevTools MCP to give your agent eyes into the browser. This bridges the gap between static code analysis and live browser execution — the agent can see what the user sees, inspect the DOM, read console logs, analyze network requests, and capture performance data. Instead of guessing what's happening at runtime, verify it.

## When to Use

- Building or modifying anything that renders in a browser
- Debugging UI issues (layout, styling, interaction)
- Diagnosing console errors or warnings
- Analyzing network requests and API responses
- Profiling performance (Core Web Vitals, paint timing, layout shifts)
- Verifying that a fix actually works in the browser
- Automated UI testing through the agent

**When NOT to use:** Backend-only changes, CLI tools, or code that doesn't run in a browser.

## Setting Up Chrome DevTools MCP

### Installation

Add the following to your project's `.mcp.json` or Claude Code settings:

```json
{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": ["-y", "chrome-devtools-mcp@latest", "--isolated"]
    }
  }
}
```
…

Read the whole file at its exact version.

How to install

mdr add nota-america/forgecat-agent-profiles/browser-testing-with-devtools@sha256:4e3aacd6a380cd25

[![mdr](https://markdownregistry.com/badge/art_js3wyv524lw673ei.svg)](https://markdownregistry.com/a/art_js3wyv524lw673ei)

Versions

The registry has recorded 2 versions of this file, between Jun 10, 2026 and Sep 16, 2026, about one every 98 days.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_js3wyv524lw673ei
GET https://markdownregistry.com/api/v1/resolve?ref=nota-america/forgecat-agent-profiles/browser-testing-with-devtools
GET https://markdownregistry.com/api/v1/blob/4e3aacd6a380cd25bc6c2d67fdd1c926a9b22535b8a62109ecd33cefd909e3d9

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from nota-america/forgecat-agent-profiles

Every file in nota-america/forgecat-agent-profiles

Other files named browser-testing-with-devtools

Browse by kind, by grade B, or by owner.