observability

Define versioned observability contracts for cross-boundary telemetry events.

1|Updated Mar 17, 2026

Search Tags:#observability #instrumentation #telemetry #model-usage #event-schema #token-accounting

Ready to run

npx skills add https://github.com/yknothing/prodcraft --skill observability-yknothing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: observability
Source: https://github.com/yknothing/prodcraft/tree/main/skills/cross-cutting/observability
Command: npx skills add https://github.com/yknothing/prodcraft --skill observability-yknothing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-cutting instrumentation design to define structured telemetry contracts that survive handoffs across phases and components, enabling reliable debugging, cost accounting, and governance.

Core Features & Use Cases

Define versioned event schemas to capture skill invocation, model usage, and runtime boundaries.
Instrument shared entry points and separate signal production from consumption, enabling dashboards and responders to adapt independently.
Use for AI execution telemetry, token accounting, and workflow visibility across the lifecycle.

Quick Start

Define the observable telemetry contract and begin instrumenting the shared boundaries.

Frequently Asked Questions about observability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I design telemetry contracts for AI execution and model usage?▼

Design telemetry contracts by defining standardized, versioned event schemas that capture model usage and runtime boundaries. This enables reliable debugging, cost accounting, and governance across cross-boundary pipelines.

What is the best way to implement token accounting across workflow transitions?▼

Implement token accounting by instrumenting shared runtime boundaries with canonical fields for model execution. This separates signal capture from consumption, enabling dashboards to adapt independently while tracking token usage.

How do I capture skill invocation telemetry without coupling production to consumption?▼

Capture skill invocation telemetry by defining versioned event schemas at shared entry points. This clear separation allows signal production and consumption to evolve independently, preventing pipeline coupling.

When do I need versioned event schemas for cross-boundary observability?▼

You need versioned event schemas for cross-boundary observability when instrumentation must survive handoffs across phases and components. This ensures structured telemetry contracts remain reliable for debugging and governance.

Can I use this observability approach for runtime boundaries like workflow transitions?▼

Yes, this observability approach applies to runtime boundaries including workflow transitions, model execution, and skill invocation. It defines standardized contracts enabling schema design and instrumentation across pipelines.

Why separate signal capture from consumption in pipeline instrumentation?▼

Separate signal capture from consumption in pipeline instrumentation to allow dashboards and responders to adapt independently. This decoupling ensures telemetry contracts survive component handoffs without breaking downstream consumers.