Skip to content
TrustedSkillsbeta
Back to all skills

Debugging

Checked
nmalinowski·vlatest·testing·MIT

Identifies and suggests fixes for code errors using nmalinowski's debugging expertise and best practices.

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 nmalinowski/groundwork --skill debugging -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

nmalinowski

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 nmalinowski/groundwork at 3db3f85bcf.

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

Commit
3db3f85bcf
Manifest
skills/debugging/SKILL.md
Scanned
2 files, 985 lines
Copies in repo
2 — all of them scanned
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 assists in identifying and resolving errors within code or processes. It can analyze error messages, suggest potential causes, and propose solutions to improve functionality. The tool aims to streamline the debugging process by providing targeted insights and guidance for developers and troubleshooters.

When to use it

  • When encountering unexpected behavior or errors in a program.
  • To understand complex error messages and their underlying causes.
  • For troubleshooting issues within automated workflows or scripts.
  • During code reviews to proactively identify potential bugs.

Key capabilities

  • Error message analysis
  • Root cause suggestion
  • Solution proposal
  • Troubleshooting guidance

Example prompts

  • "I'm getting a 'TypeError: undefined is not an object' error in my JavaScript code. Can you help me debug it?"
  • "This Python script is crashing with a traceback. What could be the problem?"
  • "Analyze this log file and identify any recurring errors or warnings."

Tips & gotchas

The skill’s effectiveness relies on providing clear and complete error messages or code snippets for analysis. It's best used in conjunction with standard debugging practices, as it provides suggestions rather than automated fixes.