zap-cli

Query and trace agent events with JSON output via CLI.

22|4|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/joelhooks/atproto-agent-network --skill zap-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zap-cli
Source: https://github.com/joelhooks/atproto-agent-network/tree/main/.agents/skills/zap-cli
Command: npx skills add https://github.com/joelhooks/atproto-agent-network --skill zap-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline the debugging and health monitoring of autonomous agents by providing a dedicated observability CLI that outputs structured data in JSON for easy analysis.

Core Features & Use Cases

  • View, filter, and analyze agent events in real time using a simple CLI.
  • Query and trace decision flows, tool calls, and memory operations to diagnose issues.
  • Use presets and quick-start workflows to monitor network health and performance.

Quick Start

Install zap-cli and run it against your agent network to start observing real-time events.

Frequently Asked Questions about zap-cli

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

FAQPage Schema
How do I debug autonomous agent events and trace tool calls from a CLI?

You can debug autonomous agent events by using an observability CLI to view, query, and trace tool calls, memory operations, and decisions. It outputs structured JSON data, making it easy to filter events and analyze agent health in real time.

What is agent observability and how does tracing decision flows work?

Agent observability monitors autonomous agent health by tracing decision flows and events. It works by querying an event store to diagnose issues across prompts and tool calls, providing structured JSON output for detailed analysis.

Do I need a specific environment to run an observability CLI for agent debugging?

Yes, running an observability CLI for agent debugging requires a local Bun or Node environment. You also need access to the agent event store to successfully query logs, trace decisions, and monitor network health.

Can I use jq to filter and analyze JSON output from agent event logs?

Yes, you can use jq to filter agent event logs because the observability CLI provides jq-friendly JSON formatting. This allows you to easily parse structured data from tool calls, memory operations, and prompts during debugging.

What is the best way to monitor autonomous agent network health and performance?

The best way to monitor agent network health is using an observability CLI with built-in presets and quick-start workflows. These presets allow you to rapidly query the event store and trace performance issues across the edge.