daily-update
Skill4 starsChanged 10 months agoApache-2.0View on GitHub
Generate a formatted async daily standup message for the Sentry SDK team channel. Use when asked to create a "daily update", "async daily", "standup update", or "async team update".
7 other projects use a version of this.
Adopted by
Most recently taken up by
- kdy1/kdy1-scriptstheir own version, first seen Nov 8, 2026
- Ar9av/obsidian-wikitheir own version, first seen Nov 8, 2026
- chobizzy/llm-wikitheir own version, first seen Nov 1, 2026
- MrEddieO/claude-skillstheir own version, first seen Oct 20, 2026
- pandoempe/mpw_claudetheir own version, first seen Oct 11, 2026
- BenjaminG/ai-skillstheir own version, first seen Jun 2, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- Ar9av/obsidian-wiki★ 3.7ksame name
- kdy1/kdy1-scripts★ 33same name
- tarasinghrajput/Anukar-skills★ 7same name
- BenjaminG/ai-skills★ 4same name
- chobizzy/llm-wiki★ 3same name
- MrEddieO/claude-skills★ 0same name
- pandoempe/mpw_claude★ 0same name
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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- contributing-mdSkill
- linear-initiativeSkill
- linear-sdk-telemetry-labelerSkill
- linear-type-labelerSkill
- sdk-feature-implementationSkill
- span-convention-reviewSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Ask the user for the following.
- Distinctive: line 38
Always start with the 🔄 emoji — this makes the update searchable in Slack
- Very specific: line 39
Use today's date in YYYY-MM-DD format
- Distinctive: line 40
Leave a blank line between the date and the first bullet
- Very specific: line 42
If the user provides a Linear issue link, inline it after the task description: Task description SDK-123
- Distinctive: line 43
Only include Blocker, Needs, and OOO lines if the user has something to report — omit them entirely otherwise
- Very specific: line 51
After the code block, remind the user: post this in your #team-sdk-* channel.
“Common” is measured: kept by at least 6 in 10 of the 7 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
Async Daily Update
Generate a properly formatted async daily standup message for posting in the team Slack channel.
Step 1: Gather Information
Ask the user for the following. Collect all answers before generating the message.
Required:
- What are you working on today? (list each task; ask if any have Linear issue links to include)
Optional — ask about each, only include in output if the user has something to report:
- Any blockers? (something preventing you from making progress)
- Anything you need from a specific teammate? (who and what)
- Any time OOO today? (if yes, ask for the time range and time zone)
Step 2: Generate the Message
Format the message exactly as follows:
🔄 YYYY-MM-DD
- [task one]
- [task two — add link if provided]
- **Blocker:** [description]
- **Needs:** [what you need — @mention the person directly]
- **OOO:** [time range with time zone, e.g., 14:00–17:00 CET]Rules
- Always start with the 🔄 emoji — this makes the update searchable in Slack
- Use today's date in
YYYY-MM-DDformat - Leave a blank line between the date and the first bullet
- Each task is a separate bullet point
- If the user provides a Linear issue link, inline it after the task description:
Task description [SDK-123](https://linear.app/...) - Only include Blocker, Needs, and OOO lines if the user has something to report — omit them entirely otherwise
- For Needs, mention the specific person by name or @handle
- For OOO, always include the time zone (e.g., CET, EST, PST)
Step 3: Output
Display the final message as a plain code block so the user can copy and paste it directly into Slack.
After the code block, remind the user: post this in your #team-sdk-* channel.
Examples
Minimal (no optional fields):
🔄 2024-02-16
- Finishing OTLP exporter implementation [SDK-234](https://linear.app/team/issue/SDK-234)
- Code review for Marco's span processor refactor [SDK-245](https://linear.app/team/issue/SDK-245)With optional fields:
🔄 2024-02-16
- Wrapping up bugfixes in profiling integration and preparing release notes
- Shifting focus to client reports implementation after bugfixes merge
- **Blocker:** Need test credentials for staging environment to verify the span ingestion fix
- **Needs:** API design review on error handling from @Sarah
- **OOO:** 14:00–17:00 CETDoes 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.