analyticsshowlisted

# /analytics show Renders the local event log as a report. Never reads remote data, never POSTs. Defaults to a 30-day window and markdown output. ## Prerequisites - Python 3.10+ on the host. - `~/.event4u/agent-config/workspace/analytics/events.jsonl` exists or is empty (empty is a normal result, not an error). ## Steps ### 1. Parse the argument ``` /analytics show [--window 24h|7d|30d] [--event <name>] [--role <slug>] [--format markdown|csv|json] ``` - `--window` defaults to `30d`. - `--format` defaults to `markdown`. - `--event` and `--role` are optional filters. ### 2. Run the implementation ```bash python3 packages/core/installer/python/workspace_analytics.py \ show [--window=...] [--event=...] [--role=...] [--format=...] ``` ### 3. Surface the result **Markdown** view (default): ``` # Workspace analytics — last 30d ## Top prompts - `tradesperson` · `estimate` — 12 - `content-creator` · `script-video` — 7 ## Launcher → completion rate per role - `tradesperson` — 83% (12 launched · 10 completed) **Average session length:** 3m 41s **Knowledge sources clicked:** 14 ``` **CSV** view — one row per event: `ts,event,role,task,host_tier,duration_ms`. Pipe into `awk`/`csvkit` for ad-hoc queries. **JSON** view — full event array; useful for `jq` filters or chart pipelines. ### 4. Empty log Print the markdown shell with `_No events recorded in this window._` and offer the next step: ``` > 1. open the workspace tab to start recording events