Agent skill · data analytics · jeremylongshore
adobe-observability
Instrument Adobe integrations with redacted structured logs, request/job/activation correlation, service-level indicators, alerts, and evidence retention. Use when the task requires adobe content-safe observability. Trigger with "monitor Adobe API", "Adobe observability", or "App Builder logs".
Why this skill is useful
Provides specific Prometheus metrics and OpenTelemetry tracing patterns for Adobe API integrations that the AI wouldn't reliably generate on its own.
What it needs
Requires grafana, opentelemetry, prometheus installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Adobe Content-Safe Observability Overview Instrument Adobe integrations with redacted structured logs, request/job/activation correlation, service-level indicators, alerts, and evidence retention. This workflow produces a reviewable artifact and evidence before any live side effect. Prerequisites Current first-party Adobe documentation for every selected service, API version, auth flow, limit, and lifecycle. Named product, identity, security, data, budget, release, and operations owners appropriate to the scope. Synthetic or approved non-production fixtures with secret and content canaries. Current Contract App Builder local, Runtime activation, CLI, and Console log surfaces differ. Successful activation persistence is mode-dependent; current Console application logs can provide broader visibility. Runtime log size and retention are bounded and mutable. Recheck the dated evidence map before relying on mutable product behavior. Authentication Log service, operation, environment aliases, request/job/activation IDs, state, status class, duration, retry, bytes, and usage class. Never log secrets, Authorization, signed URLs, prompts, document/image/event content, or direct identifiers. Instructions 1. Define SLOs, telemetry consumers, data classification, retention, and incident evidence needs. 2. Inventory logs, metrics, traces, dashboards, activations, queue evidence, and current blind spots by execution mode. 3. Create a redacted correlation model from ingress through queue, Adobe request/job, storage, and downstream acknowledgement. 4. Measure availability, terminal success, queue age, vendor time, 429s, retries, unknown jobs, duplicates, and cleanup lag. 5. Add alerts tied to actionable runbooks, budget limits, credential/EOL dates, event disablement, and stale assets. 6. Run content/secret/URL canaries, failure drills, retention verification, and dashboard reconciliation. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/adobe-observability