Loading...
Loading...
Found 1,678 Skills
Stateful LLDB debugging via LLDB Python API
Troubleshoot Coval OpenTelemetry trace ingestion, missing trace UI, sparse traces, bad simulation or conversation correlation, auth/org errors, oversized payloads, duplicate spans, and production debugging with Trace Search.
Converts cuTile GPU kernels (@ct.kernel) to Triton (@triton.jit). Handles standard in-repo conversion, debugging (cudaErrorIllegalAddress, shape mismatch, numerical mismatch), and mapping cuTile idioms (ct.load/ct.store, ct.Constant, ct.launch) to Triton equivalents. Covers dual-kernel layout flags (e.g. transpose=True/False + autotune grid via META) per translations/advanced-patterns.md. Use when converting, porting, or translating cuTile kernels to Triton, or debugging existing Triton translations.
Debug Android WebView, browsers, and Node.js using Chrome DevTools through FoldDevtools with root or remote debugging
The orchestrator and entry point for the engineering skills suite. Use this skill whenever the task involves doing engineering work to a high bar — reviewing code or a design, designing a new system or component, debugging a hard problem or running an incident, implementing a substantive change, writing documentation, or sanity-checking an approach. Use it when the user phrases things casually ("rip into this", "be brutal", "is this approach right", "what am I missing", "what would you change", "look at this") or formally ("review this PR", "audit this design"). Use it proactively for any non-trivial engineering work, before declaring something done. The skill triages the work, dispatches to the right specialty skill(s), enforces verification, and produces an evidence-backed result. The goal is to ensure no AI shortcut, sycophantic agreement, or stylistic distraction gets in the way of work that holds up to senior-engineer scrutiny.
[Fix & Debug] ⚡⚡ Fix a GitHub issue with systematic debugging
Debug Kubernetes pods, nodes, and workloads. Use when pods are failing, containers crash, nodes are unhealthy, or users mention debugging, troubleshooting, or diagnosing Kubernetes issues.
Guide for debugging crashes related to custom memory heaps, particularly use-after-free issues caused by static destruction ordering, DEBUG vs RELEASE discrepancies, and custom allocator lifecycle problems. This skill should be used when investigating crashes that occur only in RELEASE builds, memory-related crashes involving custom allocators, static initialization/destruction order issues, or use-after-free bugs in C++ applications.
Creates and edits Liftosaur workout programs using Liftoscript. Use for program authoring, exercise/set changes, progression setup (lp/dp/sum/custom), advanced custom progression logic, custom progress/update script debugging, and reuse/template refactors.
Test and debug Mom Factura Payment API integrations using QA environment and payment simulation. Use when setting up test environments, simulating payment outcomes (success, failure, timeout), debugging API errors, or validating integration before production.
Use when ANY runtime debugging is needed — setting breakpoints, inspecting variables, evaluating expressions, analyzing threads, or reproducing crashes interactively with LLDB
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions "largest contentful paint", "page load speed", "CWV", or wants to improve how fast their hero image or main content renders.