Skip to content
TrustedSkillsbeta
Back to all skills

Debug

Checked
parcadei·vlatest·testing·MIT

Automatically identifies and suggests fixes for common errors in Parcadei game code during development.

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 parcadei/continuous-claude-v3 --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

parcadei

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 parcadei/continuous-claude-v3 at d07ff4b06b.

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

Commit
d07ff4b06b
Manifest
.claude/skills/debug/SKILL.md
Scanned
1 file, 174 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

The parcadei-debug skill enables AI agents to perform deep diagnostic analysis on codebases, specifically leveraging the Continuous Claude v3 architecture. It allows agents to identify root causes of failures, trace execution paths, and suggest targeted fixes based on real-time context.

When to use it

  • You need to diagnose why a recent deployment failed in production without access to logs.
  • An AI agent is stuck in an infinite loop or producing repetitive errors during development.
  • You want an automated system to analyze complex dependency conflicts before they break builds.
  • You require detailed tracebacks for obscure runtime exceptions that standard linters miss.

Key capabilities

  • Executes deep diagnostic routines powered by Continuous Claude v3.
  • Analyzes code structure to pinpoint logical errors and performance bottlenecks.
  • Generates actionable debugging reports with suggested remediation steps.
  • Integrates seamlessly into existing CI/CD pipelines for automated testing.

Example prompts

  • "Run a full diagnostic on the authentication module; I'm getting 503 errors intermittently."
  • "Analyze this stack trace and explain why the database connection is timing out."
  • "Debug the infinite loop in the data processing script and provide a fix."

Tips & gotchas

Ensure your codebase has sufficient context available for the AI to correlate errors with specific functions. This skill works best when paired with detailed error logs, as vague descriptions may limit the diagnostic accuracy of the Continuous Claude v3 engine.