weekly
Skill1 starsChanged 31 days agoMITView on GitHub
Run a guided weekly review of the user's Big Brain: inbox triage, active-project review, task hygiene, vault health, and consolidation. Use for weekly reviews, brain cleanup, inbox triage, or explicit $weekly invocation.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- saksham10arora-dotcom/everything-claude-codextheir own version, first seen Nov 8, 2026
- ChadPapineau/espn-fantasy-football-mcptheir own version, first seen Nov 1, 2026
- noahcostakes/claudebrain-templatetheir own version, first seen Oct 15, 2026
- gaiaaiagent/regen-heartbeattheir own version, first seen Oct 15, 2026
- pqmcgill/familytheir own version, first seen Oct 13, 2026
- mhxie/Ateliertheir own version, first seen Oct 12, 2026
Used with
Projects with it also use decide, setup and 2 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.
dirienSkilldecide
Three-agent adversarial debate protocol for strategic decisions. Two advocates steelman opposing positions while a moderator identifies risks and synthesizes a binding consensus. Use when choosing between alternatives, evaluating tradeoffs, or making high-stakes decisions.
Also in 3 projects that use this
VercelSkillsetup
Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".
Also in 6 projects that use this
SentrySkillonboard
Onboard a service to sentry-options. Use when integrating a new service, creating schemas, or setting up the multi-repo sentry-options workflow.
Also in 3 projects that use this
- SentrySkill
review
Fixture review skill.
Also in 3 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- kv0906/pm-kit★ 138same name
- saksham10arora-dotcom/everything-claude-codex★ 74same name
- alirezarezvani/gaios★ 37same name
- iwe-org/dev-workspace★ 11same name
- matteo-stratega/claude-cortex★ 8same name
- iwe-org/marketing-workspace★ 5same name
- mhxie/Atelier★ 5same name
- fotoflo/claude-skills★ 2same name
- gaiaaiagent/regen-heartbeat★ 2same name
- KKenny0/Tracework★ 2same name
7 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.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
0
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
- could be automatic: a setting could enforce it
- Very specific: line 15
Snapshot: Run big-brain status and big-brain doctor.
- Very specific: line 29
Consolidate: Use doctor findings and big-brain related <note> to propose splits for bloated notes, merges for near-duplicates, and …
- Very specific: line 36
Prefer Big Brain tools/CLI for mutations.
“Common” is measured: kept by at least 6 in 10 of the 15 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
Big Brain weekly review
Resolve the vault through big-brain; do not hardcode its path. This is a
working meeting with the user. Gather and propose first, then apply the approved
batch. Aim for about ten minutes.
- Snapshot. Run
big-brain statusandbig-brain doctor. Lead with the two or three items needing attention: overdue tasks, stale projects, inbox pileup, or broken links. - Inbox triage. For each inbox item, propose one destination: merge into an existing note/project, create a linked note, create tasks, or archive. Batch the proposals and obtain confirmation before moving/archiving.
- Project walk. For each active project, show latest log entries, open tasks, and blockers. Ask whether it remains active. For projects untouched for 2+ weeks, propose a concrete next task or status change.
- Task hygiene. Resolve every overdue task as do-this-week with a real new date, someday with no date, or dead. Never roll a due date forward silently twice; flag that as a scoping/priority signal.
- Doctor fixes. Fix obvious broken wikilinks/duplicate names only after the batch is confirmed. List ambiguous findings.
- Consolidate. Use doctor findings and
big-brain related <note>to propose splits for bloated notes, merges for near-duplicates, and removal/striking of stale facts. Never merge, archive, or rewrite notes without confirmation. - Record. Log projects reviewed, status/task changes, inbox work, consolidations, and the user's stated focus for next week in today's daily note.
Prefer Big Brain tools/CLI for mutations. Preserve area, tags, frontmatter,
tasks, and wikilinks. Never store secrets. Writes may auto-commit/push; avoid
duplicate manual commits. Keep each exchange short and concrete.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.