weekly-catchup
Skill16 starsChanged 6 months agoUnlicenseView on GitHub
Use at the start of a weekly session. Syncs all sources and generates a catch-up summary.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- anti-slop-guideSkill
- info-defragSkill
- prepare-meetingSkill
- run-experimentSkill
- sutro-contextSkill
- sutro-syncSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Check GitHub. Run gh issue list --repo cybertronai/SutroYaro --state open and gh pr list.
- Very specific: line 16
Read the last catch-up in docs/catchups/ for context on what happened last week.
- Very specific: line 25
Update docs/catchups/index.md with the new entry.
- Very specific: line 27
Update mkdocs.yml nav if needed.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Weekly Catch-Up
Steps
- Sync Google Docs. Run
python3 src/sync_google_docs.py. Check for new meeting docs. - Sync Telegram. Run
bun run sync_telegram.ts. Check chat-yad, chat-yaroslav, challenge channels. - Check GitHub. Run
gh issue list --repo cybertronai/SutroYaro --state openandgh pr list. - Read the last catch-up in
docs/catchups/for context on what happened last week. - Generate the catch-up page. Create
docs/catchups/YYYY-MM-DD.mdwith:- Sync status (docs synced, messages count, issues/PRs)
- New ideas from Telegram (summarize, don't quote private messages)
- GitHub issues update (new, closed, in progress)
- What's due (upcoming meetings, deadlines)
- Action items for the week
- Update
docs/catchups/index.mdwith the new entry. - Update
mkdocs.ymlnav if needed.
Checklist
- Google Docs synced
- Telegram synced
- GitHub checked
- Catch-up page created
- Index updated
- Nav updated
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

