Loading...
Loading...
Found 268 Skills
Use when fixing VoiceOver issues, Dynamic Type violations, color contrast failures, touch target problems, keyboard navigation gaps, or Reduce Motion support - comprehensive accessibility diagnostics with WCAG compliance, Accessibility Inspector workflows, and App Store Review preparation for iOS/macOS
Run IV, DiD, and RDD analyses in R with proper diagnostics
Install and configure LSP (Language Server Protocol) for Claude Code to enable go-to-definition, find-references, and real-time diagnostics
Production incident response procedures for Python/React applications. Use when responding to production outages, investigating error spikes, diagnosing performance degradation, or conducting post-mortems. Covers severity classification (SEV1-SEV4), incident commander role, communication templates, diagnostic commands for FastAPI/ PostgreSQL/Redis, rollback procedures, and blameless post-mortem process. Does NOT cover monitoring setup (use monitoring-setup) or deployment procedures (use deployment-pipeline).
Create a Founder Sales Sprint Pack (ICP wedge + target list, outreach sequences, diagnostic discovery script, decision-enablement assets to beat “no decision”, and a white-glove activation plan). Use for founder-led sales, early sales, first customers, and first 10 customers. Category: Sales & GTM.
Systematically debug and diagnose issues methodically. Uses diagnostic techniques to identify root causes and implement fixes.
Guides structured 4-stage experiment execution with attempt budgets and gate conditions: Stage 1 initial implementation (reproduce baseline), Stage 2 hyperparameter tuning, Stage 3 proposed method validation, Stage 4 ablation study. Integrates with evo-memory (load prior strategies, trigger IVE/ESE) and experiment-craft (5-step diagnostic on failure). Use when: user has a planned experiment, needs to reproduce baselines, organize experiment workflow, or systematically validate a method. Do NOT use for debugging a specific experiment failure (use experiment-craft) or designing which experiments to run (use paper-planning).
Run, monitor, resume, merge, and debug Ralph loops. Use this skill whenever the user asks to operate `ralph run` or `ralph loops`, inspect loop state, recover suspended loops, analyze diagnostics, or unblock merge queue issues.
Generate MSBuild binary logs (binlogs) for build diagnostics and analysis. Only activate in MSBuild/.NET build context. USE FOR: adding /bl:{} to any dotnet build, test, pack, publish, or restore command to capture a full build execution trace, prerequisite for binlog-failure-analysis and build-perf-diagnostics skills, enabling post-build investigation of errors or performance. Requires MSBuild 17.8+ / .NET 8 SDK+ for {} placeholder; PowerShell needs -bl:{{}}. DO NOT USE FOR: non-MSBuild build systems (npm, Maven, CMake), analyzing an existing binlog (use binlog-failure-analysis instead). INVOKES: shell commands (dotnet build /bl:{}).
Apply behavioral psychology and cognitive biases to marketing for conversion optimization, pricing strategy, copy improvement, and campaign design. Includes 70+ mental models organized by application, diagnostic frameworks for identifying behavioral barriers, and implementation guides with before/after examples. Use when applying psychology to marketing, optimizing conversions, improving pricing pages, or when user mentions psychology, cognitive bias, persuasion, behavioral science, mental models, why people buy, decision-making, consumer behavior, or neuromarketing.
Run system health checks including CPU, memory, disk, and process status. Use when: user asks about system performance, needs diagnostics, or wants to check resource usage. No API key needed.
Donella Meadows's System Leverage Points applied to any complex system — company, market, policy, or organization. Spawns a team of specialist agents — System Cartographer, Leverage Diagnostician, Counterintuitive Analyst, Paradigm Archaeologist, Dancing Advisor — who each apply a distinct lens from Meadows's framework to identify where you're wasting effort on low-leverage interventions. The lead synthesizes into a leverage audit: which level you're pushing at, which level you should be pushing at, and whether you're pushing in the right direction. Use when the user says "meadows this", "where's the leverage", "systems analysis", "why isn't this working", or describes a complex system that seems stuck despite effort. Works as a standalone analysis or paired with /munger.