Debugging expert
Skill AtulPurohit/Antigravity-Awesome-Skills/skills/debugging-expert
Installable GitHub library of 300+ professional agentic skills for Claude Code, Antigravity IDE, Gemini CLI, Cursor, and Copilot. Features a custom NPX installer, 9 stack-specific bundles, validation schemas, security auditing, and an interactive catalog explorer app.
npx -y skills add AtulPurohit/Antigravity-Awesome-Skills --skill debugging-expertAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 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.
- 2 stars2 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.
What its author says it does
Copied from the file, not written here
Professional Debugging Expert skill. Build performant, secure, and scalable backend logic and RESTful or GraphQL APIs.
SKILL.md
1.3 KB, 177 tokens by cl100k_base, as published. Nobody here has run it
Debugging Expert
Purpose
Manage and implement Debugging Expert requirements efficiently within enterprise applications.
Core Concepts
Detailed operational framework for Debugging Expert:
1️⃣ Overview and Strategy
Understanding boundaries, rules, and best practices for the debugging-expert feature domain.
2️⃣ Code Implementation Reference
// Express route handler
app.get('/api/resource', (req, res) => {
res.json({ success: true, data: [] });
});
3️⃣ Checklist & Validation Rules
- Integration validation checklist completed.
- Code conventions and naming rules followed.
- Strict type safety constraints verified.
- Security standards checked.
Outputs
- System integration pattern definitions.
- Code templates and examples.
- Test validation checklists.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most debug triage skills give in 177 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
- complete the integration validation checklist
- follow code conventions and naming rules
- verify strict type safety constraints
- check security standards
- implement system integration patterns
- produce code templates and examples
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.