Menu
Use before a Sutro Group meeting to compile results and prepare a presentation report.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use periodically (weekly or before a release) to find stale numbers, outdated descriptions, broken links, and inconsistencies across the codebase. Run after merging multiple PRs or before preparing a meeting report.
Use when running a new experiment. Follows the two-phase protocol from LAB.md.
Use before any research task, experiment, or PR review. Loads current project state from DISCOVERIES.md, open questions, and recent Telegram discussion.
Use at the start of any session and before pushing. Syncs Telegram, Google Docs, and GitHub state for the Sutro Group research workspace.
Use at the start of a weekly session. Syncs all sources and generates a catch-up summary.
Use when drafting, editing, or reviewing any prose to detect and remove AI writing patterns including overused vocabulary (delve, tapestry, landscape), formulaic structures (binary contrasts, rule of three), throat-clearing openers, business jargon, and other LLM tells
| name | prepare-meeting |
| description | Use before a Sutro Group meeting to compile results and prepare a presentation report. |
Read the latest catch-up in docs/catchups/ for what happened this week.
Check which experiments were run since the last meeting. Look at research/log.jsonl and docs/findings/ for new entries.
Compile results into a report. Create docs/catchups/meeting-{N}-report.md with:
Check for plots in results/plots/. Reference them in the report if relevant.
List open GitHub issues that are relevant to discuss.
Add the report to mkdocs.yml nav under Weekly Catch-Up.
Run the anti-slop skill on the report before finalizing.
