Debugging Guide

    1

    An evidence-based debugging assistant that tracks hypotheses and isolates root causes in web applications.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Debugging Guide

    Example session with this skill installed

    My React app's login works locally but fails on staging with a 401. I've checked the API keys. Help me debug this.

    • Read your context and instructions
    • Compiled the debugging guide

    I have reviewed the reported 401 error on staging versus the local success. Since API keys are verified, we need to distinguish between session configuration and environment-specific headers.

    Investigation Status

    IDPossible CauseSupporting EvidenceConflicting EvidenceNext CheckStatus
    H1Missing CORS/Origin401 on cross-origin requestWorks locally (same-origin)Check Access-Control-Allow-OriginOpen
    H2Secure Cookie mismatchStaging uses HTTPSLocal uses HTTPInspect cookie Secure flagSupported
    H3Path/Domain mismatch401 implies no sessionAPI keys verifiedCheck Set-Cookie header pathOpen

    The evidence shows that the request reaches the server but fails authentication. We must determine if the session cookie is being sent by the browser or rejected due to attributes.

    Next Check (Proposed)
    Inspect the Network tab in your browser for the failed staging request. Look at the Request Headers and tell me:

    1. Is a Cookie header present in the request?
    2. In the Response Headers of the previous login attempt, what are the SameSite and Secure attributes of the Set-Cookie header?

    This will distinguish between a failure to store the session (H2) and a failure to send it due to origin policy (H1).

    Next steps

    • Provide the Set-Cookie attributes from the staging login response.
    • Confirm if the staging API is on a different subdomain than the frontend.
    • Share a redacted snippet of your session configuration code.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    When a web application breaks, the default response is often a cycle of guessing and "shotgun debugging" that leads to bloated code and phantom fixes. This skill enforces an evidence-based investigation workflow to isolate the root cause without touching production or risking data loss.

    What it does

    • Symptom isolation captures expected versus actual behavior and reproduction steps to define the problem scope.
    • Evidence tracking separates code-backed facts and logs from user observations to avoid bias.
    • Hypothesis management maintains a register of possible causes, supporting evidence, and conflicting data points.
    • Diagnostic selection proposes the lowest-impact check to distinguish between competing mechanisms.
    • Verification planning provides minimal, targeted fixes with specific regression test instructions.

    How it works

    1. Establishment: The agent queries the current environment, recent changes, and reproduction steps.
    2. Analysis: It reads entry points and handlers to map the execution path and identify potential failure points.
    3. Investigation: It presents a hypothesis table and asks the user to perform a specific, non-destructive check.
    4. Resolution: Once evidence isolates a cause, it proposes a minimal fix and a verification method.

    Frameworks & tools

    This skill is framework-agnostic and works with any web stack. It relies on standard diagnostic artifacts like status codes, header presence, error logs, and stack traces.

    Why this beats prompting it yourself

    Generic prompts often jump to "plausible" solutions that do not actually match the evidence. This skill uses a structured investigation guide to prevent "reproduction by assertion" and ensures that every proposed fix is backed by a confirmed, isolated cause.

    Use cases

    • Debugging intermittent session or authentication failures across different environments.
    • Investigating silent failures where a component runs but produces no output or incorrect state.
    • Conducting a handoff-ready investigation for complex bugs that require team review.
    • Identifying why a specific route or event wiring is failing despite "correct" logic.

    Known limitations

    Does not perform production mutations, database resets, or deployments. Requires the user to provide sanitized logs and snippets; it cannot autonomously access restricted or secret files.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Testing & Debugging.

    No production mutations or DB resets. Requires user-provided sanitized logs. Cannot bypass file access restrictions or handle secrets.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 11 days ago

    • Free with an Agensi account

    Permissions

    Read Files
    Write Files
    Listed11 days ago

    What's inside

    Frequently Asked Questions

    This skill replaces trial-and-error "shotgun debugging" with a structured, evidence-based workflow that tracks hypotheses and isolates root causes using diagnostic facts rather than guesses.

    The skill is framework-agnostic and works with any web stack (React, Node.js, Python, PHP, etc.) as long as you can provide standard artifacts like logs, stack traces, and network headers.

    No, this skill is designed for safe investigation; it proposes targeted fixes and diagnostic checks for you to execute, ensuring no unauthorized mutations occur in your production environment.

    You receive the complete structured debugging workflow and logic, including the hypothesis management system and diagnostic selection protocols compatible with your AI agent platform.

    Because it relies on your input of logs and snippets rather than direct server access, it works seamlessly with both local development environments and restricted enterprise setups.

    New in Testing & Debugging

    Free