reporting
Standardized templates for periodic reports, system audits, revenue tracking, and progress logs. All output goes to workspace/artifacts/ directory. Use when: generating periodic reports, system audits, performance reviews, revenue tracking, weekly retrospectives, daily progress logs, full workspace audits. Don't use when: ad-hoc status updates in chat, quick summaries in Discord, one-off answers to "how's it going?", real-time dashboards. Negative examples: - "Give me a quick update" → No. Just answer in chat. - "What's the weather?" → No. This is for structured reports. - "Post a status to Discord" → No. Just send a message. Edge cases: - Mid-week report requested → Use weekly template but note partial week. - Audit requested for single subsystem → Use full audit template, mark other sections N/A. - Revenue snapshot with $0 revenue → Still generate it. Zeros are data.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/staybased/reportingReporting — 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
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-staybased-reporting": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
Proposal Writing
Skill by staybased
ops-hygiene
Standard operating procedures for agent maintenance, security hygiene, and system health. Use when performing periodic checks, security audits, memory maintenance, secret rotation, dependency updates, or any recurring "housekeeping" tasks. Also use when setting up automated maintenance schedules or when asked about agent security posture.
Lead Magnets
Skill by staybased
Pricing Psychology
Skill by staybased
trade-validation
10-dimension weighted scoring framework for prediction market trade evaluation. Enforces disciplined position sizing, circuit breakers, and mandatory counter-arguments. Use when: evaluating prediction market trades, scoring opportunities, deciding position sizes, comparing Polymarket/Kalshi opportunities, running pre-trade checklists. Don't use when: general crypto analysis, DeFi yield farming, non-prediction-market investments, stock/equity analysis, sports betting (different framework needed). Negative examples: - "Should I buy ETH?" → No. This is for prediction markets with binary/discrete outcomes. - "What's the best DeFi yield?" → No. Wrong domain entirely. - "Score this sports bet" → No. Sports betting has different dimensions (injuries, matchups). Edge cases: - Crypto prediction markets (e.g., "Will BTC hit $X?") → YES, use this if on Polymarket/Kalshi. - Multi-outcome markets → Score each outcome separately. - Markets with <$25 liquidity → Auto-fail on Liquidity dimension.