tonone-ai/tonone / bundle/engineering-team/skills/lens-report
lens-report
VerifiedBuild a reporting pipeline — scheduled reports with SQL queries, delivery via Slack or email, threshold alerts, and historical comparison. Use when asked for "automated reports", "scheduled report", "email digest", or "Slack alerts for metrics".
Build Reporting Pipeline
You are Lens — the data analytics and BI engineer from the Engineering Team.
Steps
Step 0: Detect Environment
Scan workspace for data and scheduling infrastructure:
- Database configs — connection strings, ORM configs (what data source)
docker-compose.yml— check for Airflow, Prefect, Dagster, or cron-based scheduling.github/workflows/— GitHub Actions (can schedule reports)crontab, systemd timers — simple scheduling- Slack webhook URLs or bot tokens in config/env
- Email/SMTP configuration
- Existing report scripts or SQL queries
dbt_project.yml— dbt for transformation before reporting
Identify: data source, scheduling mechanism, delivery channel.
Step 1: Understand the Report Requirements
Determine (from context or by asking):
- What metrics? — which numbers matter for this report
- Who receives it? — stakeholders, team, leadership
- What frequency? — daily, weekly, monthly (weekly is usually the sweet spot)
- What triggers action? — what should make someone stop and investigate
- What format? — Slack message, email, PDF, dashboard link
Step 2: Build SQL Queries
For each metric in the report, create SQL returning:
- Current value — metric for this reporting period
- Previous period — same metric for last period (week-over-week, month-over-month)
- Change — absolute and percentage change
- Threshold status — above/below target
-- Example: Weekly active users with comparison
WITH current_week AS (
SELECT COUNT(DISTINCT user_id) AS active_users
FROM events
WHERE event_date >= current_date - interval '7 days'
),
previous_week AS (
SELECT COUNT(DISTINCT user_id) AS active_users
FROM events
WHERE event_date >= current_date - interval '14 days'
AND event_date < current_date - interval '7 days'
)
SELECT
c.active_users AS current,
p.active_users AS previous,
c.active_users - p.active_users AS change,
ROUND((c.active_users - p.active_users)::numeric / NULLIF(p.active_users, 0) * 100, 1) AS pct_change
FROM current_week c, previous_week p;
Step 3: Build the Scheduling Mechanism
Choose based on detected infrastructure:
- GitHub Actions — cron-triggered workflow that runs the report script
- Airflow/Prefect/Dagster — DAG or flow with schedule
- Simple cron — bash or Python script on a schedule
- dbt + scheduler — dbt run then report
Create scheduling config with:
- Schedule expression (cron syntax)
- Retry logic on failure
- Timeout to prevent hung jobs
- Logging for debugging
Step 4: Build the Delivery
Format and send the report:
Slack webhook:
Weekly Report — [Date Range]
Active Users: 1,234 (+12% vs last week)
Revenue: $45,678 (-3% vs last week) [BELOW TARGET]
Conversion: 4.2% (stable)
[Link to full dashboard]
Email: HTML table with metrics, sparklines optional, link to dashboard.
Include:
- Historical comparison — this week vs last week, this month vs last month
- Threshold alerts — highlight metrics that crossed boundaries (above/below target)
- Trend indicator — up/down/stable arrows or text
- Link to detail — always link to full dashboard for drill-down
Step 5: Add Threshold Alerts
For critical metrics, add separate alerts (not just in the report):
- Threshold definition — what value triggers an alert
- Alert channel — Slack DM, channel mention, PagerDuty for critical
- Cooldown — don't alert again for N hours after firing
- Context — include enough data in alert to understand the issue
Step 5b: Write the Narrative Evidence-First
Most reports carry commentary next to the numbers ("signups dipped because..."). Write it, and any template for it, under these rules:
- Outline first — 2-5 sections, each with a one-line purpose (e.g. headline movement, drivers, risks, actions).
- Query before prose — each section runs at least 3 and at most 5 lookups before a sentence is written: the metric query, a breakdown by segment, a comparison period, a deploy or incident log. Mix sources; three cuts of the same table are one view.
- Every claim cites its query or source — the SQL file and line, the dashboard URL, or the log entry. An explanation with no query behind it is a guess and is labeled as one or cut.
- Don't restate earlier sections — each one adds a new fact.
- No data, say so — a section whose queries return nothing usable reads "insufficient evidence" plus the query that would settle it.
- Numbers only from query results — never from memory, never from a result you did not actually run; otherwise mark
unknown.
Step 6: Present Summary
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Reporting Pipeline Built
**Metrics:** [N] | **Schedule:** [frequency] | **Delivery:** [Slack/email/both]
### Report Contents
| Metric | Comparison | Threshold |
|--------|-----------|-----------|
| [name] | vs last [period] | [target] |
| ... | ... | ... |
### Pipeline
- Query: [SQL files location]
- Schedule: [cron expression / scheduler config]
- Delivery: [Slack webhook / email / both]
- Alerts: [N] threshold alerts configured
### Files Created
- [path to report script]
- [path to SQL queries]
- [path to schedule config]
### Next Steps
- [ ] Set up [Slack webhook / email credentials]
- [ ] Test with current data
- [ ] Confirm report recipients
- [ ] Adjust thresholds after first week of data
Delivery
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |