Report

What This Skill Does

The Report skill is a highly flexible automation tool for OpenClaw that allows users to configure recurring data reports based on custom sources. Instead of relying on rigid, pre-built dashboards, this skill empowers you to define exactly what metrics matter to you and how they should be delivered. By utilizing a configuration-first approach, the skill stores settings in ~/report/, ensuring your reporting preferences remain persistent across sessions. The skill handles the heavy lifting of scheduling via standard cron syntax and formatting data into readable outputs like chat messages, files, or external notifications.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/ivangdavila/report After installation, the skill automatically initializes the workspace by creating the ~/report/ directory structure, preparing the environment for your first configuration file.

Use Cases

• Revenue Monitoring: Automate weekly summaries of Stripe transactions to keep track of financial growth.
• Engineering Metrics: Generate end-of-week reports on GitHub issue resolution or repository commit activity.
• Personal Productivity: Aggregate data from various local logs or APIs to create a daily summary of task completion or habit tracking.
• System Maintenance: Receive scheduled alerts on disk usage or process health stored in log files, delivered directly to Telegram.

Example Prompts

1. "Create a weekly report named 'revenue-tracker' that pulls from my Stripe API and sends the summary to my Telegram channel."
2. "List all my currently configured reports and tell me when the next one is scheduled to run."
3. "Pause the 'github-activity' report for now; I don't need the updates while I am on vacation."

Tips & Limitations

• Security First: Never store raw API keys or tokens in your configuration files. Always reference them via environment variables (e.g., STRIPE_API_KEY) to keep sensitive data out of your logs.
• Scheduling: Use standard cron syntax. If you are unsure, the skill supports common aliases like 'daily' or 'weekly' equivalents.
• Privacy: Note that this skill does not autonomously pull data. You must explicitly grant access to any source, and for external delivery channels like Telegram or email, ensure you trust the endpoint as sensitive data will be transmitted off-device.
• File Management: All generated reports are saved locally in ~/report/{name}/generated/, providing an audit trail for all past outputs.