review
Skill0 starsChanged 51 days agoMITView on GitHub
My Business Brain Sunday evening review and updates pack. Checks the watch list for changes at official pages, supplier prices and industry feeds, then runs the health check, the week's changes, past work affected by changed facts, open sentiment and leads, unsaved facts, golden answers, the research toolkit and the dashboard, in one short report. Use when the user runs /my-business-brain:review, asks for the weekly or Sunday review, asks what changed this week, or wants to watch a page or feed for changes.
192 other projects use a version of this.
Adopted by
Most recently taken up by
- dzhng/skillstheir own version, first seen Nov 15, 2026
- muxy-app/muxytheir own version, first seen Nov 15, 2026
- macro-inc/macrotheir own version, first seen Nov 15, 2026
- yagizdo/quivertheir own version, first seen Nov 15, 2026
- markmhendrickson/neotomatheir own version, first seen Nov 15, 2026
- felipeam86/pipe-skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use close-spec, daily-arxiv and 10 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.
dzhngSkillclose-spec
When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).
Also in 5 projects that use this
LambenthanSkilldaily-arxiv
每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新
Also in 5 projects that use this
dzhngSkilldesign-with-images
Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.
Also in 5 projects that use this
LambenthanSkillexp-eval
实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges
Also in 5 projects that use this
- +5 more from Lambenthan
- +3 more from dzhng
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- garrytan/gstack★ 142ksame name
- ansible/ansible★ 71ksame name
- docling-project/docling★ 71ksame name
- traefik/traefik★ 66ksame name
- ClickHouse/ClickHouse★ 51ksame name
- temporalio/temporal★ 24ksame name
- ccch1mneyyy/dsh-Go★ 24ksame name
- tisfeng/Easydict★ 15ksame name
- juicedata/juicefs★ 15ksame name
- elie222/inbox-zero★ 13ksame name
182 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 repository9 other files it gives its agents.
- analyzeSkill
- askSkill
- briefSkill
- chiefSkill
- contract-clocksSkill
- healSkill
- learnSkill
- my-business-brainSkill
- setupSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 156 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Toolkit: only if something changed, or a missing helper would have made this week's work easier (the user installs it.
- Very specific: line 23
If no Sunday review is scheduled, offer once to schedule it for Sunday evening in the owner's time zone (${user_config.timezone}, ask if …
“Common” is measured: kept by at least 6 in 10 of the 156 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
/my-business-brain:review
Set the week up in five minutes.
- Load the
my-business-brainskill from this plugin (via the Skill tool). If it cannot be loaded, read../my-business-brain/SKILL.mdand../my-business-brain/references/research-and-watch.mddirectly. - Find the brain (the folder with
BRAIN.md). If there is none, offer/my-business-brain:setupfirst. - Watch list. If the user wants a page or feed followed, add it:
scripts/watch.py <brain> add URL --name "..." [--entries ID,...] [--keywords "..."]. If the list is empty and the brain holds official facts (VAT, licence fees, filing dates) or supplier prices, suggest two or three sources worth watching, from the most authoritative source for each (references/trusted-sources.md), and add the ones the user agrees to. - Run the review:
scripts/weekly_review.py <brain>(from the core skill folder), with--langset to the language of record. It runs the watch check, health, the week's changes, impact, signals, unsaved facts, golden answers, the toolkit check and the dashboard, and saves_system/reviews/<date>.md. Where scripts cannot run, do the same checks by hand in that order. - Report answer first as the brain's identity (
scripts/identity.py <brain> card), in the language of record (${user_config.language}):- One headline line: the health score, how many possible fact changes, open leads, and anything drifting.
- Needs your decision: each "may affect what the brain knows" item, with the entry it touches. Offer to check it at the official source now (vet it; the brain never changes a fact because a page changed), then supersede and report the impact if it holds.
- Leads and sentiment: say they are not facts. For each lead, offer to confirm (then
signals.py <brain> confirm ID --entry ENTRY) or dismiss it. - This week: what the brain learned and changed, past work affected, unsaved facts and golden answers, a line each.
- Promises and delegations: overdue first, with an offer to draft the follow-ups (
delegations.py nudges; sending needs the owner's yes). - Agents and playbook: any specialist whose scores dropped, and anything new in the playbook.
- Toolkit: only if something changed, or a missing helper would have made this week's work easier (the user installs it; the brain never does).
- Offer to open the dashboard. In the first week of a month, mention the journal for the month just ended.
- If no Sunday review is scheduled, offer once to schedule it for Sunday evening in the owner's time zone (
${user_config.timezone}, ask if unknown), or the evening before their first working day if their weekend differs. Create it only if they say yes.
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.

