Skip to main content
ZICQ

Skills ZICQ category:Agent Workflows browser-debugging

Browser Debugging

Debug client-side issues using browser developer tools. Identify JavaScript errors, styling issues, and performance problems in the browser.

535 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

Debug client-side issues using browser developer tools. Identify JavaScript errors, styling issues, and performance problems in the browser.

When to use it

](#when-to-use)

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Browser Debugging; Table of Contents; Overview; When to Use; Quick Start; Reference Guides.

File analysis

File analysis: besides SKILL.md, the body references references/browser-devtools-fundamentals.md, references/debugging-techniques.md, references/common-issues-solutions.md, references/performance-debugging.md. Those resources load on demand.

Browser DebuggingTable of ContentsOverviewWhen to UseQuick StartReference GuidesBest Practices✅ DO❌ DON'T

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
name
browser-debugging
description
Debug client-side issues using browser developer tools. Identify JavaScript errors, styling issues, and performance problems in the browser.
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.
Files referenced by the instructions · 4
  • references/browser-devtools-fundamentals.md
  • references/debugging-techniques.md
  • references/common-issues-solutions.md
  • references/performance-debugging.md

These paths are extracted from the text. Check the upstream package to verify the files exist.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "browser-debugging" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-658ffda472e73e97-Browser-Debugging.html
Save it as .cursor/skills/browser-debugging/SKILL.md or .claude/skills/browser-debugging/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/aj-geddes/useful-ai-prompts instead of creating only a SKILL.md.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/aj-geddes/useful-ai-prompts' --list

npx skills add 'https://github.com/aj-geddes/useful-ai-prompts' --skill 'browser-debugging'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout

name: browser-debugging description: > Debug client-side issues using browser developer tools. Identify JavaScript errors, styling issues, and performance problems in the browser.

Browser Debugging

Table of Contents

Overview

Browser debugging tools help identify and fix client-side issues including JavaScript errors, layout problems, and performance issues.

When to Use

  • JavaScript errors
  • Layout/styling issues
  • Performance problems
  • User interaction issues
  • Network request failures
  • Animation glitches

Quick Start

Minimal working example:

Chrome DevTools Tabs:

Elements/Inspector:
  - Inspect HTML structure
  - Edit HTML/CSS in real-time
  - View computed styles
  - Check accessibility tree
  - Modify DOM

Console:
  - View JavaScript errors
  - Execute JavaScript
  - View console logs
  - Monitor messages
  - Clear errors

Sources/Debugger:
  - Set breakpoints
  - Step through code
  - Watch variables
  - Call stack view
  - Conditional breakpoints

Network:
  - View all requests
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

| Guide | Contents | |---|---| | Browser DevTools Fundamentals | Browser DevTools Fundamentals | | Debugging Techniques | Debugging Techniques | | Common Issues & Solutions | Common Issues & Solutions | | Performance Debugging | Performance Debugging |

Best Practices

✅ DO

  • Follow established patterns and conventions
  • Write clean, maintainable code
  • Add appropriate documentation
  • Test thoroughly before deploying

❌ DON'T

  • Skip testing or validation
  • Ignore error handling
  • Hard-code configuration values

Related skills

Agent Workflows

Skill Creator

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that exte…

Agent Workflows

Clawdhub

Use the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. Use when you need to fetch new skills on the fl…

Agent Workflows

Agent Team Orchestration

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team …

Agent Workflows

Superpowers

Spec-first, TDD, subagent-driven software development workflow. Use when: (1) building any new feature or app — triggers brainstorm → plan →…