Loading...
Loading...
Found 1,740 Skills
Sentry error tracking and debugging specialist
Use when setting up CI/CD, Docker, deployment pipelines, monitoring, alerting, infrastructure, or debugging production issues
Classify user requests and route to the correct agent + skill combination. Use for any user request that needs delegation: code changes, debugging, reviews, content creation, research, or multi-step workflows. Invoked as the primary entry point via "/do [request]". Do NOT handle code changes directly - always route to a domain agent. Do NOT skip routing for anything beyond pure fact lookups or single read commands.
Run quality gates on implemented feature: tests, lint, type checks, and custom validation. Use after /feature-implement completes. Use for "validate feature", "run quality gates", "check feature", or "/feature-validate". Do NOT use for ad-hoc linting or debugging.
Guides efficient Haskell aligned with GHC practice -- laziness and strictness, purity, fusion, newtypes, pragmas, Core reading, and space-leak avoidance. Use when writing or reviewing Haskell, optimizing or profiling, debugging strictness or memory, or when the user mentions GHC, thunks, foldl vs foldl', list fusion, SPECIALIZE, or UNPACK.
UdonSharp (C# to Udon Assembly) scripting skill for VRChat world development. Use this skill when writing, reviewing, or debugging UdonSharp C# code. Covers compile constraints (List<T>/async/await/try/catch/LINQ blocked), network sync (UdonSynced, RequestSerialization, FieldChangeCallback, NetworkCallable), persistence (PlayerData/PlayerObject), Dynamics (PhysBones, Contacts), Web Loading, and event handling. SDK 3.7.1 - 3.10.2 coverage. Triggers on: UdonSharp, Udon, VRC SDK, UdonBehaviour, UdonSynced, NetworkCallable, VRCPlayerApi, SendCustomEvent, PlayerData, PhysBones, synced variables, VRChat world scripting, C# to Udon.
Go error handling patterns, wrapping, sentinel errors, custom error types, and the errors package. Grounded in Effective Go, Go Code Review Comments, and production-proven idioms. Use when implementing error handling, designing error types, debugging error chains, or reviewing error handling patterns. Trigger examples: "handle errors", "error wrapping", "custom error type", "sentinel errors", "errors.Is", "errors.As". Do NOT use for panic/recover patterns in middleware (use go-api-design) or test assertion errors (use go-test-quality).
Guidelines for organizing .NET projects, including solution structure, project references, folder conventions, .slnx format, centralized build properties, and central package management. Use when setting up a new .NET solution with modern best practices, configuring centralized build properties across multiple projects, implementing central package version management, or setting up SourceLink for debugging.
Apply when building or debugging a VTEX IO session transform app (vtex.session integration). Covers namespace ownership, input-vs-output fields, transform ordering (DAG), public-as-input vs private-as-read model, cross-namespace propagation, configuration.json contracts, caching inside transforms, and frontend session consumption. Use when designing session-derived state for B2B, pricing, regionalization, or custom storefront context.
Comprehensive Pal MCP toolkit for code analysis, debugging, planning, refactoring, code review, and execution tracing. Provides systematic workflows with expert validation for complex development tasks.
Workato platform help — enterprise iPaaS, 1200+ connectors, recipe-based automation, API Management, MCP Gateway, Agent Studio (Genies AI agents), Data Tables, Event Streams, B2B/EDI, Embedded iPaaS, IDP. Use when recipe costs keep spiraling and you need to optimize task consumption, recipe errors are unclear and debugging is painful, evaluating Workato vs MuleSoft vs Boomi vs Celigo, setting up API management or MCP gateway, building Genies AI agents in Agent Studio, or connecting enterprise apps without coding. Do NOT use for simple Zapier/Make automations (use /sales-integration) or MuleSoft-specific questions (use /sales-mulesoft).
Use when editing .lean files, debugging Lean 4 builds (type mismatch, sorry, failed to synthesize instance, axiom warnings, lake build errors), searching mathlib for lemmas, formalizing mathematics in Lean, or learning Lean 4 concepts. Also trigger when the user asks for help with Lean 4, mathlib, or lakefile. Do NOT trigger for Coq/Rocq, Agda, Isabelle, HOL4, Mizar, Idris, Megalodon, or other non-Lean theorem provers.