Skip to content
TrustedSkillsbeta
Back to all skills

Debug

Checked
iulspop·vlatest·testing

Identifies and suggests fixes for common errors in iulspop's generated code during testing cycles.

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 iulspop/aidd-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

iulspop

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 iulspop/aidd-skills at 6f8a5e303d.

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

Commit
6f8a5e303d
Manifest
skills/debug/SKILL.md
Scanned
1 file, 28 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 iulspop-debug skill provides debugging capabilities for AI agents. It allows you to inspect the agent's internal state, including variables and memory, during execution. This is useful for understanding why an agent made a particular decision or identifying errors in its logic.

When to use it

  • Troubleshooting unexpected behavior: If your agent isn’t performing as expected, use this skill to examine its intermediate steps.
  • Understanding complex reasoning chains: When an agent is following a multi-step process, debug can help you see the data and logic at each stage.
  • Validating internal state: Confirm that variables hold the values you anticipate during execution.
  • Identifying memory leaks or incorrect data handling: Inspect the agent’s memory to detect potential issues with data management.

Key capabilities

  • Inspect agent's internal state
  • Examine variables and memory
  • Trace reasoning steps

Example prompts

  • "Debug step 3 of the current task."
  • "Show me the value of 'current_location'."
  • "What was in memory at the last decision point?"

Tips & gotchas

This skill requires a good understanding of the agent's internal workings to effectively interpret the debugging information. It is most effective when used with agents that have detailed logging or state tracking enabled.