Skip to content
TrustedSkillsbeta
Back to all skills

Systematic Debugging

Checked
guanyang·vlatest·testing·MIT

Systematically identifies and isolates software bugs using guided analysis and automated reproduction techniques.

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 guanyang/open-agent-hub --skill systematic-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

guanyang

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 guanyang/antigravity-skills at 0d6f1e7d3f.

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

Commit
0d6f1e7d3f
Manifest
skills/systematic-debugging/SKILL.md
Scanned
11 files, 1,214 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 enables AI agents to perform methodical, step-by-step debugging of code or system processes. It helps identify root causes of errors by analyzing logs, stack traces, and execution flows rather than guessing solutions.

When to use it

  • You encounter unexpected runtime errors that standard error messages do not explain clearly.
  • A complex script fails intermittently under specific data conditions or environments.
  • You need to isolate whether a bug lies in logic, configuration, or external dependencies.
  • Automated tests are failing, and you require a structured approach to pinpoint the failure source.

Key capabilities

  • Systematic analysis of error logs and stack traces.
  • Step-by-step execution flow tracing.
  • Identification of logical inconsistencies or missing configurations.
  • Generation of targeted hypotheses for root causes.

Example prompts

  • "Run a systematic debug on this failing Python script and explain the root cause."
  • "Analyze these server logs step-by-step to find why the API returns 500 errors."
  • "Debug this intermittent failure in my data pipeline by tracing the execution flow."

Tips & gotchas

Ensure you provide complete error messages, relevant code snippets, or log excerpts for accurate analysis. This skill works best when combined with clear context about the environment and expected behavior.