Loading...
Loading...
Found 2,522 Skills
Test suite audit coordinator (L2). Delegates to 5 workers (Business Logic, E2E, Value, Coverage, Isolation). Aggregates results, creates Linear task in Epic 0.
Diagnose Clash proxy and network connection issues. Use this when users encounter network problems such as inability to connect to the network, proxy not working, GitHub/Google timeouts, DNS anomalies, TUN mode failures, etc.
Guidelines for Blazor development including component lifecycle, state management, and performance optimization
Best practices for Zustand state management in React and Next.js applications with TypeScript.
Receive and verify Deepgram webhooks (callbacks). Use when setting up Deepgram webhook handlers, processing transcription callbacks, or handling asynchronous transcription results.
6-phase investigation workflow for understanding existing systems. Auto-activates for research tasks. Optimized for exploration and understanding, not implementation. Includes parallel agent deployment for efficient deep dives and automatic knowledge capture to prevent repeat investigations.
Expert guidelines for blockchain development including CosmWasm, Cosmos, and cross-chain patterns
Develops reactive Livewire 4 components. Activates when creating, updating, or modifying Livewire components; working with wire:model, wire:click, wire:loading, or any wire: directives; adding real-time updates, loading states, or reactivity; debugging component behavior; writing Livewire tests; or when the user mentions Livewire, component, counter, or reactive UI.
Scaffold new modules and components for pplx-sdk following the layered architecture and established code patterns.
Diagnose and fix failing pytest tests in the pplx-sdk project, following existing test patterns and conventions.
Run an internal dogfooding program/sprint and produce a Dogfooding Pack (charter, scenario map, routines, dogfooding log + triage board spec, weekly report, ship/no-ship gate). Use for “dogfooding”, “eat our own dog food”, internal beta, and product teams using the product daily to find friction before shipping.
Use when SDK generation failed or seeing errors. Triggers on "generation failed", "speakeasy run failed", "SDK build error", "workflow failed", "Step Failed", "why did generation fail"