agentsclimarketplace
Sign in

Python debugger

Skill xcl1989/CrabAgent/src/crabagent/skills/python-debugger

Systematically debug Python code using structured error analysis, logging inspection, and test-driven fixesFrom its SKILL.md

Install
npx -y skills add xcl1989/CrabAgent --skill python-debugger

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.6 KB, 344 tokens by cl100k_base, as published. Nobody here has run it

Python Debugger Skill

You are now operating with the Python Debugger skill. Follow this systematic approach when debugging Python code.

Debugging Workflow

Step 1: Reproduce the Error

  • Run the failing code or test to confirm the error
  • Capture the full traceback
  • Identify the exact line and error type

Step 2: Analyze the Error

  • Read the error message carefully
  • Check the types of variables involved
  • Look at the call stack to understand the flow
  • Use read to examine the relevant source files

Step 3: Hypothesize

  • Form a hypothesis about the root cause
  • Consider common Python pitfalls:
    • Mutable default arguments
    • Off-by-one errors
    • Incorrect indentation
    • Type mismatches
    • Import circular dependencies
    • Missing self parameter
    • Incorrect exception handling

Step 4: Verify and Fix

  • Use bash to run targeted tests
  • Use edit to apply the fix
  • Run tests again to confirm the fix
  • Check for regressions in related tests

Step 5: Validate

  • Run the full test suite if available
  • Check edge cases
  • Ensure no new warnings are introduced

Tools Priority

  1. bash - Run code and tests to reproduce/verify
  2. read - Examine source files and tracebacks
  3. grep - Search for patterns across the codebase
  4. edit - Apply fixes

Common Patterns

See references/common-fixes.md for a catalog of common Python bugs and their fixes.

What ships with it: 1 file

980 B alongside SKILL.md

references/

Gives 0 of the 12 instructions most debug triage skills give in 344 tokens

Counted across 839 of the 1,149 authors here whose files we hold, read 2026-08-07

  • Investigate root cause before proposing any fixin 102 of 839, across 67 files
  • Read error messages completelyin 89 of 839, across 49 files
  • Create a failing test case before fixingin 84 of 839, across 46 files
  • Reproduce the issue consistentlyin 82 of 839, across 41 files
  • Change one variable at a timein 82 of 839, across 42 files
  • Check recent changesin 74 of 839, across 36 files
  • Write the regression test before fixingin 74 of 839, across 40 files
  • Fix the root cause not the symptomin 60 of 839, across 45 files
  • Implement a single fix at a timein 59 of 839, across 20 files
  • Trace data flow backward to the sourcein 50 of 839, across 20 files
  • Remove all debug instrumentationin 49 of 839, across 13 files
  • Form a single hypothesisin 48 of 839, across 18 files

Said here and by no other author read

  • examine the relevant source files
  • run targeted tests

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,629. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.