Skip to content
TrustedSkillsbeta
Back to all skills

Fullstack Debugger

Listed
curiositech·vlatest·testing·MIT

Rapidly identifies and fixes full-stack application errors using advanced AI analysis and automated debugging 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 curiositech/some_claude_skills --skill fullstack-debugger -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

curiositech

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 4 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: api.cloudflare.com, jb4l-meeting-proxy.erich-owens.workers.dev, jbuds4life.pages.dev, site.com.

    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.

    Hosts contacted

    api.cloudflare.comundeclaredsite.comundeclaredjbuds4life.pages.devundeclaredjb4l-meeting-proxy.erich-owens.workers.devundeclared

    What it found (3 of 9)

    • .claude/skills/fullstack-debugger/SKILL.md:302contacts api.cloudflare.com
      curl -X POST "https://api.cloudflare.com/client/v4/zones/ZONE_ID/purge_cache" \
    • .claude/skills/fullstack-debugger/references/error-patterns.md:232contacts api.cloudflare.com
      curl -X POST "https://api.cloudflare.com/client/v4/zones/ZONE/purge_cache" \
    • .claude/skills/fullstack-debugger/references/debug-decision-tree.md:23contacts site.com
      │   │       → Test: curl -H "Origin: https://site.com" <endpoint>

  • 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 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 curiositech/some_claude_skills at 6713fc7a64.

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

Commit
6713fc7a64
Manifest
.claude/skills/fullstack-debugger/SKILL.md
Scanned
8 files, 1,414 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 curiositech-fullstack-debugger skill assists in identifying and resolving issues across the full technology stack, from front-end to back-end. It provides detailed error analysis and suggests potential solutions based on code context and common debugging patterns. This skill is designed to streamline troubleshooting for developers of all levels.

When to use it

  • You're encountering a bug in a web application and need help pinpointing the root cause across multiple layers.
  • A user reports an error, and you require assistance in understanding the technical details of the problem.
  • You are debugging complex code interactions and want suggestions for potential fixes.
  • You’re facing performance bottlenecks and need to identify areas for optimization within your application's architecture.

Key capabilities

  • Full-stack error analysis
  • Code context awareness
  • Solution suggestion based on common debugging patterns
  • Performance bottleneck identification

Example prompts

  • "I'm seeing a 500 error on my website; can you help me debug it?"
  • "Analyze this code snippet and identify potential issues: [code snippet]"
  • "My application is slow; what are some possible performance bottlenecks I should investigate?"

Tips & gotchas

The skill's effectiveness relies heavily on providing sufficient context, including relevant code snippets and error messages. It may require iterative prompting to narrow down the issue effectively.