Loading...
Loading...
Found 1,093 Skills
Activate when the user clearly has a skill issue. Generates chaotic, barely-functional code with maximum confidence and sarcastic commentary. Guarantees an infinite loop of attempted fixes that never quite land.
Fix failing ToolUniverse tools by diagnosing test failures, identifying root causes, implementing fixes, and validating solutions. Use when ToolUniverse tools fail tests, return errors, have schema validation issues, or when asked to debug or fix tools in the ToolUniverse framework.
Systematically debug and diagnose issues methodically. Uses diagnostic techniques to identify root causes and implement fixes.
Guide for testing Codex TUI interactively
Use when given a Sentry issue URL and you need to fetch exception details, stacktrace, and request context using sentry-cli (and Sentry API fallback when needed).
Fetch and analyze Sentry issues, events, transactions, and logs. Helps agents debug errors, find root causes, and understand what happened at specific times.
Helps with Prowler repository CI and PR gates (GitHub Actions workflows). Trigger: When investigating CI checks failing on a PR, PR title validation, changelog gate/no-changelog label, conflict marker checks, secret scanning, CODEOWNERS/labeler automation, or anything under .github/workflows.
DART testing patterns - unit tests, integration tests, CI validation
Guide for integrating Agentica SDK with Claude Code CLI proxy
Check reference SDK implementations using btca ask
Environment Triage
strace and ltrace skill for system call and library call tracing. Use when a binary behaves incorrectly without crashing, diagnosing file-not-found errors, permission failures, network issues, or unexpected library calls by tracing syscalls and library function calls. Activates on queries about strace, ltrace, syscall tracing, library interception, ENOENT, EPERM, strace -e, or diagnosing binary behaviour without a debugger.