session-monitor-agent

Monitor chat session events across tenants to detect latency anomalies, error patterns, and attribution drift.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/MCERQUA/jam-skills --skill session-monitor-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-monitor-agent
Source: https://github.com/MCERQUA/jam-skills/tree/main/session-monitor-agent
Command: npx skills add https://github.com/MCERQUA/jam-skills --skill session-monitor-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables cross-tenant analysis of chat session events, detecting latency anomalies, error patterns, and attribution drift to improve the mesh agent's nightly reflections.

Core Features & Use Cases

  • Cross-tenant Analysis: Visibility across all chat session events, regardless of tenant.
  • Latency Anomaly Detection: Identify latency issues across different tenants.
  • Error Pattern Correlation: Correlate errors across multiple tenants for shared root causes.
  • Reflection Posting: Automated posting of analysis reflections to the nightly chatroom.
  • Use Case: For instance, identify a cross-tenant pattern of error responses that might indicate a system issue, leading to quicker resolution and better user experience.

Quick Start

Use the session-monitor-agent skill to analyze and reflect on chat session events for a given date.

Frequently Asked Questions about session-monitor-agent

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

FAQPage Schema
How do I detect latency anomalies across multiple tenant chat sessions?

To detect latency anomalies across multiple tenant chat sessions, you monitor cross-tenant chat session events and identify latency deviations. This skill analyzes session data and system reports to pinpoint latency issues across different tenants for quicker resolution.

What is cross-tenant attribution drift in chat session analysis?

Cross-tenant attribution drift in chat session analysis refers to inconsistencies in how interactions are credited across different tenants. This skill monitors chat session events to detect and report on attribution drift alongside latency anomalies and error patterns.

Can I correlate error patterns across different tenants for shared root causes?

Yes, you can correlate error patterns across different tenants for shared root causes. This skill provides cross-tenant analysis of chat session events to identify shared system issues, leading to quicker resolution and improved user experience.

Do I need access to tenant chat data and system reports for anomaly detection?

Yes, you need access to tenant chat data and system reports for anomaly detection. This skill requires access to these data sources to effectively monitor and analyze chat session events for latency anomalies and attribution drift.

How do I automate posting analysis reflections to a nightly chatroom?

To automate posting analysis reflections to a nightly chatroom, you use a skill that generates and posts insights from chat session analysis. This skill automates the posting of analysis reflections to improve the mesh agent's nightly reflections.