Loading...
Loading...
Found 2,164 Skills
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.
Fetch and analyze AppSignal error incidents. Use when debugging errors, investigating exceptions, or when the user mentions AppSignal, incidents, or error monitoring.
Interactive debugging via DAP-MCP for multiple languages with natural language commands
C++20 coroutines skill for understanding coroutine mechanics and debugging. Use when working with co_await, co_yield, co_return, implementing promise_type, understanding coroutine frame layout, debugging suspended coroutines in GDB, or inspecting frame allocation with Compiler Explorer. Activates on queries about C++20 coroutines, co_await, co_yield, promise_type, coroutine_handle, coroutine suspension, or coroutine frame.
Dodun 操作手册。Use when the user asks how Dodun works, how to install or use the CLI, how to join a space, send or receive with a token, manage skills, inspect inbox or attachments, manually route a task, or debug why routing / execution / receive-back failed. Prefer this over the old `dodun-agent-network` wording and only use legacy register/search/send commands when the user explicitly wants low-level directory debugging.
Stateful LLDB debugging via LLDB Python API
LangSmith tracing and trace debugging for AgentSeek templates. Covers CLI installation, adding tracing to LangGraph apps, querying traces, and inspecting run IO. Use when debugging agent backends, investigating slow traces, or adding observability to a template.
Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.
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`.
Debugging-method traps: run the discriminating experiment first, read build logs bottom-up, treat an empty actual as unwritten, audit shared handles before removing a feature, read commit history critically. Use when a fix is not converging.
Walk a person from an idea to a Claude Managed Agents agent that runs on its own, and stay with them through debugging. Explains each concept at the moment it matters (Agent, Environment, Session, Deployment, vault, memory store, outcome), asks the real decisions as illustrated AskUserQuestion choices, designs the system prompt in Simplified Technical English, finds MCP connectors, sets up credentials without the secret ever reaching the chat, writes the files, applies them with the `ant` CLI, runs a capped test session, and diagnoses failed sessions from their events. Trigger on "crea un agente en Managed Agents", "managed agents wizard", "quiero un agente que corra solo", "agente programado", "agente que revise mis repos cada lunes", "mi sesión se quedó pegada", "por qué falló mi agente", "debug my managed agent session", "explícame la traza", "set up a scheduled Claude agent", "deploy an agent on a cron". Not for the Claude Agent SDK (use agent-sdk-wizard), the raw Messages API, or Claude Code itself.
Search Sourcegraph-indexed codebases for patterns, examples, and system understanding. Triggers on implementation questions, debugging, or "how does X work" queries.