Loading...
Loading...
Found 1,737 Skills
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.
CSS animation fill-mode requirements for Editframe timeline system. Use when creating CSS animations, debugging flashing/flickering issues, or when user mentions animation problems, fade effects, slide effects, or sequential animations.
Stateful LLDB debugging via LLDB Python API
UI guidance for web apps installed on Apple platforms — iOS and iPadOS home-screen apps first (viewport-fit and safe areas, status bar and theme colour after iOS 26, sticky/fixed bars and overlays, startup images, icons and manifest, touch CSS, install hints, iOS-version gotchas) plus macOS Safari "Add to Dock" web apps (what carries over, what does nothing there, cookies, scope, icons, menu bar). Use when adding or debugging add-to-home-screen or Add to Dock behaviour, notch/safe-area layout, apple-mobile-web-app-* meta tags, web app manifest, splash screens, or anything that only looks wrong as an installed web app on iPhone, iPad or Mac. Not for service workers, offline caching, or push.
All-in-one Redis expertise covering data modeling and key naming, client connections (pooling, pipelining, client-side caching, timeouts), clustering and replication, Redis Search (FT.CREATE, vector and hybrid search, RAG pipelines), observability and incident triage, production security hardening, and semantic caching for LLM responses via LangCache. Use whenever designing, writing, reviewing, or debugging anything that touches Redis: choosing a data structure, naming keys, configuring a client, sharding across a cluster, building or tuning a search index, monitoring or diagnosing performance, hardening a deployment, or caching LLM completions. Adapted from Redis, Inc.'s official agent-skills repository (https://github.com/redis/agent-skills, MIT licensed), merged into one skill so the right domain loads automatically without picking between seven separate ones.
Current crewai 1.15.x API versus the 0.x API that coding assistants remember: imports, Agent/Task/Crew parameters and defaults, kickoff variants, CrewOutput fields, LLM model strings and provider extras, structured output (output_pydantic, response_model, response_format), guardrails, unified Memory, knowledge embedders, the `crewai create crew` wizard vs --classic, reset-memories flags, and removed features. Use when writing, reviewing, or debugging any crewai code, before trusting remembered crewai syntax, or when a user pastes errors like `cannot import name 'BaseTool' from 'crewai_tools'`, `cannot import name 'persist'`, `ShortTermMemory`, `Anthropic native provider not available`, `LiteLLM fallback package is not installed`, `got an unexpected keyword argument 'response_format'`, `OPENAI_API_KEY is required`, `If return type is annotated, it must be Tuple[bool, Any]`, or `result.pydantic is None`.
Use when creating, integrating, reviewing, or debugging a Make App's default Trace ID chain, traceparent and X-Log-Id propagation, safe correlated logs, or @qfei-design/make-app-observability error notices. Every new Make App includes this baseline even when the user does not mention observability. Covers direct-gateway and Service-fronted Apps and AI transports when present. Does not own authentication, Service route design, AI protocol, tracing backend/exporter deployment, runtime packaging, or page layout.
Test, debug, or profile Roblox experiences. Use for Studio debugging, TestEZ, logging, connection cleanup, memory or network diagnostics, MicroProfiler, Scene Analysis, and Script Profiler.
Use when adding Visual Editor support to a CloudCannon site, setting up editable regions, debugging visual editing issues, or making page sections editable in the CloudCannon preview.
Creates, modifies and manages Infrahub object data YAML files for populating infrastructure instances — devices, locations, organizations, and modules. TRIGGER when: creating device instances, populating data files, defining locations or organizations, adding infrastructure objects, modifying or extending an existing data file, updating attribute values or relationship links on objects already defined in a data file, debugging why an object fails to load. DO NOT TRIGGER when: designing or modifying schemas, including changing an attribute or relationship definition on a node kind (use infrahub-managing-schemas), writing Python checks/generators, querying live data.
Runs packages temporarily, creates isolated shell environments, and evaluates Nix expressions. Use when executing tools without installing, debugging derivations, or working with nixpkgs.
Systematic debugging workflow — reproduce, investigate, hypothesize, fix, and prevent. Covers root cause analysis, bug category strategies, evidence-based diagnosis, and post-mortem documentation.