telemetry

Emit auditable skill activity telemetry events via ~/.agents/bin/emit-telemetry.

2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/grimlor/universal-dev-skills --skill telemetry-grimlor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: telemetry
Source: https://github.com/grimlor/universal-dev-skills/tree/main/skills/telemetry
Command: npx skills add https://github.com/grimlor/universal-dev-skills --skill telemetry-grimlor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

telemetry prevents silent, non-compliant skill execution by defining a strict, auditable emission protocol for skill reads, phase steps, compliance checks, and completions.

Core Features & Use Cases

  • Immediate event emission: Emits skill.invoked right after a skill is read and before any procedure step, enabling observable compliance behavior.
  • Completion and phase traceability: Emits skill.completed only after a full procedure finishes, plus phase.started/phase.completed and compliance.check events for workflow steps.
  • Operational guardrails: Halts execution if the required telemetry binary is unavailable to avoid creating incomplete telemetry records.

Quick Start

Ask your agent to read the telemetry skill first and then emit telemetry events exactly as the Iron Laws specify during the entire session.

Frequently Asked Questions about telemetry

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

FAQPage Schema
How do I log agent compliance events in real time during workflow execution?

Real-time event logging prevents silent non-compliant skill execution by emitting telemetry immediately after skill reads and before procedure steps, ensuring every workflow phase and compliance check is recorded for audit readiness.

What happens if the telemetry binary is missing during an agent session?

If the telemetry binary is missing, the agent session halts execution immediately to prevent creating incomplete telemetry records and ensure all skill activity remains strictly auditable under the defined protocol.

How do I trace workflow phases and compliance checks across multiple loaded skills?

Workflow tracing across multiple loaded skills requires emitting phase.started, phase.completed, and compliance.check events in strict order, capturing every workflow step and compliance verification with accurate outcome values.

Why do I need real-time event logging for audit readiness in agent workflows?

Real-time event logging for audit readiness prevents silent non-compliant skill execution by enforcing a strict emission protocol that records skill reads, phase steps, and completions immediately, ensuring no compliance gaps exist in agent workflows.

What compliance events should be recorded when an agent reads and executes a skill?

When an agent reads and executes a skill, record skill.invoked immediately after the read, phase.started and phase.completed for workflow steps, compliance.check for verifications, and skill.completed after the full procedure finishes.

Can I batch telemetry emissions to improve performance during multi-skill agent sessions?

No, batching telemetry emissions is prohibited; the protocol requires emitting events immediately via the telemetry binary to guarantee audit readiness and prevent incomplete telemetry records during multi-skill agent sessions.