systematic-debugging vs vendure-troubleshooting
systematic-debugging and vendure-troubleshooting are both agent skills for debugging. systematic-debugging is published by open-metadata and vendure-troubleshooting by vendurehq. Both install in Claude Code, Claude apps, Codex and Cursor. On GitHub, systematic-debugging has 15,567 stars and vendure-troubleshooting has 8,539. Both were last active in Oct 2026. The table lines up where they differ (publisher, GitHub stars and category) and has the install commands for both. Everything here comes from the listings' public sources and is refreshed daily. systematic-debugging describes itself as: Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. vendure-troubleshooting: Diagnose a broken or misbehaving Vendure project. Licenses: systematic-debugging Apache-2.0, vendure-troubleshooting unknown.
Updated Oct 26, 2026 · Built from catalog data; how we rank and grade
systematic-debugging
open-metadata
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious.
vendure-troubleshooting
vendurehq
Diagnose a broken or misbehaving Vendure project.
Who should pick which
- systematic-debugging and vendure-troubleshooting cover the same ground; the table shows where they differ.
From listing data only. We don't pick a winner on security beyond the grades; read how grades work.
Side by side
| Fact | systematic-debugging | vendure-troubleshooting |
|---|---|---|
| Type | Skill | Skill |
| Publisher | open-metadata | vendurehq |
| License | Apache-2.0 | License unknown |
| Pricing | free | free |
| Runs | Not stated | Not stated |
| Auth | Not stated | Not stated |
| Hosts supported | Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf | Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf |
| Tools | Not listed yet | Not listed yet |
| Security grade | –Security: not graded yet | –Security: not graded yet |
| Freshness grade | AFreshness: A | AFreshness: A |
| GitHub stars | 15,567 | 8,539 |
| Weekly downloads | Not measured | Not measured |
| Last release | Oct 21, 2026 | Oct 23, 2026 |
| Last activity | Oct 21, 2026 | Oct 23, 2026 |
Facts from each listing's public sources, checked daily. Tool lists arrive with tool scans.
Install
systematic-debugging
npx skills add open-metadata/OpenMetadata --skill systematic-debugging
Asks which agents to install it for (add -g for all projects). Needs Node.js 22.20+.
vendure-troubleshooting
npx skills add vendurehq/vendure --skill vendure-troubleshooting
Asks which agents to install it for (add -g for all projects). Needs Node.js 22.20+.
Also consider
- 0.846score
plano-observability-debugging
katanemo
Improve Plano tracing and debugging workflows.
SkillAFreshness: A★ 7.1KClaude Code +9 - 0.824score
systematic-debugging
GanyuanRan
Use when encountering a bug, test failure, or unexpected behavior, before proposing fixes
SkillAFreshness: A★ 1.4KClaude Code +9 - 0.788score
runtime-process-debugging
caarlos0
Debug cross-platform process, shell, sandbox, pipe, handle, startup, and shutdown behavior.
SkillAFreshness: A★ 224Claude Code +9
Questions
- Is systematic-debugging or vendure-troubleshooting more popular?
- systematic-debugging has more GitHub stars (15,567 against 8,539). Stars measure attention, not quality, so check freshness and docs too.
- Do systematic-debugging and vendure-troubleshooting work with Claude Code?
- Yes, both list a Claude Code install; the commands are on this page.
- Are systematic-debugging and vendure-troubleshooting open source?
- systematic-debugging is open source (Apache-2.0); the other is unknown.
Related
Cite this page
systematic-debugging vs vendure-troubleshooting. Agent Mart. https://agentmart.dev/compare/open-metadata-systematic-debugging-vs-vendurehq-vendure-troubleshooting (last updated 2026-10-26)