weekly
Skill11 starsChanged 2 days agoMITView on GitHub
Compose a weekly project digest from the workspace — what shipped, active plans and their staleness, open and recurring bugs, top backlog, new learnings, and graph health, ending with the single most leveraged next action. Read-only; prints without writing files. Use when the user asks for a "weekly digest", "status report", or a start-of-week review.
18 other projects use a version of this.
Adopted by
Most recently taken up by
- ychampion/ystacktheir own version, first seen Nov 15, 2026
- jzhao234/big-braintheir own version, first seen Nov 8, 2026
- 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
Used with
Projects with it also use capture, decide 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.
toneron2Skillcapture
Capture thoughts to inbox with automatic classification
Also in 4 projects that use this
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
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
SentrySkillreview
Fixture review skill.
Also in 3 projects that use this
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- kv0906/pm-kit★ 138same name
- saksham10arora-dotcom/everything-claude-codex★ 96same name
- alirezarezvani/gaios★ 50same name
- matteo-stratega/claude-cortex★ 8same name
- iwe-org/marketing-workspace★ 6same name
- mhxie/Atelier★ 5same name
- ychampion/ystack★ 4same name
- fotoflo/claude-skills★ 2same name
- gaiaaiagent/regen-heartbeat★ 2same name
- KKenny0/Tracework★ 2same name
8 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
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
2
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 45
Read-only: this skill writes no files and changes no statuses.
- Distinctive: line 48
Every number in the digest traces to a query, or to git where the workspace has it — no estimates.
“Common” is measured: kept by at least 6 in 10 of the 16 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 digest
A read-only sweep of the graph that answers: what moved, what's stuck, what's
next. Numbers come from frontmatter, and from git when the workspace is a git
repository (git rev-parse --is-inside-work-tree) — never from memory.
Steps
- Shipped. Plans and bugs completed in the last 7 days:
iwe find --filter '{type: {$in: [plan, bug]}, stage: done, completed: {$gte: <YYYY-MM-DD, 7 days ago>}}' --project completed. Releases cut:iwe find --filter '{type: release, date: {$gte: <YYYY-MM-DD, 7 days ago>}}' --project version,date. In a git repository, cross-check withgit log --since '7 days ago' --oneline. - In flight. Active plans (no
stage, orapproved) under## Activeindata/plans.md; flag any untouched for 14+ days as possibly stalled or silently done. Last touched is the last commit on the file (git log -1 --format=%cs -- data/plans/<key>.md) in a git repository, and otherwise the plan'sgenerated.at, or the file's modification date when that is missing. - Open bugs. Tickets under
## Openindata/bugs.md, split byreported_by(user-reported first), plus any with two or moreaffected_versions— those came back after a fix. - Backlog head.
## Highitems indata/backlog.md, plus how long they've sat (created). - Learnings. Learnings dated this week, one line each:
iwe find --filter '{type: learning, created: {$gte: <YYYY-MM-DD, 7 days ago>}}' --project created. - Graph health.
iwe schema validate(report violations) andiwe stats.iwe statsprints a## Broken Linkssection and a## Orphanssection only when there is something to list. Healthy means no violations, no## Broken Linkssection, and nodata/document under## Orphans: every document underdata/is reachable from a hub, the hubs fromdata/index.md, anddata/index.mdanddata/log.mdfrom the start page. - Print the digest — shipped / in flight / bugs / backlog / learnings / health — and end with the single most leveraged next action, chosen from what the sweep showed, with a one-line justification.
Rules
- Read-only: this skill writes no files and changes no statuses; if the sweep finds inconsistencies (a done plan still under Active, a fixed bug still under Open), report them as the next action instead of fixing silently.
- Every number in the digest traces to a query, or to git where the workspace has it — no estimates.
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.

