standup is agent-read markdown (skill) from thoughtbot/rails-consultant: Write a client update — identify what was done, what's next, and surface risks before they become surprises. End of day, start of day, or end of week..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
## Behavior
This is a guided conversation that ends with a polished, ready-to-send update. Start by getting the raw material from the user — then help them sharpen it.
### Step 1: Gather
Start by checking git for context:
- `git log --since="yesterday" --author=$(git config user.email)` (or last few days if no recent commits)
- Check for open branches, uncommitted work, open PRs
Then open with:
**"Here's what I can see from git. Before I help you write this — what did you actually spend your time on? Git doesn't always tell the full story."**
Wait for their answer. Git shows commits but misses investigation, debugging, conversations, decisions, and thinking. Their answer fills the gaps.
Then ask:
**"What's the most important thing the client should know from today — if they read one sentence and nothing else?"**
Wait. This forces them to prioritise. Most updates bury the lead.
Then:
**"Is there anything the client needs to decide, unblock, or be aware of before your next working session?"**
Wait. This surfaces blockers and risks before they become surprises.
### Step 2: Sharpen — Socratically
Before writing the update, push on what they've said:
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_qm2elditgvkuzg6j
GET https://markdownregistry.com/api/v1/resolve?ref=thoughtbot/rails-consultant/standup
GET https://markdownregistry.com/api/v1/blob/9c289e430c041979e7af3722a94f5300b7d81dbb929cf776a6acaabf0c90cbdf
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
thoughtbot/rails-consultant · skills/challenge/SKILL.md · Pressure-test an assumption, decision, or inherited constraint — Socratic cross-examination that forces you to defend…
thoughtbot/rails-consultant · skills/explain/SKILL.md · Explain what a piece of code does — a specific file, class, or method in close detail, or a user-facing flow as a…
thoughtbot/rails-consultant · skills/feature-dev/SKILL.md · Take one new feature slice from idea to reviewed, committed code in a single guided pass — scope it into the smallest…
thoughtbot/rails-consultant · skills/git-commit/SKILL.md · Turn the working changes into one or more atomic commits with well-written messages. Use whenever the user runs…
thoughtbot/rails-consultant · skills/hard-news/SKILL.md · Prepare to deliver difficult technical news to a client — a conversational prep session before the hard conversation…
thoughtbot/rails-consultant · skills/offboard/SKILL.md · Walk through the Designer/Developer wrap-up checklist for offboarding a client engagement — conversationally, one item…
thoughtbot/rails-consultant · skills/prior-art/SKILL.md · Discover how a codebase already handles a specific concern — search broadly, find every instance, and assess…
thoughtbot/rails-consultant · skills/rubber-duck/SKILL.md · Think out loud about a problem, decision, or approach — Socratic friction to help you find clarity, not sympathy
thoughtbot/rails-consultant · skills/slice/SKILL.md · Turn a feature into well-defined, independently shippable slices — whether it's an epic that needs breaking apart or a…
thoughtbot/rails-consultant · skills/socratic-review/SKILL.md · Socratic code review and refactoring session — whether it's your own code, a teammate's PR, or something you inherited…
thedotmack/claude-mem · plugin/skills/standup/SKILL.md · Facilitate a read-only standup across git worktrees, branches, or PRs to compare changes and produce one consolidation…
karanb192/claude-code-hooks · plugins/standup-autopilot/skills/standup/SKILL.md · Render today's standup card from what your agents actually did across repos
protolabsai/protoagent · plugins/craft/skills/standup/SKILL.md · /standup — an operational status report on everything this agent currently owns: tasks, goals, schedules, background…
andyed/session-cartographer · plugins/session-cartographer/skills/standup/SKILL.md · Brief on concurrent sessions — who else is working, in which repos, on which files, and what landed underneath you. Use…
hsuanyulee/polaris · .claude/skills/standup/SKILL.md · "Use when the user wants to generate a daily standup report or end-of-day summary (YDY / TDT / BOS / 口頭同步). Single…
