checking-system-logs

Analyze project-scoped bridge logs for Valor agent events and errors.

20|11|Updated Sep 8, 2020
One-click install
npx skills add https://github.com/tomcounsell/ai --skill checking-system-logs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checking-system-logs
Source: https://github.com/tomcounsell/ai/tree/main/.claude/skills/checking-system-logs
Command: npx skills add https://github.com/tomcounsell/ai --skill checking-system-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers debug Valor by filtering and inspecting bridge events and agent interactions on a per-project basis, making it easier to find what happened and where.

Core Features & Use Cases

  • Filter bridge events by project to isolate relevant activity.
  • Inspect event types such as message_received, agent_request, agent_response, agent_timeout, reply_sent, and error.
  • Use practical search patterns (grep and jq) to quickly extract insights from the logs for debugging sessions.
  • Use Case: Debug a timeout or error by querying the bridge log for a specific Valor project and tracing the sequence of messages and responses.

Quick Start

Run a targeted log search for the Valor project to identify recent agent responses and errors.

Frequently Asked Questions about checking-system-logs

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

FAQPage Schema
How do I filter Valor system logs to debug agent interactions for a specific project?

To debug Valor agent interactions, filter bridge logs by project to isolate relevant activity. Inspect event types such as message_received, agent_request, agent_response, and reply_sent to trace the sequence of messages and responses.

What is the best way to trace agent timeouts and errors in Valor bridge logs?

The best way to trace agent timeouts and errors in Valor bridge logs is to query the event taxonomy for agent_timeout and error events. This pinpoints failures and helps you trace the surrounding sequence of messages and responses within project-scoped logs.

How do I use jq and grep to extract event types from project logs?

You use jq and grep to extract event types from project logs by applying practical search patterns to the bridge log location. These queries filter events like message_received and agent_request to quickly extract debugging insights.

Can I debug Valor agent requests and responses on a per-project basis?

Yes, you can debug Valor agent requests and responses on a per-project basis. The log analysis workflow specifies a log location and event taxonomy to filter bridge events, isolating relevant agent activity for focused debugging sessions.

What specific event types should I look for when debugging Valor system logs?

When debugging Valor system logs, look for event types including message_received, agent_request, agent_response, agent_timeout, reply_sent, and error. These events form the taxonomy for tracing agent interactions and debugging outcomes.