What problem does it solve?
This Skill turns live operating data into decision-ready reports that clearly state what changed, why it matters, and what action (including owners and escalations) is required—without producing reporting theater or guessing missing facts.
Core Features & Use Cases
- Stateful reporting loop: Builds reports from a recurring baseline by loading prior snapshots, fetching current data, isolating meaningful deltas, and saving only the state needed for the next run.
- Lane-based reporting: Supports distinct workflows for general operating updates, expense reporting, savings goal check-ins, audience growth, engagement analysis, product analytics, social proof/mentions, and engineering delivery reporting.
- External data grounding: Enforces an external access requirement (CLI first, MCP second, API fallback) and requires the report to declare degradation when data cannot be fetched.
- Decision output contract: Produces actions and escalations with explicit statuses (watch, action required with owner, escalate now) and ensures metrics have thresholds/targets and comparison points.
Quick Start
Use the reporting skill to answer this operating question for a specific window: "What materially changed this week, why does it matter, and what decisions or escalations are needed now?"
