get-event-type-info

Inspect MNG event-type metadata and raw log files from the agent state directory.

401|41|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/imbue-ai/mng --skill get-event-type-info
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: get-event-type-info
Source: https://github.com/imbue-ai/mng/tree/main/libs/mng_claude_zygote/imbue/mng_claude_zygote/resources/defaults/thinking/skills/get-event-type-info
Command: npx skills add https://github.com/imbue-ai/mng --skill get-event-type-info

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers understand MNG event types and access raw log data to diagnose issues and validate behaviors without sifting through scattered files.

Core Features & Use Cases

  • Event-type metadata overview: quickly inspect the fields and structure of each event type.
  • Raw log access: read raw events from the agent state directory for a given source.
  • Investigation guidance: provides commands and queries to locate conversations, messages, and agent events for debugging.

Quick Start

Inspect raw events for a specific source by viewing its events.jsonl file in the MNG agent state directory.

Frequently Asked Questions about get-event-type-info

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

FAQPage Schema
How do I inspect raw event logs for MNG agent debugging?

Event types for MNG agent monitoring include messages, mng_agents, scheduled, stop, conversations, monitor, and claude_transcript, each providing structured metadata for debugging agent behavior.

Can I filter raw events by conversation_id in the agent state directory?

Raw event inspection provides both high-level summaries of event type structures and low-level access to individual log entries, enabling engineers to validate behaviors without manually sifting through scattered files.

What's the best way to understand event type structures before debugging?

Event inspection guidance offers specific commands and queries to locate conversations, messages, and scheduled events, streamlining the process of diagnosing issues across different MNG agent sources.

Why does my MNG agent debugging require accessing the agent state directory?

MNG agent debugging requires accessing the agent state directory because the raw events.jsonl files containing the actual execution logs and event metadata are stored exclusively in $MNG_AGENT_STATE_DIR.