Stable event contracts
The agent is guided toward named events, bounded snake_case fields, explicit units, and identifiers that remain useful in SQL.
What the skill covers
Instructions that end in inspectable data
Safe collection boundaries
Raw prompts, completions, credentials, authorization headers, and private payloads stay out of the analytics path by default.
An end-to-end result
Instrumentation is not finished until representative events arrive and a query or dashboard proves the workflow is visible.
Start here
Paste one bounded brief
Replace the placeholder with a server-side API key, then ask the agent to inspect the repository before choosing event boundaries.
agent prompt
AI agent observability prompt
text
Instrument this project with structured logs using /skill.md.
Use this Telemetry API key: YOUR_API_KEY
Please:
1. Find the most important user-facing flows, background jobs, and AI/tooling workflows.
2. Add structured logging with pragmatic snake_case tables and fields.
3. Capture the key signals for each workflow, including status, latency, identifiers, and error context when relevant.
4. Send test events to Telemetry and verify that ingestion works.
5. Create a high-level dashboard with charts and tables that summarize the most important signals in this project.
6. Tell me what you instrumented, which tables you created, and which dashboard views I should review first.
Prefer small, composable events over giant payloads, and optimize for dashboards that humans can scan quickly.Review boundary
Keep a human in control of the contract
The skill helps an agent find useful workflow boundaries, but your team still owns the event meaning, allowed fields, retention policy, and operational thresholds.
- Review every new table and field before deployment.
- Use bounded identifiers instead of private payloads.
- Verify success, failure, and terminal outcomes.
Continue the workflow
AI agent telemetry dashboard template
Start with a bounded event schema and a reviewable dashboard for runs, tools, latency, cost, failures, and outcomes.
Open guideAI agent monitoring
Choose useful run, tool, model, cost, failure, and outcome boundaries.
Open guideAgent prompt pack
Copy focused briefs for product analytics, OpenAI costs, APIs, revenue, and jobs.
Open guideStructured logging guide
Review event design, privacy boundaries, delivery behavior, and verification.
Open guideClaude Code observability
Apply the reviewed event contract and verification loop from a Claude Code implementation pass.
Open guideCursor telemetry setup
Use a focused Cursor workflow for activation, retention, and inspectable dashboard instrumentation.
Open guideCodex instrumentation prompt
Give Codex a bounded brief for product, reliability, and outcome telemetry with verification.
Open guideInstrument the first workflow, then inspect the result
Start free with a provisioned workspace, API key, sample event, and dashboard. Replace the sample with reviewed production events when the shape looks right.