event-logging

Log user actions to the dashboard activity feed with structured metadata.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/JBODE-mhhs/Zeus2.0-public --skill event-logging-jbode-mhhs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-logging
Source: https://github.com/JBODE-mhhs/Zeus2.0-public/tree/main/templates/analyst/.claude/skills/event-logging
Command: npx skills add https://github.com/JBODE-mhhs/Zeus2.0-public --skill event-logging-jbode-mhhs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Events are how the dashboard activity feed knows what you're doing. No events = you look dead. You need to consistently log session starts, task completions, and major coordination actions to keep the dashboard accurate and actionable.

Core Features & Use Cases

  • Log session starts and ends to anchor activity timelines.
  • Record task completions and cross-agent coordination for auditing.
  • Provide structured metadata for analytics and monitoring across missions.

Quick Start

Log a session start event with agent metadata to record the session for the dashboard.

Frequently Asked Questions about event-logging

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

FAQPage Schema
How do I log user actions to an activity feed for dashboard auditing?

You can log session starts, task completions, and cross-agent coordination across Zeus workflows. This enforces a defined event schema with consistent metadata to ensure your dashboard activity feed remains accurate and actionable for analytics.

What is event logging used for in dashboard telemetry?

Event logging records user actions to fuel the dashboard activity feed, anchoring activity timelines with session starts and task completions. It provides structured metadata essential for monitoring, analytics, and auditing across missions.

How do I record cross-agent coordination events for analytics?

You record cross-agent coordination by logging these actions to the dashboard activity feed with structured metadata. This enforces a defined event schema, ensuring scalable persistence to support reliable analytics and auditing.

Do I need a defined event schema to log task completions?

Yes, using a defined event schema to log task completions enforces consistent metadata across your events. This ensures scalable persistence, keeping your dashboard activity feed accurate for analytics and auditing.

What happens if I do not log session starts to the activity feed?

Without logging session starts, your dashboard activity feed lacks timeline anchors, making agents look inactive. Consistent event logging is required to keep the dashboard accurate, actionable, and prepared for auditing.