Skip to content
TrustedSkillsbeta
Back to all skills

Debug

Checked
gemini960114·vlatest·testing

Identifies and suggests fixes for code errors using advanced reasoning and debugging techniques.

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 gemini960114/skills --skill 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

gemini960114

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 gemini960114/skills at d78152f385.

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

Scanned
1 file, 213 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 allows an AI agent to systematically identify and report errors or unexpected behavior in its own processes. It can analyze the steps taken, pinpoint the source of a problem, and suggest potential solutions for improved performance or accuracy. The debug skill helps agents become more reliable by proactively addressing internal issues.

When to use it

  • When an AI agent consistently produces incorrect outputs despite clear instructions.
  • To diagnose why an agent is failing to complete a complex task successfully.
  • During development and testing of new AI agent workflows, to quickly identify and resolve bugs.
  • When an agent's behavior deviates from expected patterns or exhibits signs of instability.

Key capabilities

  • Error analysis
  • Step-by-step process review
  • Root cause identification
  • Solution suggestion

Example prompts

  • "Debug my last response and explain why it was incorrect."
  • "Trace the steps you took to generate [specific output] and identify any potential errors."
  • "I'm consistently getting error X. Can you analyze your process and suggest a fix?"

Tips & gotchas

The effectiveness of this skill depends on the agent having sufficient internal logging or observability capabilities. Without access to its own operational data, the debug skill will be limited in what it can identify.