573 skills · sorted by relevance
Add OpenTelemetry tracing to frontend and backend flows. Connect execution records across services and background jobs, record phase durations and entity IDs, and mark failures so developers can investigate slow or broken operations.
Trace system behavior across code, APIs, authentication, data, and networks through an interactive workflow. Store steps, branches, and findings in SQLite, then export diagrams and documentation for security audits, debugging, architecture reviews, or incident analysis.
Applies systematic tracing and isolation techniques to pinpoint exactly where a bug originates in code. Use when a bug is hard to locate, code is not working as expected, an error or crash appears with unclear cause, a regression was introduced between recent commits, or you need to narrow down which component, function, or line is faulty. Covers binary search debugging, git bisect for regressions, strategic logging with [TRACE] patterns, data and control flow tracing, component isolation, minimal reproduction cases, conditional breakpoints, and watch expressions across TypeScript, SQL, and bash.
The English summary is being prepared. Showing the original description.
Site reliability specialist for Prometheus metrics, distributed tracing, alerting strategies, and SLO designUse when "observability, monitoring, prometheus, grafana, alerting, slo, sli, metrics, tracing, logging, on-call, incident, observability, prometheus, grafana, tracing, jaeger, alerting, slo, sli, metrics, logging, sre, ml-memory" mentioned.
The English summary is being prepared. Showing the original description.
Expert at making systems observable and debuggable. Covers structured logging, metrics collection, distributed tracing, error tracking, and alerting. Knows how to find the needle in the haystack when production breaks at 3 AM. Use when "observability, logging, metrics, tracing, monitoring, error tracking, Sentry, Datadog, OpenTelemetry, debugging production, observability, logging, metrics, tracing, monitoring, sentry, prometheus, opentelemetry" mentioned.
The English summary is being prepared. Showing the original description.
Expert in Langfuse - the open-source LLM observability platform. Covers tracing, prompt management, evaluation, datasets, and integration with LangChain, LlamaIndex, and OpenAI. Essential for debugging, monitoring, and improving LLM applications in production. Use when "langfuse, llm observability, llm tracing, prompt management, llm evaluation, monitor llm, debug llm, langfuse, observability, tracing, llm-monitoring, evaluation, prompt-management, debugging, analytics" mentioned.
The English summary is being prepared. Showing the original description.
Analyzing contact tracing data — network reconstruction, transmission chains, and evaluating tracing performance.
The English summary is being prepared. Showing the original description.
Implementing distributed tracing with W3C Trace Context — the byte-precise `traceparent` and `tracestate` header formats, OpenTelemetry's W3CTraceContextPropagator as the modern default (replacing X-B3-* and X-Datadog-*), head vs tail sampling, and HTTP→SQL trace propagation via sqlcommenter. Grounded in the W3C REC and OpenTelemetry specs.
The English summary is being prepared. Showing the original description.
Instrument a shipped product's AI agents with tracing and observability so you can see what they did, why outputs happened, and what each run cost. Plain-language primer plus free-tier-first backend selection (Langfuse, Phoenix, LangSmith, Braintrust) and OpenTelemetry/OpenInference instrumentation. Load when the user asks to add observability, add tracing, instrument my agents, see what my agent is doing in production, set up Langfuse or Phoenix or LangSmith, debug why my agent gave a bad answer, or track LLM cost per request. Also fires when agent-system-architecture or setup-evaluation requires an observability plan for an agent-chain product. NOT for tracing the coding agent itself — that is run-trace. Precondition for runtime-learning-loop.
The English summary is being prepared. Showing the original description.
INVOKE THIS SKILL when adding Arize AX tracing to an application. Follow the Agent-Assisted Tracing two-phase flow: analyze the codebase (read-only), then implement instrumentation after user confirmation. When the app uses LLM tool/function calling, add manual CHAIN + TOOL spans so traces show each tool's input and output. Leverages https://arize.com/docs/ax/alyx/tracing-assistant and https://arize.com/docs/PROMPT.md.
The English summary is being prepared. Showing the original description.
Create CodeTour files that guide readers through a codebase step by step, with verified file and line references. Tailor the walkthrough to new contributors, architecture readers, PR reviewers, or investigators tracing a failure or security boundary.
Debug Node.js from the terminal by pausing execution, inspecting variables, and tracing function calls. Use interactive commands or scripts to investigate failing tests, collect runtime state, and capture CPU profiles or memory snapshots.
Investigate software errors by tracing code, reviewing recent changes, and reproducing symptoms. Test a specific cause before making a minimal fix, then verify the result with regression tests and a structured debug report.
Turn a project's claude-mem history into weekly narrative chapters. Each chapter builds on the previous week's handoff, tracing ongoing work, decisions, and unresolved questions, with an index and chronologically ordered Markdown files.
Inspect stored Muse records when regular product tools do not reveal enough detail. Use read-only database queries to investigate missing records, trace execution history, and check relationships or inconsistencies across different product areas.
Review GitHub Actions workflows that run AI agents, tracing how external input reaches prompts and tools. Produce findings with evidence, severity, impact, and remediation guidance through static analysis, which examines configuration without running attacks.
Investigate errors and unexpected behavior by finding related code, following function calls, and checking source files. GitNexus helps trace execution paths, while the diagnosis identifies the repository and reports how current its code index is.
Solve sandboxed CTF security challenges by reconstructing encoding and encryption steps, extracting data hidden in media, and tracing mobile app signing or storage behavior. Preserve exact parameters and evidence to reproduce decoded content or signed requests.
Organize CTF investigations by mapping the supplied targets, tracing one minimal path, and selecting the relevant specialist workflow. Findings are grounded in observed behavior and reproducible evidence, with a clean baseline used for verification.
Analyze Android apps in a CTF sandbox using static inspection and Frida hooks, which observe or alter running code. Trace request signing, local storage, and Java-to-native boundaries to reproduce a request accepted by the server.
Add structured logs, performance metrics, and traces that follow requests across Python services. Establish consistent log fields and request IDs so production failures can be investigated using recorded activity and service health signals.
Investigate incorrect, missing, or unexpectedly changed OpenViking memories by tracing memory files back to archived change records and, when needed, source messages. Return an evidence trail, identify gaps, and suggest next steps without modifying data.
Explore unfamiliar code with Codebase Memory to map architecture, trace function calls and dependencies, and assess change impact. Findings are checked against source files, with index freshness and coverage considered before drawing conclusions.
Investigate why a bug, performance change, or experimental result occurred. Compare competing explanations using supporting and contradicting evidence, rank likely causes, and identify the next check that would best resolve uncertainty.