observeinc

Investigate alerts using systematic SRE methodology to understand issues, assess impact, test hypotheses, and identify root causes with evidence-based analysis. Use when: (1) User asks to investigate or analyze an alert (2) User mentions a specific alert or monitor that is firing (3) Debugging production issues or incidents (4) User asks about alert root cause or impact (5) User wants to understand why something is alerting (6) Performing incident response or triage.

Troubleshoot and debug Observe Agent data collection on Kubernetes. Use this skill whenever the user reports any K8s-side problem with Observe — pods crashing, stuck Pending, ImagePullBackOff, "no data in Observe", missing datastreams, suspected token/secret issues, endpoint reachability failures, or platform-specific symptoms on Fargate / GKE Autopilot / EKS Auto Mode — even if they don't explicitly say "debug" or "Observe Agent." Covers pod status, secrets, endpoint reachability, debug logging, self-monitoring metrics, and platform-specific failure modes.

Troubleshoot and debug Observe Agent data collection on Linux hosts. Use this skill whenever the user reports any host-side problem with Observe — the agent failing to start, `observe-agent status` reporting errors, `init-config` failing with unknown flags, "no data in Observe" from a Linux host, fleet heartbeats not arriving, apt/yum repo failures, `unauthorized` token errors, or systemd service failures — even if they don't explicitly say "debug" or "observe-agent." Covers agent status, live log tailing, config validation, debug logging, datastream ingestion verification, and common error patterns.

End-to-end onboarding of a Kubernetes cluster to Observe — creates the backend datastreams + content via the Observe CLI and deploys the observe/agent helm chart. Use for ANY request to install or set up the Observe Agent on Kubernetes, onboard a K8s cluster to Observe, or send K8s data to Observe — across any flavor (EKS, GKE, AKS, GKE Autopilot, EKS Fargate, EKS Auto Mode, minikube, kind, on-prem). Do NOT route a Kubernetes onboarding request to a generic datastream-creation flow; always orchestrate via this skill, which delegates to setup-k8s-backend and setup-k8s-collection.

End-to-end Host Explorer deployment for Observe — creates backend resources (datastreams, content, ingest token) via the Observe CLI and installs the observe-agent on a Linux host. Use this skill whenever the user mentions setting up Observe on a Linux machine, onboarding a host (Ubuntu, Debian, RHEL, CentOS) to Observe, deploying host monitoring from the terminal or CI, or replacing the Observe UI's Host setup wizard — even if they don't say "Host Explorer" explicitly. Orchestrates setup-linux-host-backend and setup-linux-host-collection.

Contains dataset kind selection, column selection rules, core syntax, and the skill index. NEVER generate OPAL, and NEVER invoke an opal-* reference, without first loading this skill.

Use the Observe CLI (`observe`) to investigate production systems and pull telemetry. Reach for this skill whenever the user wants to: search or tail logs; query metrics (CPU, memory, latency, error rate, request volume, custom app metrics); explore traces and spans; correlate events across services, hosts, containers, or Kubernetes resources; investigate or triage alerts (what fired, why, what's still active, related signals); debug an incident or production issue; check service or system health; compare service RED metrics or dependencies; figure out what's happening with a customer, deployment, or user; find which services emit a given tag or label; slice production data by service, environment, region, host, pod, status code, etc.; or pull any observability data out of the platform for analysis, dashboards, or scripting. Also covers the underlying primitives the CLI exposes (datasets, OPAL queries, knowledge-graph tag search, alerts, AI agent skills, auth) when the user asks about them directly.

Installs and configures OpenTelemetry auto-instrumentation for applications written in Java, .NET, Node.js, Python, Ruby. Use when instrumenting applications with opentelemetry auto-instrumentation, auditing existing auto-instrumentation implementations, migrating from vendor locked instrumentations to OpenTelemetry, or checking for latest versions of instrumentation libraries.

Use the Observe CLI (`observe`) to investigate production systems and pull telemetry. Reach for this skill whenever the user wants to: search or tail logs; query metrics (CPU, memory, latency, error rate, request volume, custom app metrics); explore traces and spans; correlate events across services, hosts, containers, or Kubernetes resources; investigate or triage alerts (what fired, why, what's still active, related signals); debug an incident or production issue; check service or system health; figure out what's happening with a customer, deployment, or user; find which services emit a given tag or label; slice production data by service, environment, region, host, pod, status code, etc.; or pull any observability data out of the platform for analysis, dashboards, or scripting. Also covers the underlying primitives the CLI exposes (datasets, OPAL queries, knowledge-graph tag search, alerts, monitors, AI agent skills, auth) when the user asks about them directly.

Create git branches with a username prefix. Use when creating new branches, checking out new branches, or when the user asks to start work on a feature, fix, or task.

Create commit messages for git

Investigate alerts using systematic SRE methodology to understand issues, assess impact, test hypotheses, and identify root causes with evidence-based analysis. Use when: (1) User asks to investigate or analyze an alert (2) User mentions a specific alert or monitor that is firing (3) Debugging production issues or incidents (4) User asks about alert root cause or impact (5) User wants to understand why something is alerting (6) Performing incident response or triage.

Troubleshoot and debug Observe Agent data collection on Kubernetes. Use this skill whenever the user reports any K8s-side problem with Observe — pods crashing, stuck Pending, ImagePullBackOff, "no data in Observe", missing datastreams, suspected token/secret issues, endpoint reachability failures, or platform-specific symptoms on Fargate / GKE Autopilot / EKS Auto Mode — even if they don't explicitly say "debug" or "Observe Agent." Covers pod status, secrets, endpoint reachability, debug logging, self-monitoring metrics, and platform-specific failure modes.

End-to-end onboarding of a Kubernetes cluster to Observe — creates the backend datastreams + content via the Observe CLI and deploys the observe/agent helm chart. Use for ANY request to install or set up the Observe Agent on Kubernetes, onboard a K8s cluster to Observe, or send K8s data to Observe — across any flavor (EKS, GKE, AKS, GKE Autopilot, EKS Fargate, EKS Auto Mode, minikube, kind, on-prem). Do NOT route a Kubernetes onboarding request to a generic datastream-creation flow; always orchestrate via this skill, which delegates to setup-k8s-backend and setup-k8s-collection.

Contains dataset kind selection, column selection rules, core syntax, and the skill index. NEVER generate OPAL, and NEVER invoke an opal-* reference, without first loading this skill.

Installs and configures OpenTelemetry auto-instrumentation for applications written in Java, .NET, Node.js, Python, Ruby. Use when instrumenting applications with opentelemetry auto-instrumentation, auditing existing auto-instrumentation implementations, migrating from vendor locked instrumentations to OpenTelemetry, or checking for latest versions of instrumentation libraries.

Add one or more OpenTelemetry Collector components (receivers, processors, exporters, connectors, extensions) to the observe-agent distribution. Use for ALL requests that mention adding, including, or enabling a new OTel component. Triggers: add receiver, add processor, add exporter, add connector, add extension, new OTel component, include component, enable component, add otel, otelcol component.

Release a new version of the Observe Agent. Use when the user asks to release, tag, publish, or cut a new version of the observe-agent, or mentions the release process.

Run a local end-to-end smoke test of the observe-agent to verify it collects and exports telemetry correctly. Use when the user wants to verify their branch changes work, run a smoke test, test the agent locally, or validate the observe-agent pipeline before committing or merging.

Check for updates to OpenTelemetry Collector components and dependencies. Use when the user asks about upgrading OTel, checking for new collector versions, or reviewing upstream OpenTelemetry changes.

Deploy and troubleshoot the Observe AWS Collection stack in a single AWS account. Use when a customer needs help deploying a CloudFormation stack that collects AWS logs, metrics, and config data and sends it to Observe. Covers parameter selection, filedrop setup, metric stream configuration, poller configuration, and common errors.

Query and manage Observe using the Observe CLI. Use when the user wants to run OPAL queries, list datasets, manage objects, or interact with their Observe tenant from the command line.