Loading...
Loading...
Found 240 Skills
Analyze implementation details, trace data flow, and explain technical workings with precise file:line references. Use when you need to understand HOW code works.
Reference for all GrepAI MCP tools. Use this skill to understand available MCP tools and their parameters.
[Fix & Debug] Investigate and explain how existing features or logic work. READ-ONLY exploration with no code changes.
MLflow ML lifecycle management. Use for ML experiment tracking.
Trace design decisions and concepts through session history, handoffs, and git. Triggers: "trace decision", "how did we decide", "where did this come from", "design provenance", "decision history".
Setup Sentry in Ruby apps. Use when asked to add Sentry to Ruby, install sentry-ruby gem, or configure error monitoring for Ruby applications or Rails.
Navigate, search, and understand the Resume Matcher codebase using ripgrep, ack, or grep. Find functions, classes, components, API endpoints, trace data flows, and understand architecture. Use FIRST when exploring code, finding files, or understanding project structure.
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for CTF web, API, SSR, frontend, queue-backed app, and routing challenges. Use when the user asks to inspect a site or API, follow real browser requests, debug auth or session flow, trace uploads or workers, find hidden routes, or explain why frontend and backend behavior diverge under sandbox-internal routing. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
Opik observability for LLM agents — Agent Configuration, Local Runner (opik connect), Evaluation Suites, threads, integrations. Use for "configure my agent", "connect my agent", "evaluate my agent" or "integrate with Opik".
This skill should be used when the user asks to "debug DSPy programs", "trace LLM calls", "monitor production DSPy", "use MLflow with DSPy", mentions "inspect_history", "custom callbacks", "observability", "production monitoring", "cost tracking", or needs to debug, trace, and monitor DSPy applications in development and production.
Interactive code execution path tracer that explains how code flows from entry point to output. Uses step-by-step navigation with AskUserQuestion to explore conditional branches and function calls. Use when: - User asks "How does X work in this codebase?" - User wants to understand HTTP request/response flow - User asks about middleware execution order - User wants to trace a function call chain - User asks "What happens when..." questions - User wants to learn how code paths connect Keywords: trace, flow, execution, path, call chain, middleware, request handling, what happens, how does, step through, follow the code
APM - traces, services, dependencies, performance analysis.