Skip to main content

/

/

Stats

Actions

Tags

Stats

Actions

Tags

ClaudePluginHub

Community directory for discovering and installing Claude Code plugins.

Find plugins for your project

AI-powered recommendations based on your stack.

Product

Browse Plugins
Marketplaces
Pricing
About
Contact

Resources

Learning Center
Blog
Weekly Digest
Claude Code Docs
Plugin Guide
Plugin Reference
Plugin Marketplaces

Community

Browse on GitHub
Get Support

Legal

Terms of Service
Privacy Policy

Browse · Plugins · Top Plugins · Marketplaces · Components · Technologies · Skills · Agents · Commands · Hooks · MCP Servers · LSP Servers · Output Styles · Themes · Monitors

Categories · Productivity · Development · Testing · Deployment · Security · Documentation · Data · Utilities

© 2025 ClaudePluginHub

Community Maintained · Not affiliated with Anthropic

ClaudePluginHub

ClaudePluginHub

Tools Learn Pricing

Search everything...

new-skill-2 | devtools

Home
Skills
devtools
new-skill-2

Skill

new-skill-2

From devtools

Explains error messages and stack traces. Use when the user shares an error, exception, or crash log and wants to understand what went wrong.

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/devtools:new-skill-2

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

When the user shares an error message or stack trace:

SKILL.md

17 lines · ~196 tokens

Stats

Stars0

MaintenanceExcellent

Last CommitApr 12, 2026

Actions

View Source View Plugin View on GitHub View README

Stats

Stars0

MaintenanceExcellent

Last CommitApr 12, 2026

Actions

View Source View Plugin View on GitHub View README

Explain Error

When the user shares an error message or stack trace:

Identify the error type — What category of error is this? (syntax, runtime, type, network, permission, etc.)
Explain in plain English — What does this error actually mean? Avoid jargon.
Find the root cause — Look at the stack trace to identify where and why it failed.
Suggest a fix — Give a concrete code change or action to resolve it.
Explain how to prevent it — What pattern or practice avoids this in the future?

Keep explanations concise. Lead with the fix, follow with the explanation.

$

npx claudepluginhub uncurated-tests/sample-plugin --plugin devtools

Similar Skills

writing-skills

230.8k

Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.

6 files

View writing-skills