Home / shashankswe2020-ux / whoop-mcp · GitHub

browser-testing-with-devtools SKILL.md skillB

This file is byte-identical to the first copy the registry indexed, one of 3 indexed copies. Same content hash, so the same checks give both the same grade.

browser-testing-with-devtools from shashankswe2020-ux/whoop-mcp is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add shashankswe2020-ux/whoop-mcp/browser-testing-with-devtools@git:20260410.1a22ea0

Pins git:20260410.1a22ea0 in mdr.lock. Pin the fingerprint instead.

Audit grade: B, 16 of 17 checks passed
Kind: SKILL.md skill
Repository: shashankswe2020-ux/whoop-mcp
Path: .github/skills/browser-testing-with-devtools/SKILL.md
Versions recorded: 1
Latest version: git:20260410.1a22ea0, committed Apr 10, 2026
Size: 12,501 bytes
Repository stars: 176
License: MIT

Tests in real browsers. 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 via Chrome DevTools MCP.

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

```bash
# Add Chrome DevTools MCP server to your Claude Code config
# In your project's .mcp.json or Claude Code settings:
{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": ["@anthropic/chrome-devtools-mcp@latest"]
    }
  }
}
```

### Available Tools
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add shashankswe2020-ux/whoop-mcp/browser-testing-with-devtools@sha256:d50505e232bf61cd

The line at the top of this page pins the label git:20260410.1a22ea0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

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

5 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Apr 10, 2026.

version	committed	commit	size	audit
git:20260410.1a22ea0 latest	2026-04-10	1a22ea0	12,501 B	B	view

Audit of the latest version

B 16 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

fail: No prompt-injection phrasing (matched: Ignore previous instructions)
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (12501 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.

Source

GitHub

shashankswe2020-ux/whoop-mcp · 176 stars · license MIT · pushed 2026-10-30 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_zts2fhqdiij2y2kt
GET https://markdownregistry.com/api/v1/resolve?ref=shashankswe2020-ux/whoop-mcp/browser-testing-with-devtools
GET https://markdownregistry.com/api/v1/blob/d50505e232bf61cd51caf6d249a39e14451fea34ce1d5d064d944b6780d4f4e6

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 shashankswe2020-ux/whoop-mcp

api-and-interface-design SKILL.md skill

shashankswe2020-ux/whoop-mcp · .github/skills/api-and-interface-design/SKILL.md · Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when…