troubleshooting

0
B

Structured debugging workflow. Only when user explicitly asks for help debugging.

CommandsAgentsMarketplace
#debugging#Check#Verify#Drizzle Studio#troubleshooting description#React#issues#editing

Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security

Installation for Agentic Skill

View all platforms →
skilz install settlemint/agent-marketplace/troubleshooting
skilz install settlemint/agent-marketplace/troubleshooting --agent opencode
skilz install settlemint/agent-marketplace/troubleshooting --agent codex
skilz install settlemint/agent-marketplace/troubleshooting --agent gemini

First time? Install Skilz: pip install skilz

Works with 14 AI coding assistants

Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...

View All Agents
Download Agent Skill ZIP

Extract and copy to ~/.claude/skills/ then restart Claude Desktop

1. Clone the repository:
git clone https://github.com/settlemint/agent-marketplace
2. Copy the agent skill directory:
cp -r agent-marketplace/devtools/skills/troubleshooting ~/.claude/skills/

Need detailed installation help? Check our platform-specific guides:

Related Agentic Skills

Agentic Skill Details

Type
Other
Meta-Domain
Primary Domain
Market Score
0

Agent Skill Grade

B
Score: 81/100 Click to see breakdown

Score Breakdown

Spec Compliance
13/15
PDA Architecture
22/30
Ease of Use
22/25
Writing Style
8/10
Utility
18/20
Modifiers: -2

Areas to Improve

  • Missing TOC for 500+ line file
  • Agent debugging section too verbose
  • Success criteria buried at end

Recommendations

  • Add trigger phrases to description for discoverability
  • Add table of contents for files over 100 lines

Graded: 2026-01-19

Developer Feedback

I took a look at your troubleshooting skill and wanted to share some thoughts.

Links:

The TL;DR

You're at 81/100, solid B territory. This is based on Anthropic's best practices for skill design. Your strongest area is Utility (18/20) – the skill actually solves real debugging problems with systematic workflows. Weakest area is Progressive Disclosure Architecture (22/30) – mainly because a 523-line file without a TOC makes navigation harder than it should be.

What's Working Well

  • Strong trigger coverage – Your metadata includes specific error patterns (TypeError, ECONNREFUSED) and intent phrases ("help debug", "fix this"), which means agents will actually find this skill when they need it
  • Solid utility focus – The quick_start workflow, CI feedback loop section, and before/after checklist patterns show you understand how debugging actually works in practice
  • Helpful references – Moving regenerate-vs-repair and boundary-complexity concepts to separate files is the right call, even if you could delegate more

The Big One: Navigation Crisis

Your 523-line SKILL.md is packed with value but impossible to scan. Agents and humans alike need to know what's where without reading everything. Add a table of contents immediately after the frontmatter with anchor links to each major section:

## Contents
- [Quick Start](#quick-start)
- [Agent Debugging](#agent-debugging)
- [CI Feedback Loop](#ci-feedback-loop)
- [Success Criteria](#success-criteria)

This one change gets you +2 points and makes the skill actually usable at scale.

Other Things Worth Fixing

  1. **Agent debugging section i...

AI-Detected Topics

Extracted using NLP analysis

debugging Check Verify Drizzle Studio troubleshooting description React issues editing inspection debugging tools

Report Security Issue

Found a security vulnerability in this agent skill?