standup
Skill96 starsChanged 12 days agoMITView on GitHub
Use when the user says "/standup", "standup", "stand-up", "daily standup", "what did I do yesterday", "what am I doing today", "what are my blockers", or wants a quick standup summary
56 other projects use a version of this.
Adopted by
Most recently taken up by
- HsuanYuLee/polaristheir own version, first seen Nov 12, 2026
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
- spencerldixon/skillstheir own version, first seen Nov 8, 2026
- pahlevikun/levistacktheir own version, first seen Nov 1, 2026
- AuroraBackcountry/agent-configtheir own version, first seen Nov 1, 2026
Used with
Projects with it also use close-day, meeting-prep and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
vantageos-agencySkillclose-day
End-of-day routine: close tasks with their time, leave the repository and the disk clean, write the diary, harvest friction, and hand over to tomorrow. Use this skill whenever the user says "close day", "end of day", "fin de journée", "bonne nuit", "wrap up", "call it a day", "close session", "daily close", or mentions ending their work session -- even if they don't say "close-day" explicitly.
Also in 3 projects that use this
OpenAISkillmeeting-prep
Use when creating Public Equity Investing meeting prep briefs. Do not use for private diligence, IB, FP&A, legal, or scheduling-only tasks.
Also in 5 projects that use this
jasonmichaelbell78-creatorSkilltodo
Cross-session todo management with interactive menu, JSONL-backed persistence, and AI-powered context capture. Manages ideas, tasks, and insights that emerge during sessions so they survive across sessions. Independent of GSD.
Also in 3 projects that use this
takleb3rrySkillkickoff
Initialize a new project by analyzing source documents and generating requirements.md and design.md
Also in 3 projects that use this
asterkinSkilladr
Create Architecture Decision Records (ADRs) following project standards. Guides template usage, process, and best practices for documenting architecturally significant decisions.
Also in 4 projects that use this
GitHubSkillrefactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
Also in 4 projects that use this
Other versions56 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 56
- anthropics/knowledge-work-plugins★ 36ksame name
- drafthq/draft★ 40same name
- shipshitdev/skills★ 39same name
- rlajous/claude-code-commands★ 30same name
- GTMify/aigtm★ 25same name
- kriscard/Skills★ 15same name
- carlvellotti/codex-for-pms-skills-bonus★ 8same name
- edjchapman/claude-code-config★ 8same name
- jcurbelo/agent-seed★ 8same name
- zauberzeug/game-of-cards★ 7same name
46 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- templates/AGENTS.mdAGENTS.md
- templates/CLAUDE.mdCLAUDE.md
- bootSkill
- brandSkill
- catchupSkill
- contentSkill
- dailySkill
- emailSkill
- moneySkill
- oppsSkill
- outreachSkill
- projectSkill
- resumeSkill
- shipSkill
- summarySkill
- tldrSkill
- video-notesSkill
- weeklySkill
- wiki-healthSkill
- wikiSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 52 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Never invent items. Every bullet must trace directly to text in one of the three files.
- Distinctive: line 30
Do not summarise, paraphrase beyond light clean-up, or merge items from different files.
- Distinctive: line 31
If a file does not exist, say so in one line and move on.
- Very specific: line 32
Keep each bullet to one line.
- Distinctive: line 33
Do not add commentary, greetings, or follow-up questions after the three sections.
“Common” is measured: kept by at least 6 in 10 of the 52 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/standup: the 60-second standup briefing
Read in parallel:
daily/<yesterday>.md: what was done yesterdaydaily/<today>.md: what is planned for today.remember/hot.md: active projects, tracks, hard rules (blockers live here)
Date arithmetic: yesterday = today - 1 calendar day. Use ISO format YYYY-MM-DD for filenames.
Output (exactly this, no intro)
STANDUP: <date>
Yesterday
One bullet per item found in yesterday's daily note. If the file is missing: "No note for <date>."
Today
One bullet per item found in today's daily note. If the file is missing: "No note for <date>."
Blockers
One bullet per blocker found across today's daily note and .remember/hot.md. If none appear: "None."
Rules
- Never invent items. Every bullet must trace directly to text in one of the three files.
- Do not summarise, paraphrase beyond light clean-up, or merge items from different files.
- If a file does not exist, say so in one line and move on. Do not error.
- Keep each bullet to one line; drop markdown formatting noise (extra
#,---dividers). - Do not add commentary, greetings, or follow-up questions after the three sections.
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.

