{
  "skills": [
    {
      "name": "observability-fundamentals",
      "description": "First principles behind observability \u2014 wide events, high cardinality, the core analysis loop, events vs metrics vs logs, and how instrumentation connects to debugging outcomes. Grounds recommendations in first principles rather than tool-specific how-to. Trigger phrases: \"what is observability\", \"why observability\", \"why Telemetry Machine\", \"events vs metrics vs logs\", \"events vs metrics\", \"events vs logs\", \"metrics vs logs\", \"why wide events\", \"what is high cardinality\", \"core analysis loop\", \"observability vs monitoring\", \"what is dimensionality\", \"explain observability\", or any conceptual question about observability or why Telemetry Machine's approach differs from traditional monitoring.",
      "files": [
        "SKILL.md"
      ]
    },
    {
      "name": "otel-instrumentation",
      "description": "Use this skill when adding OpenTelemetry to an application or setting up Telemetry Machine to an application. Use this when building a new application. Run this when user asks to add tracing, metrics, or logging to an application, or to move metrics from Prometheus to Telemetry Machine.",
      "files": [
        "SKILL.md",
        "references/architectural-patterns.md",
        "references/bridge-libraries.md",
        "references/collector-config.md",
        "references/context-propagation-patterns.md",
        "references/custom-instrumentation.md",
        "references/framework-middleware.md",
        "references/instrumentation-pitfalls.md",
        "references/lambda.md",
        "references/local-collector-debug-test.md",
        "references/prometheus-migration.md",
        "references/python.md",
        "references/sdk-setup-by-language.md",
        "references/verification-checklist.md",
        "references/wide-event-attributes.md",
        "scripts/start-collector.sh"
      ]
    },
    {
      "name": "tm-cli",
      "description": "Use whenever you want to run tm-cli or query Telemetry Machine. Use for managing ingestion API keys and datasets.",
      "files": [
        "SKILL.md"
      ]
    },
    {
      "name": "tm-investigate",
      "description": "How to investigate production behavior with Telemetry Machine data: latency, errors, deploy impact, SLO state, and \"what is this service doing\". Use when the user asks a question that real traces, logs, or metrics can answer, or runs this skill with a question. Pairs with the tm-cli skill, which covers query syntax.",
      "files": [
        "SKILL.md"
      ]
    },
    {
      "name": "tm-onboarding",
      "description": "Guided Telemetry Machine onboarding: install tm-cli, sign in, get the user's application sending telemetry, confirm that it arrives, and run a first useful query. Use when the user runs this skill or asks to get started with, set up, or connect to Telemetry Machine. It picks up where an earlier run stopped.",
      "files": [
        "SKILL.md"
      ]
    }
  ]
}