Debugging
Find and fix bugs, error analysis
cross-gcc
by mohitmishra786
Cross-compilation with GCC skill for embedded and multi-architecture targets. Use when setting up cross-gcc toolchains, configuring sysroots, building for ARM/AArch64/RISC-V/MIPS from an x86-64 host, troubleshooting wrong-architecture errors, or running cross-compiled binaries under QEMU. Activates on queries about cross-compilation triplets, sysroot, pkg-config for cross builds, embedded toolchains, or Yocto/Buildroot integration.
zig-debugging
by mohitmishra786
Zig debugging skill. Use when debugging Zig programs with GDB or LLDB, interpreting Zig runtime panics, using std.debug.print for tracing, configuring debug builds, or debugging Zig programs in VS Code. Activates on queries about debugging Zig, Zig panics, zig gdb, zig lldb, std.debug.print, Zig stack traces, or Zig error return traces.
valgrind
by mohitmishra786
Valgrind profiler skill for memory error detection and cache profiling. Use when running Memcheck to find heap corruption, use-after-free, memory leaks, or uninitialised reads; or Cachegrind/Callgrind for cache simulation and function-level profiling. Activates on queries about valgrind, memcheck, heap leaks, use-after-free without sanitizers, cachegrind, callgrind, KCachegrind, or massif memory profiling.
dynamic-linking
by mohitmishra786
Dynamic linking skill for Linux/ELF shared libraries. Use when debugging library loading failures, configuring RPATH vs RUNPATH, understanding soname versioning, using dlopen/dlsym for plugin systems, LD_PRELOAD interposition, or controlling symbol visibility. Activates on queries about shared libraries, dlopen, LD_LIBRARY_PATH, RPATH, soname, LD_PRELOAD, symbol visibility, or "cannot open shared object file" errors.
llvm-learning
by gmh5225
Comprehensive learning resources and tutorials for LLVM, Clang, and compiler development. Use this skill when helping users learn LLVM internals, find educational resources, or understand compiler concepts.
OpenTelemetry Observability Expert
by anton-abyzov
OpenTelemetry expert for full-stack observability including distributed tracing, metrics, and log correlation. Covers OTel Collector configuration, auto-instrumentation for Node.js/Python/Java/.NET/Go, sampling strategies, backend integration (Grafana, Jaeger, Datadog), and cost optimization. Activates for: OpenTelemetry, OTel, distributed tracing, tracing, spans, metrics, observability, Jaeger, Grafana Tempo, OTLP.
External Issue Import
by anton-abyzov
Import external issues from GitHub, Jira, or Azure DevOps and create SpecWeave increments with platform suffixes (G/J/A). Supports filtering and duplicate prevention. Use when saying "import issues", "pull from github", "grab jira issues", or "import from ado".
Node.js Backend Agent - API & Server Development Expert
by anton-abyzov
Node.js/TypeScript backend developer for Express, Fastify, NestJS, and GraphQL. Use when building Node.js APIs, REST endpoints, GraphQL APIs, or backend services.
Code Grill Expert
by anton-abyzov
Critical code review and quality interrogation before increment completion. Use when finishing a feature, before /sw:done, or when saying "grill the code", "review my work", "critique implementation".
Rust Backend Agent - High-Performance Memory-Safe API Expert
by anton-abyzov
Rust backend developer for building high-performance, memory-safe APIs and services. Use when building Rust backends with Axum, Actix-web, Rocket, or Warp. Covers Tokio async runtime, SQLx, Diesel, error handling, and zero-cost abstractions.
pua-debugging
by tanweai
"Use when any task fails two or more times, when about to give up or say 'I cannot', when deflecting to the user ('you should manually...', 'please check...', 'you may need to...'), blaming the environment without verification ('might be a permissions issue', 'could be a network problem'), producing any excuse to stop trying, spinning in circles (repeatedly tweaking the same code/parameters without new information — busywork/磨洋工), fixing only the surface issue without checking for related problems, skipping verification after a fix and claiming 'done', giving suggestions instead of actual code/commands, saying 'this is beyond scope' or 'this requires manual intervention', encountering permission/network/auth errors and stopping instead of trying alternatives, or showing any passive behavior (waiting for user instructions instead of proactively investigating). Also triggers on user frustration phrases in any language: '你怎么又失败了', '为什么还不行', '换个方法', '你再试试', '不要放弃', '继续', '加油', 'why does this still not work', 'try harder', 'you keep failing', 'stop giving up', 'try again', 'don't give up', 'keep going', 'figure it out'. Applies to ALL task types: debugging, implementation, config, deployment, research, DevOps, infrastructure, API integration, data processing. Do NOT trigger on first-attempt failures or when a known fix is already in progress."
frontend-patterns
by romiluz13
"Internal skill. Use cc10x-router for all development tasks."
Go Backend Agent - High-Performance API & Microservice Expert
by anton-abyzov
Go/Golang backend developer for building high-performance APIs and microservices. Use when building Go backends, REST/gRPC APIs, CLI tools, or concurrent services with net/http, Gin, Echo, Chi, or Fiber.
Observability Engineer - Full-Stack Monitoring Expert
by anton-abyzov
Full-stack observability architect for Prometheus, Grafana, OpenTelemetry, distributed tracing (Jaeger/Tempo), SLIs/SLOs, error budgets, and alerting. Use for metrics, dashboards, traces, or reliability engineering.
Doctor - Installation Health Scanner
by anton-abyzov
Run installation health diagnostics - detect ghost commands, stale cache, hash mismatches, and namespace pollution. Use when saying "doctor", "health check", "diagnose installation", or "check installation".
api-rate-limiting
by aj-geddes
Implement API rate limiting strategies using token bucket, sliding window, and fixed window algorithms. Use when protecting APIs from abuse, managing traffic, or implementing tiered rate limits.
circuit-breaker-pattern
by aj-geddes
Implement circuit breaker patterns for fault tolerance, automatic failure detection, and fallback mechanisms. Use when calling external services, handling cascading failures, or implementing resilience patterns.
browser-debugging
by aj-geddes
Debug client-side issues using browser developer tools. Identify JavaScript errors, styling issues, and performance problems in the browser.
alert-management
by aj-geddes
Implement comprehensive alert management with PagerDuty, escalation policies, and incident coordination. Use when setting up alerting systems, managing on-call schedules, or coordinating incident response.
localstack
by localstack
Manage LocalStack container lifecycle. Use when users need to start, stop, restart, or check status of LocalStack, configure LocalStack environment variables, or troubleshoot LocalStack container issues.
managing-git
by CloudAI-X
Manages Git workflows including branching, commits, and pull requests. Use when working with Git, creating commits, opening PRs, managing branches, resolving conflicts, or when asked about version control best practices.
error-handling
by CloudAI-X
Implements error handling patterns, structured logging, retry strategies, circuit breakers, and graceful degradation. Use when designing error handling, setting up logging, implementing retries, adding error tracking, or when asked about error boundaries, log aggregation, alerting, or resilience patterns.
typst
by lucifer1004
"Typst document creation and package development. Use when: (1) Working with .typ files, (2) User mentions typst, typst.toml, or typst-cli, (3) Creating or using Typst packages, (4) Developing document templates, (5) Converting Markdown/LaTeX to Typst"
systematic-debugging
by FradSer
Provides systematic debugging methodology with 4-phase process (root cause investigation, pattern analysis, hypothesis testing, implementation). Use when encountering any bug, error, failure, broken functionality, test failure, unexpected behavior, troubleshooting issue, or investigating why something isn't working. Always apply before proposing fixes or making changes.