← ClaudeAtlas

create-progress-reportlisted

Build a designed, self-contained HTML progress report for the child — how she's actually doing, and what to work on next — surfaced in the Progress tab for both parent and child.
manishiitg/coding-agent-loop · ★ 13 · AI & Automation · score 63
Install: claude install-skill manishiitg/coding-agent-loop
# Create a progress report One self-contained HTML file that both parent and child can read: an honest picture of **how she's doing** and a clear answer to **what to work on next**. A snapshot, not a narrative essay — lead with the concrete and recent, then stop. If in doubt, cut a section rather than pad it. 1. **Gather real evidence — the substance, not just filenames.** - Every activity's own `conversation.json` (e.g. `find . -maxdepth 4 -name conversation.json`, skipping `materials/`, `reports/`, `memory/`, `conversations/`). Read what actually happened: which problems came up, whether she got them on her own or needed hints, how many attempts, what tripped her up, any celebrate moments and why. This is the real signal — a list of activity titles and dates is not enough. For "Right now"/"How she's doing"/"What to work on next" you only need what's recent — don't bother with anything under `archive/` (activities Pulse has retired for being untouched a while) for these sections. - Each activity's `attempts/*.json` — what she's actually completed, and what the attempt shows. - The `<Subject>/<Topic>/` activity folders and `materials/` — what exists, so you can name what's covered versus not started. - For the **Overall** section you need the FULL history, not just the recent few: skim across the whole workspace INCLUDING `archive/` — lifetime totals (topics attempted, tests completed, star total) must