debugging
9
chrome-devtools
Debug web pages directly in Chrome using DevTools capabilities via MCP
pacphi
tools
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
debugging
9
root-cause-tracing
Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
CatsMiaow
tools
debugging
9
benchmarking-optimization
This skill should be used when the user asks to "run benchmarks", "profile performance", "measure allocations", "optimize render speed", "find hot paths", "generate flamegraph", or mentions stackprof, memory profiler, or performance optimization.
tobi
tools
debugging
9
ios-pentest
Comprehensive iOS mobile application penetration testing skill with Frida/Objection integration for jailbroken and non-jailbroken devices. This skill should be used when performing security assessments on iOS applications including static analysis, dynamic analysis, runtime manipulation, traffic interception, keychain analysis, and vulnerability identification. Triggers on requests to pentest iOS apps, test iPhone/iPad security, analyze IPAs, bypass security controls, or perform OWASP MASTG iOS assessments.
hardw00t
tools
debugging
9
osworld-observe
Get the current observation from the OSWorld environment. Returns screenshot (base64 PNG) and accessibility tree (JSON).
bdambrosio
tools
debugging
8
ux-improver
Recursively improve web application UX via vision-based screenshot analysis. Use when asked to "improve UX", "fix usability", "audit user experience", or "/uximprove". Triggers on UX review, usability improvement, user flow analysis, interaction audit.
Motium-AI
tools
debugging
8
codebase-context
This skill should be used when the user asks to "analyze the codebase", "understand the tech stack", "extract project patterns", "get codebase context", "what technologies are used", or when preparing context for planning documents, PRDs, or design documentation.
jsegov
tools
debugging
8
react-best-practices
A comprehensive guide and rule set for writing clean, performant, and maintainable React code.
mdbabumiamssm
tools
debugging
8
mcp-chrome-devtools
This skill provides guidance for using Chrome DevTools MCP for browser debugging and automation. Use when debugging web pages, analyzing performance, inspecting network requests, viewing console messages, or interacting with Chrome DevTools features programmatically.
s-hiraoku
tools
debugging
8
code-metrics
Measures code structure metrics (coupling, cohesion, complexity, call graph). Use when analyzing code quality quantitatively, checking architectural health, or reviewing structural changes.
ssiumha
tools
debugging
8
fuzzing-strategist
Fuzzing strategist persona specializing in dynamic testing guidance, fuzzing strategy development, and crash analysis
jpoley
tools
debugging
8
browser-devtools
Browser debugging and automation using Playwright. Use for web debugging, console monitoring, network analysis, screenshot capture, DOM inspection, and UI testing during development.
vukhanhtruong
tools
debugging
8
web-performance-seo
Fix PageSpeed Insights/Lighthouse accessibility "!" errors caused by contrast audit failures (CSS filters, OKLCH/OKLAB, low opacity, gradient text, image backgrounds). Use for accessibility-driven SEO/performance debugging and remediation.
ZhanlinCui
tools
debugging
8
react-performance-optimizer
Analyzes React/Next.js code for performance bottlenecks, focusing on waterfalls, bundle size, and rendering efficiency.
mdbabumiamssm
tools
debugging
8
root-cause-analysis
WHEN to auto-invoke: Debugging issues, fixing bugs, investigating errors, "not working" problems, unexpected behavior, stack traces, error messages, troubleshooting, "why is this happening". WHEN NOT to invoke: Building new features from scratch, documentation, refactoring working code, adding tests to working code.
gr8monk3ys
tools
debugging
8
s-debug
Diagnose and fix bugs using evidence-based investigation. Requires runtime evidence before fixes—never guess based on code alone. Covers hypothesis-driven debugging, instrumentation logging, Lua errors, taint issues, combat lockdown, and API failures. Triggers: error, bug, debug, fix, crash, taint, nil value, diagnose, hypothesis, runtime, evidence, instrumentation.
Falkicon
tools
debugging
8
exploit-researcher
Exploit researcher persona specializing in attack surface analysis, exploit scenario generation, and vulnerability chaining
jpoley
tools