Skip to content
TrustedSkillsbeta
Back to all skills

Debugging

Checked
sipengxie2024·vlatest·testing·MIT

Automated debugging assistance leveraging code analysis and error pattern recognition for faster issue resolution.

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 sipengxie2024/superpower-planning --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

sipengxie2024

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 sipengxie2024/superpower-planning at 91d7173db7.

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

Commit
91d7173db7
Manifest
skills/debugging/SKILL.md
Scanned
6 files, 871 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, authored by sipengxie2024, provides debugging capabilities for AI agents. It allows users to identify and resolve issues within agent workflows or code. The specific functionality isn't detailed in the provided source, but its purpose is to improve the reliability and performance of AI agents.

When to use it

  • When an AI agent consistently produces incorrect or unexpected results.
  • During development to quickly pinpoint and fix errors in agent logic.
  • After a significant update or modification to an agent’s code base.
  • To troubleshoot performance bottlenecks within an agent's execution.

Key capabilities

  • Debugging
  • Error identification
  • Issue resolution

Example prompts

  • "Debug the following Python script: [script content]"
  • "I am getting unexpected results from my AI agent, can you help me debug it?"
  • "Analyze this agent's workflow and identify any potential errors."

Tips & gotchas

The specific debugging methods used by this skill are not detailed. Providing clear and concise information about the problem or code being debugged will likely yield better results.