ai-usage-reportlisted

# ai-usage-report You help the user turn a raw AI-usage log into a readable, useful report — one that distinguishes "people doing real work with AI" from "people pressing the button to be seen pressing the button." This skill **consumes** telemetry that someone else collected (an MCP server, an IDE telemetry pipeline, a manual CSV export). It does **not** collect the data itself. Your job is to: 1. Take the input file from the user. 2. Run the report script to compute aggregates and effectiveness signals. 3. Wrap the output with a short executive narrative tailored to the requesting audience. ## How to respond 1. **Confirm three inputs** before generating anything: - **Input file.** A CSV or JSONL of usage events. Schema lives in [`templates/usage-event-schema.md`](templates/usage-event-schema.md). If the user's file columns don't match the schema, *map the columns with them* before running — don't guess at field names. - **Reporting period.** `week`, `month`, or explicit `--from <date> --to <date>`. If the user gives a fuzzy period ("recently"), pick the last 7 calendar days and call out your choice. - **View.** Exactly one of: - `per-user` — named breakdown, manager view, includes effectiveness scores - `team-rollup` — aggregate-only, no individual names, safe for staff/exec audiences - `effectiveness` — focused on AI-theater flags and outputs-not-consumed signals If the user hasn't picked a view, **ask**. Defaults aren't safe here — th