Skip to content
TrustedSkillsbeta
Back to all skills

Fe Debug

Checked
ingpdw·vlatest·testing·MIT

Quickly identifies and suggests fixes for frontend errors in web applications using automated analysis and code inspection.

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 ingpdw/pdw-fe-dev-tool --skill fe-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

ingpdw

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 ingpdw/pdw-fe-dev-tool at 6bd6f544c0.

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

Commit
6bd6f544c0
Manifest
plugins/pdw-fe-dev-tools/skills/fe-debug/SKILL.md
Scanned
1 file, 396 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

The fe-debug skill assists with front-end development debugging. It can help identify and resolve issues in JavaScript, CSS, and HTML code. This tool provides insights into the application's state and behavior to facilitate faster troubleshooting and improved code quality.

When to use it

  • When encountering unexpected behavior or errors in a web application.
  • During the development process to quickly pinpoint and fix bugs.
  • To understand the current state of variables, DOM elements, or network requests within an application.
  • While troubleshooting performance bottlenecks in front-end code.

Key capabilities

  • Debugging JavaScript code
  • Inspecting CSS styles
  • Examining HTML structure
  • Analyzing network requests

Example prompts

  • "Debug this JavaScript function and tell me why it's not working."
  • "Show me the current CSS applied to this element."
  • "What is the value of this variable at this point in execution?"
  • "Inspect the network request for this API endpoint."

Tips & gotchas

This skill requires a running front-end application or code snippet to debug. The effectiveness depends on the clarity and context provided within the prompt.