weekly-review-planning
Skill9 starsChanged 39 days agoMITView on GitHub
Plan a realistic week from calendar, inbox, projects and waiting items; keep sources, owners and capacity visible.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- ashleysbrain/skillstheir own version, first seen Nov 8, 2026
- rakaarwaky/agents-arwakytheir own version, first seen Oct 15, 2026
- nobodyohm-web/Thottheir own version, first seen Oct 13, 2026
- barzzly/BarzzLyp_Agent_Skillstheir own version, first seen Oct 8, 2026
- NousResearch/hermes-agenttheir own version, first seen Oct 2, 2026
- wlkerwong-boop/family-ai-skillstheir own version, first seen Sep 16, 2026
Used with
Projects with it also use github.
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.
NVIDIASkillgithub
Interact with GitHub using the gh CLI restricted to REST API only (no GraphQL). Use when the user wants to work with GitHub issues, pull requests, repos, releases, or Actions — especially in sandboxed environments where the GraphQL endpoint may be blocked. Trigger keywords - github, gh, pull request, PR, github issue, github actions, workflow, release, gh api.
Also in 5 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- NousResearch/hermes-agent★ 262ksame name
- aivrar/portable-hermes-agent★ 239same name
- wundercorp/loki★ 28same name
- Samin12/skills★ 8same name
- abduznik/abduznik-skills★ 2same name
- rmusser01/tldw-stuff★ 2same name
- ashleysbrain/skills★ 1same name
- barzzly/BarzzLyp_Agent_Skills★ 0same name
- nobodyohm-web/Thot★ 0same name
- rakaarwaky/agents-arwaky★ 0same name
1 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 repository13 other files it gives its agents.
- site/llms-full.txtllms.txt
- site/llms.txtllms.txt
- checked-spreadsheet-analysisSkill
- document-to-action-itemsSkill
- gmail-browser-draftSkill
- google-calendar-browser-tasksSkill
- google-drive-browser-tasksSkill
- grounded-researchSkill
- meeting-action-itemsSkill
- private-team-reviewSkill
- systematic-debuggingSkill
- todoist-browser-tasksSkill
- use-mac-appsSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this method when the user asks to review their week, plan priorities, or follow up on unfinished work.
“Common” is measured: kept by at least 6 in 10 of the 11 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 review & planning
Use this method when the user asks to review their week, plan priorities, or follow up on unfinished work.
- Establish the requested date range and time zone from the user or current context. Read authorized sources; work_collect can gather a bounded morning snapshot. It is not a full weekly calendar or inbox export. Use available calendar/search tools for other dates and explicitly list sources you could not inspect.
- Separate completed work (with evidence), still-open commitments, waiting items, and suggestions. Absence from a new snapshot does not mean completion. Keep a short source link or document section for each material commitment.
- Make an action list with outcome, owner, due date, next step, dependency and source. Preserve unspecified owners/dates as “Not set.” Ask only about ambiguities that prevent a useful plan.
- Compare the proposed workload with visible appointments and the user's stated capacity. Offer a small number of priorities, a realistic first step, and work to defer. Do not invent free time from an incomplete calendar.
- Return a readable weekly plan, not a narration of tool calls. Save a requested document in the workspace and verify it with task_verify. If using a work_report, preserve its source receipts and partial coverage.
- Publishing tasks, sending follow-ups or changing a calendar requires the relevant connected tool and its approval. Read back confirmed changes; report a timeout as uncertain and check before retrying.
Finish with priorities, next actions, waiting items and coverage gaps. A plan is not proof those actions happened.
Provenance
Reviewed Sidemates adaptation of weekly-review-planning. Instructions are bundled with Sidemates and do not grant tool or account permissions. See LICENSE for reuse terms.
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.