Generate a daily system activity summary across all joelclaw subsystems. Triggers on 'daily summary', 'what happened today', 'system report', 'today's tally', 'activity summary', 'what did we do', 'daily report'.
71
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Generate a comprehensive daily activity report across all joelclaw subsystems.
Collect from ALL of these:
# joelclaw repo
cd ~/Code/joelhooks/joelclaw && git log --oneline --since="$(date +%Y-%m-%d)T00:00:00" --no-merges
# Vault
cd ~/Vault && git log --oneline --since="$(date +%Y-%m-%d)T00:00:00" --no-mergesjoelclaw runs --count 200 --hours 24Summarize: total, completed, failed, unique functions. Flag any failures.
kubectl get pods -n joelclaw --no-headersNote any new deployments, restarts, or unhealthy pods.
Count sessions created today. Note which were gateway-dispatched vs standalone.
joelclaw otel stats --hours 24cd ~/Vault/docs/decisions && git log --oneline --since="$(date +%Y-%m-%d)T00:00:00" --no-merges -- .Count: new ADRs, status changes, grooming activity.
Check for discovery/noted events in recent Inngest runs.
joelclaw otel search "memory.observe|observations" --hours 24Query canonical OTel for deploy actions today:
joelclaw otel search "deploy" --hours 24Use OTel for runtime configure/install evidence, then check relevant Brain .svx receipts and source-control history for durable changes:
joelclaw otel search "configure|install" --hours 24Concise, structured. Group by category:
For Telegram: use HTML tags, keep mobile-friendly.
For CLI: return HATEOAS JSON with summary object.
aa0116c
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.