agtrace-provider-normalization

Normalize AI agent provider logs into unified domain types.

59|4|Updated Dec 2, 2025
One-click install
npx skills add https://github.com/lanegrid/agtrace --skill agtrace-provider-normalization
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agtrace-provider-normalization
Source: https://github.com/lanegrid/agtrace/tree/main/.agent/skills/agtrace-provider-normalization
Command: npx skills add https://github.com/lanegrid/agtrace --skill agtrace-provider-normalization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides deep knowledge of how agtrace normalizes diverse AI agent log formats into unified domain types, enabling provider implementations, tool normalization, and a schema-on-read architecture.

Core Features & Use Cases

  • Provider adapter architecture: explains the three-tier pattern (Trait-Based Adapter, Provider-Specific Implementation, Unified Domain Types) and how to implement new providers.
  • Schema-on-read workflow: describes lazy parsing, raw logs as source of truth, and type-safe conversion.
  • Practical guidance for adding a new provider, registering adapters, and mapping tools across Claude, Codex, Gemini.
  • Event building and MCP handling: overview of deterministic UUIDs, multi-stream events, and MCP tool handling.

Quick Start

Begin by reviewing the architecture overview and examining existing provider implementations to understand how Discovery, Parser, and ToolMapper are wired together. Then, explore the provider directories under crates/agtrace-providers to see how new providers are integrated.

Frequently Asked Questions about agtrace-provider-normalization

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

FAQPage Schema
How do I unify AI agent provider logs from Claude, Codex, and Gemini into a single schema?

To unify AI provider logs, implement a three-tier adapter pattern consisting of trait-based adapters, provider-specific implementations, and unified domain types. This normalizes diverse log formats into a single domain model.

What is the schema-on-read workflow for normalizing AI log formats?

Schema-on-read normalizes AI log formats by treating raw logs as the source of truth and applying lazy parsing to achieve type-safe conversion. This defers structural parsing until the data is queried or processed.

How do I add a new provider adapter to an AI log normalization system?

To add a new provider, implement Discovery, Parser, and ToolMapper components, then register the adapter in the provider registry. This wires the new provider into the existing unified domain type architecture.

How are tool calls normalized across different AI agent providers?

Tool calls are normalized across AI agent providers using a ToolMapper component within the adapter architecture. It translates provider-specific tool invocation formats into unified domain types.

When do I need to build multi-stream events with deterministic UUIDs for AI logs?

You need multi-stream events with deterministic UUIDs when building unified events from asynchronous AI log streams. This ensures that related log entries across different providers can be deterministically correlated.