skills

Use the `ollygarden` CLI to query OllyGarden services, insights, analytics, organizations, and webhooks from the terminal. Use when the user asks to run ollygarden commands, list services or insights, set up or debug webhooks, manage auth contexts (multiple orgs or environments), or pipe OllyGarden data through jq. Triggers on "ollygarden cli", "og cli", "list my services", "fetch insights from cli", "ollygarden auth", "create a webhook", "ollygarden context", "ollygarden --json".

Fetch active OllyGarden service insights from the Olive API and apply remediation fixes to the current codebase. Use when the user asks to get insights, fix insight, address insight, or remediate insight for the current service. Retrieves insights grouped by impact, then applies fixes strictly following the API-provided remediation_instructions.

Universal OpenTelemetry auto-instrumentation planning and review guidance. Use when deciding whether agent/library instrumentation is sufficient, when tuning auto-instrumented boundaries, when avoiding duplicate manual spans, or when reviewing auto instrumentation for noise, PII, volume, and business value.

Ollygarden's recommended patterns and anti-patterns for OpenTelemetry declarative configuration. Use when reviewing or authoring otel.yaml files, when deciding whether declarative config is right for a project, or when the user asks for "the right way" to configure OpenTelemetry. Triggers on "otel best practices", "otel anti-patterns", "is this otel config correct", "should I use declarative config".

Ollygarden's recommended pattern for setting up the OpenTelemetry SDK in Go services using otelconf. Covers project structure, the Providers struct, no-op fallback, runtime attribute injection, and the zap log bridge. Use when adding OTel to a Go project, structuring telemetry code, or reviewing an existing setup. Triggers on "go otel setup", "go telemetry pattern", "Providers struct go otel".