weekly-update
Skill3 starsChanged 3 months agoMITView on GitHub
Produce a compact company weekly update from current context, tasks, decisions, waiting-for items, and meeting notes. Use once a week. Triggers on "weekly update", "update the projects", and "run the weekly updates".
7 other projects use a version of this.
Adopted by
Most recently taken up by
- priyesh0453/weekly-updatetheir own version, first seen Oct 20, 2026
- alabenkhlifa/dayjobtheir own version, first seen Oct 20, 2026
- omeirhaeghe/staffgenttheir own version, first seen Oct 11, 2026
- madeordinary/serel-memorytheir own version, first seen Oct 9, 2026
- bogdanbaciu21/skillstheir own version, first seen Jul 28, 2026
- jpoindexter/theft-kittheir own version, first seen May 20, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- KarlRaf/gtm-starter-kit★ 213same name
- bogdanbaciu21/skills★ 2same name
- alabenkhlifa/dayjob★ 1same name
- jpoindexter/theft-kit★ 1same name
- madeordinary/serel-memory★ 1same name
- omeirhaeghe/staffgent★ 1same name
- priyesh0453/weekly-update★ 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 repository6 other files it gives its agents.
- company/AGENTS.mdAGENTS.md
- company/CLAUDE.mdCLAUDE.md
- debriefSkill
- meeting-notesSkill
- morning-sweepSkill
- reflectSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Company mode: use this when operating-system/ exists with operating-system/GLOBAL_TASKS.md.
- Very specific: line 17
Personal mode: use this when root-level TASKS.md and personal context files exist without the company operating system.
- Distinctive: line 18
Both detected: ask which mode to use. Write nothing until the user chooses.
- Distinctive: line 21
Do not create a structure just to make the skill run.
- Distinctive: line 29
Read the top-level company signals:
- Distinctive: line 39
If a source is missing, say so.
- Distinctive: line 51
Keep it to one screen. Separate facts from inference.
- Distinctive: line 57
After writing, return a short company-level read on the pattern across the work.
“Common” is measured: kept by at least 6 in 10 of the 6 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
Weekly Update
Turn the week's scattered signals into one compact view of progress, open loops, risk, and the next move.
Done when: the approved dated section is added to operating-system/WEEKLY_UPDATE.md above the previous entries, or the user has a conversational summary in personal mode.
Detect the structure first
Inspect the current folder before planning any write.
- Company mode: use this when
operating-system/exists withoperating-system/GLOBAL_TASKS.md. - Personal mode: use this when root-level
TASKS.mdand personal context files exist without the company operating system. - Both detected: ask which mode to use. Write nothing until the user chooses.
- Neither detected: say that this folder does not contain a recognised personal or company structure. Point the user to START-HERE. Write nothing.
Do not create a structure just to make the skill run.
Personal mode
The personal structure does not maintain a weekly-update file. Explain that this workflow belongs to the company level, point the user to the company setup, and write nothing. Offer a conversational summary only if the user wants one.
Company mode
Read the top-level company signals:
operating-system/current-context.mdoperating-system/GLOBAL_TASKS.mdoperating-system/DECISIONS.mdoperating-system/WAITING_FOR.md- this week's files in
operating-system/meetings/ - the previous entry in
operating-system/WEEKLY_UPDATE.md - any email or message exports the user explicitly provides
If a source is missing, say so. Do not infer activity from silence.
Draft one dated section with:
- Status: Green, Amber, or Red, with one line explaining why
- Since last week: progress, not activity
- Open loops
- Risks
- Decisions needed and their owners
- Follow-ups
- Suggested next action: the single most important move
Keep it to one screen. Separate facts from inference. Where a source was quiet, say "no meaningful signal this week." Draft only, never send.
Approval gate
Show the complete proposed section and name operating-system/WEEKLY_UPDATE.md as the only target. Wait for approval. On approval, add the new dated section above the previous entries. If the file is missing and operating-system/templates/WEEKLY_UPDATE.md exists, propose creating it from that template first. Never replace or discard previous weeks.
After writing, return a short company-level read on the pattern across the work.
Scaling to per-project folders
Company mode deliberately writes one top-level operating-system/WEEKLY_UPDATE.md. If the organisation later needs separate project updates, create a WEEKLY_UPDATE.md inside each project and change this routing rule. Keep a short cross-project summary at the top level.
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.