Skip to content
TrustedSkillsbeta
Back to all skills

Chrome Debug

Checked
akornmeier·vlatest·testing

Automates Chrome browser debugging tasks, streamlining testing workflows with akornmeier's specialized scripts.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add akornmeier/claude-config --skill chrome-debug -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

akornmeier

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned akornmeier/claude-config at a4a955d68c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
a4a955d68c
Manifest
skills/chrome-debug/SKILL.md
Scanned
1 file, 71 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill, akornmeier-chrome-debug, allows AI agents to debug Chrome browser instances. It provides capabilities to inspect elements, view console logs, and step through code within a controlled Chrome environment. This is particularly useful for testing web applications or diagnosing issues within browser extensions.

When to use it

  • Debugging Web Applications: Use this skill when an agent needs to troubleshoot errors or unexpected behavior in a web application running inside Chrome.
  • Testing Browser Extensions: If your AI agent interacts with or develops browser extensions, this skill can help debug their functionality.
  • Automated Testing: Integrate the debugging capabilities into automated testing workflows for web-based projects.
  • Reproducing User Issues: Agents can use it to recreate and diagnose user-reported issues within a Chrome environment.

Key capabilities

  • Chrome browser instance control
  • Element inspection
  • Console log viewing
  • Code stepping

Example prompts

  • "Debug the JavaScript code running on this webpage."
  • "Inspect the element with ID 'myButton' in the Chrome window."
  • "Step through the execution of the calculateTotal function."

Tips & gotchas

  • Requires a Chrome browser to be installed and accessible.
  • The agent needs appropriate permissions to control the Chrome instance.