trace-connectors

Configure trace schemas and export connectors for external audit sinks.

Updated May 11, 2026

Search Tags:#schema #audit #observability #trace #harness #connectors

Ready to run

npx skills add https://github.com/AesopScott/mojo --skill trace-connectors

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trace-connectors
Source: https://github.com/AesopScott/mojo/tree/main/harnesses/skills/trace-connectors
Command: npx skills add https://github.com/AesopScott/mojo --skill trace-connectors

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the lack of visibility and auditability in system harnesses by providing a controlled mechanism to define trace schemas and export connectors for external audit sinks.

Core Features & Use Cases

Capability Control: Define exactly what data is recorded, including routes, payloads, and timing, without expanding system authority.
Auditability: Configure export connectors to ensure that system events are captured for debugging, replay, or compliance review.
Use Case: When modifying a Trace harness, use this skill to implement a new audit sink for tracking sensitive API calls while ensuring the change remains bounded and testable.

Quick Start

Use the trace-connectors skill to define a new audit schema and export connector for the current harness boundary.

Frequently Asked Questions about trace-connectors

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

FAQPage Schema

How do I configure trace schemas to improve system observability and auditability?▼

To improve system observability, you configure trace schemas to define exactly what data is recorded, such as routes, payloads, and timing, maintaining strict capability control without expanding system authority boundaries.

What is the best way to implement an audit sink for tracking sensitive API calls in a harness?▼

The best way to track sensitive API calls is configuring export connectors to capture system events for debugging and compliance review, ensuring modifications remain bounded and testable through positive and boundary verification.

Can I use export connectors to log external data without expanding system authority?▼

Yes, you can use export connectors to log external data for compliance review while maintaining capability control, ensuring the harness records only defined data like routes and payloads without expanding system authority boundaries.

When do I need to define trace schemas for external audit sinks?▼

You need to define trace schemas for external audit sinks when modifying a trace harness to enhance system auditability, requiring controlled capability expansion and external data logging for debugging, replay, or compliance review.

Do I need positive and boundary testing to verify export connector configurations?▼

Yes, you need positive and boundary testing to verify export connector configurations, ensuring the trace schemas and audit sinks operate correctly within defined authority boundaries and maintain strict system observability and auditability.