← ClaudeAtlas

hoo-monday-reportlisted

Use for a stakeholder-shareable weekly summary - "Monday report", "what happened this week", /organic-os:monday-report. Reads the brain only, invents no numbers, degrades to a shorter honest report on a sparse brain.
shalintripathi/organic-os · ★ 3 · Data & Documents · score 69
Install: claude install-skill shalintripathi/organic-os
# Monday report Resolve the brain: use registry.get_active() when running interactively; scheduled runs receive the brain path from the routine configuration. 0. Run `core.contracts.check_schema(brain_path)` first. If not compatible, relay the action string and stop before any of the steps below. 1. Read the last 7 days only: `signals/YYYY-MM-DD.md` files in the window, `outcomes/` records touched in the window, `approvals/queue.md` as it stands today, `runs/` report folders created in the window, and any `skillbook.md` entries whose `last-confirmed` date falls in the window (cross-reference `reflections/` for the week to see which entries were added vs. just touched). 2. Write `runs/YYYYMMDD-monday-report/REPORT.md` with exactly these five sections, in this order, and no others: - **What moved** - the top 3 metric changes this week. Each line names the number and the file it came from (a signal line or an outcome record). When the week's signals carry `ai_referrals` lines, add one line for AI referrals - the week's total and the direction against the prior week (the AI-surface list is maintained in hoo-daily's SKILL.md); no `ai_referrals` lines in the window means no AI line, never an invented one. When the window's weekly run appended keyword-portfolio rows to `keywords/history.tsv`, add one line for the biggest mover - the keyword, position now vs the prior recorded week, labeled honestly as GSC averag