Reporting
Verified@staybased
npx machina-cli add skill @staybased/reporting --openclawReporting — Standardized Report Templates
All reports output to workspace/artifacts/ with naming convention:
{type}-{YYYY-MM-DD}.md
Report Types
1. Weekly Retrospective
File: artifacts/weekly-retro-YYYY-MM-DD.md
Cadence: Sunday evening
Template: templates/weekly-retro.md
Covers: revenue, agent economy, what shipped, what stalled, service uptime, next week priorities.
2. Full System Audit
File: artifacts/full-audit-YYYY-MM-DD.md
Cadence: Monthly or on-demand
Template: templates/full-audit.md
Covers: executive summary, revenue pipeline, workflow gaps, agent utilization, infrastructure efficiency, tool inventory, cron effectiveness, strategy assessment, content status, recommendations.
3. Daily Progress Log
File: artifacts/daily-log-YYYY-MM-DD.md
Cadence: End of day
Template: templates/daily-log.md
Covers: tasks completed, decisions made, blockers, tomorrow's priorities.
4. Revenue Snapshot
File: artifacts/revenue-YYYY-MM-DD.md
Cadence: Weekly or on-demand
Template: templates/revenue-snapshot.md
Covers: income by stream, expenses, net P&L, progress toward goals, trading performance.
Templates
See templates/ directory for each template file. All use {{PLACEHOLDER}} syntax for variable substitution.
Output Standards
- All reports go to
workspace/artifacts/ - Use ISO dates in filenames
- Include generation timestamp and author at bottom
- Include "Executive Summary" at top for reports >1 page
- Link to source data where possible
Overview
Reporting provides a set of standardized templates and a clear file-naming convention for periodic reports, system audits, revenue tracking, and progress logs. All outputs are written to workspace/artifacts/ and include a generation timestamp and author to ensure consistency and traceability across the workspace.
How This Skill Works
Reports are generated by selecting a type and filling placeholders in templates located under templates/. The result is saved to workspace/artifacts/ with the naming convention {type}-{YYYY-MM-DD}.md. Each file includes an Executive Summary for multi-page reports and a bottom section noting the generation timestamp and author. Source data should be linked where possible, with zeros (e.g., $0 revenue) treated as valid data rather than omitted.
When to Use It
- Generating periodic reports
- Conducting system audits
- Tracking revenue and expenses
- Weekly retrospectives
- Daily progress logs
Quick Start
- Step 1: Pick the report type and open the matching template in templates/ (e.g., templates/weekly-retro.md).
- Step 2: Fill {{PLACEHOLDER}} values with data from source systems and compute metrics.
- Step 3: Save to workspace/artifacts/ using the {type}-{YYYY-MM-DD}.md naming convention and include generation timestamp and author.
Best Practices
- Always select the correct template for the report type (weekly-retro, full-audit, revenue-snapshot, daily-log).
- Name files using ISO dates and store them under workspace/artifacts/ (e.g., artifacts/daily-log-YYYY-MM-DD.md).
- Include an Executive Summary for reports longer than one page.
- Link to source data where possible and validate metrics before finalizing.
- For edge cases, mark non-applicable sections as N/A and note any partial data (e.g., partial week).
Example Use Cases
- artifacts/weekly-retro-YYYY-MM-DD.md (Weekly Retrospective)
- artifacts/full-audit-YYYY-MM-DD.md (Full System Audit)
- artifacts/daily-log-YYYY-MM-DD.md (Daily Progress Log)
- artifacts/revenue-YYYY-MM-DD.md (Revenue Snapshot)
- artifacts/weekly-retro-YYYY-MM-DD.md (Weekly Retrospective)
