cs2-stats-monitor-5e

Query and monitor 5E CS2 player stats and match performance in real-time with customizable player lists and detailed match analysis.

Security Scan

The skill's code, runtime instructions, and resource needs align with its stated purpose (monitoring 5E CS2 matches); it performs HTTP queries to 5eplay endpoints and stores a small local state file but requests no credentials or unusual privileges.

Purpose & Capability

Name/description match the implemented behavior: the script polls 5eplay/5E endpoints, extracts per-match stats, and formats reports. Required dependencies (Python + aiohttp) are proportional to the task.

Instruction Scope

SKILL.md instructs running the included Python script and using an optional config.json; the script performs network calls to 5eplay endpoints and writes a local state file (.cs_monitor_state.json). This behavior is expected for continuous monitoring, but users should be aware the tool persists monitoring state locally and performs continuous polling when run without --once.

Install Mechanism

No install spec; this is an instruction-only skill with a bundled script. No external downloads or installers are used.

Credentials

The skill declares no required environment variables or credentials. The SKILL.md notes that season overview requires a login cookie, but the skill does not request or store secrets by default. Network access to 5eplay endpoints is required and expected.

Persistence & Privilege

always:false and no special privileges. The script stores a local state file in its scripts directory; it does not attempt to modify other skills or system-wide configs.

Assessment

This skill appears coherent with its purpose. Before installing: (1) review and, if desired, run the script in an isolated environment (or a container) so its network calls are contained; (2) expect it to create .cs_monitor_state.json in the scripts directory and to read ../config.json for defaults; (3) the tool queries 5eplay/gate endpoints — if you need season-overview data you may have to supply a login cookie manually (the skill does not request credentials automatically); (4) if you have concerns, read the included scripts/cs_monitor.py source (it's small and transparent) or run with --once to confirm behavior before enabling continuous monitoring.

CS Stats Monitor (Generic)

5E Platform CS2 Stats Query and Real-time Monitoring Tool (Generic Version).

Core Capabilities

1. Query Stats

Query detailed data of the last 5 matches for specified players.

# Query single player's last 5 matches
python {SKILL_DIR}/scripts/cs_monitor.py --once --players <player_name>

# Query multiple players
python {SKILL_DIR}/scripts/cs_monitor.py --once --players player1 player2 player3

# Use default player list (set in config)
python {SKILL_DIR}/scripts/cs_monitor.py --once

2. Real-time Monitoring

Background continuous polling, automatically output reports when new matches are detected.

# Start monitoring (default 60s polling)
python {SKILL_DIR}/scripts/cs_monitor.py --players player1 player2

# Custom polling interval
python {SKILL_DIR}/scripts/cs_monitor.py --players player1 --interval 30

# Reset monitoring state
python {SKILL_DIR}/scripts/cs_monitor.py --reset

Start Method: Use tmux to run monitoring in background, check output regularly.

# Recommended: tmux background run
tmux new-session -d -s cs-monitor
tmux send-keys -t cs-monitor "python {SKILL_DIR}/scripts/cs_monitor.py --players player1 player2" Enter

# Check output
tmux capture-pane -t cs-monitor -p

3. Configuration File (Optional)

Create {SKILL_DIR}/config.json to set default players:

{
  "default_players": ["player1", "player2", "player3"],
  "default_interval": 60
}

Data Capabilities

Per Match:

• Core Metrics: Rating, ADR, KAST, RWS, K/D/A
• Kill Details: Headshot rate, first kill, first death, AWP kills, multi-kills (3K/4K/5K)
• Clutches: 1v1~1v5 success count
• Utility: Flash assists, team flashes, utility damage, bomb plants/defuses
• Sides: T-side/CT-side K/D/Rating
• Scoreboard: Full 10-player data

Limitations:

• API returns only last 5 matches, cannot get more history
• Season overview requires login Cookie

Analysis Guidelines

When reviewing match reports, analyze from these dimensions:

1. Core Data Rating: Rating >1.3 excellent, 1.0-1.3 normal, <0.85 poor; ADR >90 strong, 60-90 average, <60 weak
2. Style Judgment: AWP kill ratio, headshot rate, first kill/death ratio, T/CT side differences
3. Stability: Standard deviation of Rating across multiple matches, gap between highest and lowest
4. Team Contribution: KAST (round participation), utility usage, clutch ability
5. If multiple players same match: Horizontal comparison, identify who carried and who underperformed

Language Style: Direct, sharp, with a touch of dark humor. No formalities. Praise when good, roast when bad.

Dependencies

• Python 3.10+
• aiohttp (pip install aiohttp)

Resources

scripts/

• cs_monitor.py — Main monitoring script, supports --once single query and continuous monitoring mode