More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Repair Observability, Metrics & Trace Failures

    1

    Repair Observability, Metrics & Trace Failures is a bounded ToolForge Labs workflow.

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Repair Observability, Metrics & Trace Failures

    Repair Observability, Metrics & Trace Failures

    Example session with this skill installed

    Our service logs a request ID, but traces frequently break across async jobs and metrics explode in cardinality after a deployment. Some exporter failures are silent. Repair the observability pipeline without logging secrets or changing production alert policy.

    • Read your context and instructions
    • Compiled the repair observability metrics

    The likely failure is a contract mismatch around logging, metrics, traces, correlation, sampling, cardinality, exporters, alert signals, context propagation, and telemetry loss. I would reconstruct one canonical invariant, identify the layer violating it, apply the smallest bounded repair, and add deterministic boundary/failure/control tests. Existing security and product policy would be preserved. If repository files are available I can map the repair to exact paths; otherwise I would provide concrete pseudocode and a verification plan without claiming execution.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Repair Observability, Metrics & Trace Failures is a bounded ToolForge Labs workflow. Diagnose and repair logging, metrics, traces, correlation, sampling, cardinality, exporters, alert signals, context propagation, and telemetry loss. Works from repositories or partial logs/configuration. Produces bounded repair patterns and deterministic tests while preserving existing product/security policy and avoiding invented execution claims. It works from a full repository or partial evidence such as snippets, logs, configuration, traces, tickets, and architecture notes. The skill preserves existing product and security policy, separates verified facts from assumptions, avoids invented execution claims, and produces concrete repair or review steps with focused deterministic validation or traceable evidence.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for LLM Ops.

    Requires clear evidence (logs, config, or code) to provide a diagnosis. Cannot verify production deployments or live traffic without direct environment access.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 2 months ago

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    Use a clean branch or a controlled review workspace. Supply repository files, logs, traces, configuration, or evidence needed for the task. Review all patches/findings before merge or operational action; keep production credentials and destructive production actions out of the workflow.

    Listed2 months ago
    Updated9 days ago

    What's inside

    Frequently Asked Questions

    The skill identifies root causes for broken trace propagation, resolves high-cardinality metric spikes that crash exporters, and fixes inconsistent log correlation across microservices.

    This skill is compatible with any AI agent platform supporting structured tool use and filesystem access, including AutoGPT, CrewAI, and LangGraph-based agents.

    It provides full support for the OpenTelemetry (OTel) ecosystem, including Prometheus, Grafana, Jaeger, Zipkin, and the ELK Stack across cloud-native environments.

    No, the skill follows a strict verification protocol that uses local fixtures and fake services to validate telemetry repairs before they are applied to your codebase.

    The skill includes logic for PII detection and maps ownership boundaries to ensure that new logging or tracing instrumentation adheres to your security and privacy policies.

    You receive the production-ready skill definition, integration documentation, and access to all future updates to ensure compatibility with evolving OpenTelemetry standards.

    New in LLM Ops