How do I install the Checking System Logs skill?

Run npx skillmds add majiayu000/checking-system-logs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Checking System Logs safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Checking System Logs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Checking System Logs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Checking System Logs?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Checking System Logs by majiayu000 — Agent Skill

Name: Checking System Logs
Rating: 4.5 (4 reviews)
Author: majiayu000

Checking System Logs

Find bridge events, agent responses, timeouts, and errors in system logs. ALWAYS filter by project name. Use when debugging system behavior, investigating errors, or checking what the agent did.

majiayu000 2e6bb31 2 files · 2.5 KB Updated Sep 9, 2026 567 repo stars

File contents

System Logs

Location: /Users/valorengels/src/ai/logs/bridge.events.jsonl

IMPORTANT: Always filter by project to get relevant results.

Fields

project - required filter ("DM", "Valor", "Django Project Template", etc.)
type - event type (see below)
chat - group name (null for DMs)
session_id - e.g., "tg_dm_179144806"
sender - who triggered the event

Event Types

message_received - incoming message
agent_request - request sent to agent
agent_response - Valor's response
agent_timeout - response timed out
reply_sent - message sent back to user
error - system error

Query Examples

# ALWAYS filter by project first, then by type or other criteria

# All recent events for a project
grep '"project": "Valor"' /Users/valorengels/src/ai/logs/bridge.events.jsonl | tail -20 | jq .

# Agent responses for a project
grep '"project": "Valor"' /Users/valorengels/src/ai/logs/bridge.events.jsonl | grep '"type": "agent_response"' | tail -10 | jq .

# Errors for a project
grep '"project": "Valor"' /Users/valorengels/src/ai/logs/bridge.events.jsonl | grep '"type": "error"' | tail -10 | jq .

# Timeouts for a project
grep '"project": "Valor"' /Users/valorengels/src/ai/logs/bridge.events.jsonl | grep '"type": "agent_timeout"' | tail -10 | jq .

# Search keyword within a project
grep '"project": "Valor"' /Users/valorengels/src/ai/logs/bridge.events.jsonl | grep -i "keyword" | tail -10 | jq .

List Available Projects

grep -o '"project": "[^"]*"' /Users/valorengels/src/ai/logs/bridge.events.jsonl | sort -u

If No Results

If a project filter returns no results, list available projects and report them:

# No results? Check available projects:
grep -o '"project": "[^"]*"' /Users/valorengels/src/ai/logs/bridge.events.jsonl | sort -u
# Then retry with a valid project name from the list

---name: checking-system-logsdescription: Find bridge events, agent responses, timeouts, and errors in system logs. ALWAYS filter by project name. Use when debugging system behavior, investigating errors, or checking what the agent did.--- # System Logs **Location**: `/Users/valorengels/src/ai/logs/bridge.events.jsonl` **IMPORTANT**: Always filter by project to get relevant results. ## Fields - `project` - **required filter** ("DM", "Valor", "Django Project Template", etc.) - `type` - event type (see below) - `chat` - group name (null for DMs) - `session_id` - e.g., "tg_dm_179144806" - `sender` - who triggered the event ## Event Types - `message_received` - incoming message - `agent_request` - request sent to agent - `agent_response` - Valor's response - `agent_timeout` - response timed out - `reply_sent` - message sent back to user - `error` - system error ## Query Examples ```bash # ALWAYS filter by project first, then by type or other criteria # All recent events for a project grep '"project": "Valor"' /Users/valorengels/src/ai/logs/bridge.events.jsonl | tail -20 | jq . # Agent responses for a project grep '"project": "Valor"' /Users/valorengels/src/ai/logs/bridge.events.jsonl | grep '"type": "agent_response"' | tail -10 | jq . # Errors for a project grep '"project": "Valor"' /Users/valorengels/src/ai/logs/bridge.events.jsonl | grep '"type": "error"' | tail -10 | jq . # Timeouts for a project grep '"project": "Valor"' /Users/valorengels/src/ai/logs/bridge.events.jsonl | grep '"type": "agent_timeout"' | tail -10 | jq . # Search keyword within a project grep '"project": "Valor"' /Users/valorengels/src/ai/logs/bridge.events.jsonl | grep -i "keyword" | tail -10 | jq . ``` ## List Available Projects ```bash grep -o '"project": "[^"]*"' /Users/valorengels/src/ai/logs/bridge.events.jsonl | sort -u ``` ## If No Results If a project filter returns no results, list available projects and report them: ```bash # No results? Check available projects: grep -o '"project": "[^"]*"' /Users/valorengels/src/ai/logs/bridge.events.jsonl | sort -u # Then retry with a valid project name from the list ```

Frequently asked questions