Loading...
Loading...
Found 12,113 Skills
Structured workflows for investigating production issues in Honeycomb — the sequence of tool calls (context priming, broad query, BubbleUp, trace analysis, verification) and how to chain results between steps to reach root causes. Trigger phrases: "investigate production issue", "debug latency spike", "find root cause", "use BubbleUp", "analyze traces", "debug an outage", "why is my API slow", "errors are increasing", "health check", "SLO burning", or any request to investigate or debug production problems.
Structured performance profiling workflow. Identifies bottlenecks, measures against budgets, and generates optimization recommendations with priority rankings.
Walk the user through a PR as a single top-to-bottom narrative ordered by dependency/causal flow, with a heavy scrutiny pass for bugs, missing tests, scope creep, and security. Operates on a temp git worktree so it works while the main working tree is dirty. Use when the user asks to review a PR, walk through a PR, review a PR, or review one branch against another.
Integration guide for @daveyplate/better-auth-tauri - cookie-based auth in Tauri v2 desktop apps via deep links. Use when setting up Better Auth in a Tauri application, configuring social OAuth for desktop, or wiring up deep link authentication flows.
Uniview Smart Parking Open Platform Data Analysis Domain openydt data: Read-only data statistics and reports including parking lot payment bills, bill summaries, traffic flow, top license plate distribution, real-time parking lot data, daily vehicle exit/transaction counts, per-minute traffic flow, parking space usage, parking duration analysis, etc. Trigger words: data analysis/statistics/reports/check bills/payment bills/bill summaries/traffic flow/traffic statistics/top license plates/license plate distribution/real-time data/present vehicles/exit counts/transaction counts/per-minute traffic/parking space usage/parking space utilization rate/parking space occupancy/heatmap/echart/parking duration/duration analysis/parking duration distribution
Create and optimize in-app paywalls, upgrade screens, upsell modals, and feature gates for SaaS products. Trigger phrases: "write paywall copy," "design an upgrade screen," "upsell modal," "feature gate," "freemium conversion," "trial expiration screen," "limit reached," "upgrade prompt," "in-app paywall," "paywall copy," "upgrade flow," "convert free users to paid," "paywall conversion rate," "paywall A/B test." Note: this skill covers in-app upgrade experiences, not public-facing pricing pages.
Use whenever researching a technical question — a library, tool, API, error, version, or "what's the best way to X" — or whenever you're about to answer from memory. Forces multiple real searches over primary sources (official docs, source code, high-vote Stack Overflow, maintainer blogs) instead of one search plus training-data filler, and rejects SEO content-farm slop. Trigger on "research X", "look into", "what's the best library for", "how does X work", "is this still true", "find out".
TAO Execution SDK for submitting and monitoring GPU training jobs on supported platforms (Lepton, Brev, SLURM, local Docker, Kubernetes). Use when the user wants to run TAO jobs through the SDK, get job tracking, S3 I/O wrapping, multi-node distributed training, or platform-specific features that docker-run can't provide. Trigger phrases include "use the TAO SDK", "call tao_sdk", "AutoMLRunner", "ActionWorkflow", "Job handles", "S3 I/O wrapping", "TAO platform run".
The purpose, UX flow, and modern-minimalist design bar for the vigiles.sh landing site (site/). Use whenever designing, editing, adding to, or reviewing any site/ component, hero, section, or marketing copy — read it BEFORE touching site/, and hold every change against it. Not for docs/ or the app itself.
AI SDLC change-impact and lifecycle recovery workflow. Use when a requirement, acceptance criterion, decision, API contract, risk assumption, or other traced source changed after downstream artifacts were created and an AI assistant must identify stale artifacts, affected lifecycle stages, and evidence-backed reopen or revalidation actions without silently rewriting authoritative state. Supports `--quick-flow` for focused trace scanning and `--full-flow` for strict state and source-evidence gates.
Use when setting up a GitHub project board, labels, and Actions workflows for a new or existing repo.
Design voice and conversational interfaces — dialog flows, error recovery, and persona. Use when the interface speaks and listens rather than being tapped. For graphical input collection, use `form-design`.