ClawHub

Reporting

v1.0.0

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.

⭐ 0· 1.2k·10 current·10 all-time
by@staybased
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name and description match the shipped artifacts and templates. The skill is purely about generating structured reports; it does not request unrelated binaries, environment variables, or network access.
✓
Instruction Scope
SKILL.md and templates are limited to producing Markdown files in workspace/artifacts/ using placeholders. The instructions do ask to "link to source data where possible," which could lead an agent to fetch internal data when filling placeholders, but that is coherent with report generation rather than out-of-scope activity.
✓
Install Mechanism
No install spec and no code files beyond templates; nothing is downloaded or written to disk by an installer. This is the lowest-risk pattern.
✓
Credentials
The skill requests no environment variables, credentials, or config paths. Template placeholders reference revenue and metrics, which are appropriate for a reporting skill and do not in themselves justify access to secrets.
✓
Persistence & Privilege
always is false and the skill does not request persistent system presence or modify other skills. Model invocation is allowed (default), which is expected for usable skills.
Assessment
This skill appears coherent and low-risk, but review before enabling: (1) Confirm workspace/artifacts/ is an appropriate, access-controlled location because reports contain sensitive revenue and performance data. (2) Decide what sources the agent may use to fill placeholders — avoid granting it broad access to databases, cloud credentials, or third‑party APIs unless necessary. (3) If you don't want autonomous runs, keep the skill user-invocable only and monitor generated artifacts. (4) Consider sanitizing any fields (trading P&L, credentials, internal logs) before sharing artifacts externally.

Like a lobster shell, security has layers — review code before you run it.

latestvk97b9e13jhp963rwenev86yb99810jrq

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments