LangBot Plugin Development
langbot-app/LangBot
Guides building, debugging and testing LangBot plugins: components, SDK calls, README and locale rules, SDK pitfalls and WebSocket-based testing.
Systematic approach to diagnosing and fixing errors. An agent skill from vstorm-co/pydantic-deepagents.
Install Systematic Debugging
$ npx skills add vstorm-co/pydantic-deepagents --skill systematic-debugging -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vstorm-co/pydantic-deepagents systematic-debugging --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vstorm-co/pydantic-deepagents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/apps/cli/skills/systematic-debugging .claude/skills/systematic-debugging && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "systematic-debugging" agent skill from https://github.com/vstorm-co/pydantic-deepagents/tree/main/apps/cli/skills/systematic-debugging into .claude/skills/systematic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systematic-debugging", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vstorm-co/pydantic-deepagents/tree/main/apps/cli/skills/systematic-debuggingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vstorm-co/pydantic-deepagents --skill systematic-debugging -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vstorm-co/pydantic-deepagents systematic-debugging --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vstorm-co/pydantic-deepagents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/apps/cli/skills/systematic-debugging .agents/skills/systematic-debugging && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "systematic-debugging" agent skill from https://github.com/vstorm-co/pydantic-deepagents/tree/main/apps/cli/skills/systematic-debugging into .agents/skills/systematic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systematic-debugging", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vstorm-co/pydantic-deepagents --skill systematic-debugging -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vstorm-co/pydantic-deepagents systematic-debugging --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vstorm-co/pydantic-deepagents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/apps/cli/skills/systematic-debugging .cursor/skills/systematic-debugging && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "systematic-debugging" agent skill from https://github.com/vstorm-co/pydantic-deepagents/tree/main/apps/cli/skills/systematic-debugging into .cursor/skills/systematic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systematic-debugging", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vstorm-co/pydantic-deepagents.git --path apps/cli/skills/systematic-debugging--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vstorm-co/pydantic-deepagents --skill systematic-debugging -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vstorm-co/pydantic-deepagents systematic-debugging --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vstorm-co/pydantic-deepagents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/apps/cli/skills/systematic-debugging .gemini/skills/systematic-debugging && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "systematic-debugging" agent skill from https://github.com/vstorm-co/pydantic-deepagents/tree/main/apps/cli/skills/systematic-debugging into .gemini/skills/systematic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systematic-debugging", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vstorm-co/pydantic-deepagents systematic-debuggingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vstorm-co/pydantic-deepagents --skill systematic-debugging -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vstorm-co/pydantic-deepagents.git skills-src && mkdir -p .github/skills && cp -r skills-src/apps/cli/skills/systematic-debugging .github/skills/systematic-debugging && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "systematic-debugging" agent skill from https://github.com/vstorm-co/pydantic-deepagents/tree/main/apps/cli/skills/systematic-debugging into .github/skills/systematic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systematic-debugging", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vstorm-co/pydantic-deepagents --skill systematic-debugging -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vstorm-co/pydantic-deepagents systematic-debugging --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vstorm-co/pydantic-deepagents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/apps/cli/skills/systematic-debugging .opencode/skills/systematic-debugging && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "systematic-debugging" agent skill from https://github.com/vstorm-co/pydantic-deepagents/tree/main/apps/cli/skills/systematic-debugging into .opencode/skills/systematic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systematic-debugging", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
systematic-debugging- GitHub stars
- 1.1k
- Token cost
- ~732 tokens
- SKILL.md length
- 383 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
Systematic approach to diagnosing and fixing errors. An agent skill from vstorm-co/pydantic-deepagents.
- Works in 5 steps: Reproduce → Isolate → Diagnose → …
- Tasks that involve Debugging
- SKILL.md covers The Debugging Loop, Step 1: Reproduce, Step 2: Isolate and Step 3: Diagnose, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Systematic Debugging is an agent skill from vstorm-co/pydantic-deepagents. Systematic approach to diagnosing and fixing errors
Its SKILL.md is about 730 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Debugging. It works with Python. The repository describes itself as: Open-source, self-hosted Claude Code - a terminal AI assistant and the Python framework behind it. Tool-calling, sandboxed execution, multi-agent teams, skills, checkpoints… The licence is MIT.
When your agent uses it
- Tasks that involve Debugging
Example prompts
- “/systematic-debugging”
Requirements
- Python 3
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 650b592. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Systematic Debugging loads about 732 tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 383 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from vstorm-co/pydantic-deepagents at commit 650b592, republished under its MIT licence (© vstorm-co). 383 words, ~732 tokens.
Download SKILL.mdSave it as
.claude/skills/systematic-debugging/SKILL.md (or your agent's skills folder).- name
- systematic-debugging
- description
- Systematic approach to diagnosing and fixing errors
- tags
- debugging, errors, benchmark
- version
- 1.0.0
Systematic Debugging
A structured approach to finding and fixing bugs.
The Debugging Loop
1. REPRODUCE → 2. ISOLATE → 3. DIAGNOSE → 4. FIX → 5. VERIFYNever skip steps. Never guess-and-check repeatedly.
Step 1: Reproduce
- Run the exact command that fails
- Capture FULL output (stdout AND stderr)
- Note: exit code, error message, stack trace
- If intermittent, identify what changes between runs
Step 2: Isolate
- What's the MINIMAL input that triggers the error?
- Which specific line/function fails? (read the traceback bottom-up)
- Is it a compile error, runtime error, or wrong output?
- Does it fail on all inputs or specific ones?
Step 3: Diagnose
Read the error message carefully
| Error type | Where to look |
|---|---|
| Compile error | The FIRST error (later ones are often cascading) |
| Segfault | Last function in the stack trace, check array bounds and null pointers |
| Python traceback | The innermost frame (bottom), but also check the middle for context |
| Wrong output | Diff expected vs actual: diff <(expected) <(actual) |
| Timeout/hang | Is it an infinite loop? Deadlock? I/O bound? Add a timer or counter |
Add minimal instrumentation
- C:
fprintf(stderr, "reached checkpoint %d\n", __LINE__); - Python:
print(f"DEBUG: {var=}", file=sys.stderr) - Check intermediate values, not just final output
- Remove debug prints after fixing
Step 4: Fix
- Change ONE thing at a time
- If the same approach fails 3 times → completely different strategy
- Don't add workarounds — fix the root cause
- Common root causes:
- Off-by-one errors (loop bounds, array indexing)
- Type mismatches (int vs float, signed vs unsigned)
- Encoding issues (UTF-8 vs bytes)
- Path errors (relative vs absolute, missing trailing slash)
- Race conditions (file not written yet, process not started)
Show full SKILL.md (135 more words)Show less
Step 5: Verify
- Run the same command that failed before
- Test with multiple inputs, not just the one that was failing
- Check edge cases: empty input, single element, very large input
- Run any existing test suite
Common Failure Patterns
"It compiles but gives wrong output"
- Print all intermediate values
- Compare with a known-correct reference implementation
- Check: integer overflow, floating point precision, endianness
"It works on small input but times out on large"
- Check algorithm complexity — O(n²) on 1M items = timeout
- Profile: which loop/function takes the most time?
- Restructure: hash maps, sorting, streaming
"It works locally but fails in the test"
- Check: absolute vs relative paths
- Check: different working directory
- Check: different input format than expected
- Read the test script to understand what it actually checks
© vstorm-co, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in apps/cli/skills/systematic-debugging of vstorm-co/pydantic-deepagents.
Open the folder on GitHubat commit 650b592
Compare with similar skills
Systematic Debugging next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Systematic Debugging this skillvstorm-co/pydantic-deepagents | 1.1k | — | ~732 | Automated safety check: Pass | MIT | |
| LangBot Plugin Developmentlangbot-app/LangBot | 18k | — | ~3.9k | Automated safety check: Pass | Apache-2.0 | |
| Python Performance Optimizationwshobson/agents | 40k | 13 repos | ~814 | Automated safety check: Pass | MIT | |
| Git History Bug Auditben-manes/caffeine | 18k | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| Keybase RPC Log Analysiskeybase/client | 9.3k | — | ~3k | Automated safety check: Pass | BSD-3-Clause | |
| The Art of Debuggingstas00/the-art-of-debugging | 1.7k | — | ~6.1k | Automated safety check: Notes | CC-BY-SA-4.0 |
Similar skills
Python Performance Optimization
wshobson/agents
Profiles slow Python code with cProfile and memory profilers, then applies targeted fixes for CPU, memory, I/O and query bottlenecks.
Git History Bug Audit
ben-manes/caffeine
Audits a module by walking its git history commit by commit, tracking unresolved issues forward, and reporting the ones that survive to HEAD as findings.
Keybase RPC Log Analysis
keybase/client
Captures a clean Keybase service log and analyzes it for redundant, duplicated or looping RPCs, then checks whether a caching fix reduced the calls.
The Art of Debugging
stas00/the-art-of-debugging
Condensed debugging method and tool recipes for Unix, Python and PyTorch programs: crashes, hangs, segfaults, wrong output, CUDA OOM, NaN values and slowness.
- Official
Adk Setup
google/adk-python
Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test…
More from vstorm-co/pydantic-deepagents
All 14 skills in this repoData Formats
vstorm-co/pydantic-deepagents
Working with diverse data formats: binary, text, structured, and custom
Diagram Design
vstorm-co/pydantic-deepagents
Best practices for creating research diagrams with Excalidraw MCP tools
Research Methodology
vstorm-co/pydantic-deepagents
Best practices for systematic research, source evaluation, and evidence gathering
Verification Strategy
vstorm-co/pydantic-deepagents
Thorough verification of completed work before declaring done
Environment Discovery
vstorm-co/pydantic-deepagents
Systematic exploration of unknown environments before starting work
Skill Creator
vstorm-co/pydantic-deepagents
Create new reusable skills from conversation context. An agent skill from vstorm-co/pydantic-deepagents.
Related
Works with
Categories
Questions about Systematic Debugging
What does Systematic Debugging do?
Systematic approach to diagnosing and fixing errors. An agent skill from vstorm-co/pydantic-deepagents. Systematic Debugging is an agent skill from vstorm-co/pydantic-deepagents.
When should I use Systematic Debugging?
Systematic Debugging fits situations like: tasks that involve Debugging.
How do I install Systematic Debugging in Claude Code?
Run `npx skills add vstorm-co/pydantic-deepagents --skill systematic-debugging -a claude-code`. Or copy the skill folder (apps/cli/skills/systematic-debugging in vstorm-co/pydantic-deepagents) into .claude/skills/systematic-debugging in your project. Claude Code loads it when a task matches its description.
How do I install Systematic Debugging in Codex?
Run `npx skills add vstorm-co/pydantic-deepagents --skill systematic-debugging -a codex`. Or copy the skill folder (apps/cli/skills/systematic-debugging in vstorm-co/pydantic-deepagents) into .agents/skills/systematic-debugging in your project. Codex loads it when a task matches its description.
Can I use Systematic Debugging in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vstorm-co/pydantic-deepagents --skill systematic-debugging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/systematic-debugging, .gemini/skills/systematic-debugging, .github/skills/systematic-debugging and .opencode/skills/systematic-debugging in your project.
What does Systematic Debugging need to run?
SKILL.md names no scripts, command-line tools or credentials: Systematic Debugging is instructions for the agent only. Our summary lists: Python 3.
Does Systematic Debugging access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Systematic Debugging safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Systematic Debugging use?
Systematic Debugging is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Systematic Debugging use?
About 732 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Systematic Debugging?
Skills that share tags, products or a category with Systematic Debugging: LangBot Plugin Development (langbot-app/LangBot, 18k stars), Python Performance Optimization (wshobson/agents, 40k stars), Git History Bug Audit (ben-manes/caffeine, 18k stars) and Keybase RPC Log Analysis (keybase/client, 9.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Systematic Debugging?
vstorm-co (a GitHub organization) maintains it in vstorm-co/pydantic-deepagents, which has 1,077 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 6, 2026.
Source: vstorm-co/pydantic-deepagents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.