Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Configure custom recurring reports. User defines data sources, skill handles scheduling and formatting.
Configure custom recurring reports. User defines data sources, skill handles scheduling and formatting.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
~/report/ ├── memory.md # Index + preferences ├── {name}/ │ ├── config.md # Report configuration │ ├── data.jsonl # Historical data │ └── generated/ # Past reports Create on first use: mkdir -p ~/report
This skill: ✅ Stores report configurations in ~/report/ ✅ Generates reports on schedule ✅ Delivers via channels user configures User-driven model: User defines WHAT data to include User grants access to any needed sources User provides API keys if external data needed Skill handles SCHEDULING and FORMATTING This skill does NOT: ❌ Access APIs without user-provided credentials ❌ Pull data from sources user hasn't specified ❌ Store credentials (user provides via environment)
No fixed requirements. User provides API keys as needed: # Example: if user wants Stripe data export STRIPE_API_KEY="sk_..." # Example: if user wants GitHub data export GITHUB_TOKEN="ghp_..." Config references env var name, never the value.
External delivery (Telegram/webhook/email) sends report content off-device. User explicitly configures each channel User responsible for trusting destination file delivery stays local (~/report/{name}/generated/)
TaskFileConfiguration schemaschema.mdOutput formatsformats.mdDelivery optionsdelivery.md
When creating a report: User specifies what data to track If external API needed, user provides credentials Credentials stored as env var references, not values Example: User: "Weekly report on my Stripe revenue" Agent: "I'll need Stripe API access. Please set STRIPE_API_KEY in your environment." User: "Done" → Config stored with "source": {"type": "api", "env": "STRIPE_API_KEY"}
In ~/report/{name}/config.md: name: weekly-revenue schedule: "0 9 * * 1" # Monday 9am sources: - type: api env: STRIPE_API_KEY # User provides format: chat delivery: telegram
FrequencyCronExampleDaily0 9 * * *9am dailyWeekly0 9 * * 1Monday 9amMonthly0 9 1 * *1st of monthOn-demand-When user asks
User configures in config.md: chat — Reply in conversation telegram — Send to Telegram (user provides chat ID) file — Save to ~/report/{name}/generated/ email — Send via user's configured mail
"List my reports" → Read ~/report/memory.md "Pause X report" → Update config "Run X now" → Generate on-demand
Data access, storage, extraction, analysis, reporting, and insight generation.
Largest current source with strong distribution and engagement signals.