agentleFS
prateekjainprateekjain/ChiefOfStaff/skills/weekly-review/SKILL.md

weekly-review

Skill4 starsChanged 8 months agoMITView on GitHub

Generate a comprehensive weekly board review across all ventures

92 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use quarterly-review, daily-plan 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.
  • Phoenixrr2113Skill

    quarterly-review

    Quarterly review — strategic look at the last 3 months. Career trajectory, project health, life balance, big decisions ahead. Runs 1st of Jan/Apr/Jul/Oct.

    Also in 3 projects that use this

  • steptianSkill

    daily-plan

    每日待办计划与日程管理。触发词:'今天要做'、'今日计划'、'今日待办'、'今天安排'、'安排一下'、'加个任务'、'记个任务'、'今日复盘'、'今日回顾'、'今天总结'、'本周计划'、'周总结'、'开始工作'、'上班了'、'完成了'、'加个日程'、'记个日程'、'改一下时间'、'日程调整'、'面试'、'开会'、'约了'。支持四象限优先级、时段分配、固定日程管理、智能时间估算、每日/每周复盘。当用户提到有明确时间的安排(如'下午两点面试'、'10点开会'),自动识别为日程并写入日程表。

    Also in 3 projects that use this

  • seedprodSkill

    daily-brief

    Send a morning briefing via Telegram with weather, news, and a motivational quote. Designed to run via launchd for automated daily delivery.

    Also in 5 projects that use this

  • claude-office-skillsSkill

    meeting-notes

    >

    Also in 8 projects that use this

  • Phoenixrr2113Skill

    morning-brief

    Full morning brief — calendar, email, meeting prep, execute actionable items, create follow-up tasks. Runs at 8:03 AM or when Randy asks for a morning update.

    Also in 4 projects that use this

  • zephyrwang6Skill

    daily-review

    每日工作回顾与洞察分析,对用户前一天的对话历史和使用数据进行总结与建议

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 80 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read all daily digests from this week in digests/daily/:

    line 25
  2. Very specific:

    Read portfolio/registry.md for current state.

    line 31
  3. Very specific:

    Read the most recent file in digests/weekly/ for week-over-week comparison.

    line 41
  4. Very specific:

    If any new cross-venture lessons were identified, append them to knowledge/lessons.md.

    line 118
  5. Distinctive:

    Create a new page in the "Digests" database:

    line 122
  6. Distinctive:

    If triggered manually, display the review to the founder.

    line 129

“Common” is measured: kept by at least 6 in 10 of the 80 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Weekly Review — Board-Level Portfolio Review

Generate a comprehensive weekly review of the entire portfolio.

Step 1: Gather This Week's Data

Daily Digests

Read all daily digests from this week in digests/daily/:

digests/daily/{monday-date}.md through digests/daily/{friday-date}.md

Portfolio Registry

Read portfolio/registry.md for current state.

Per-Venture State

For each active venture, pull latest and read:

  • CLAUDE.md, plans/current.md, docs/changelog.md
  • metrics/ (all files)
  • decisions/ (this week's decisions)
  • learnings/ (this week's learnings)

Previous Weekly Review

Read the most recent file in digests/weekly/ for week-over-week comparison.

Step 2: Generate Review

Spawn the reporter agent to generate the weekly review:

Generate a comprehensive weekly board review for the week ending {friday-date}.

Use this structure:

# Weekly Review — Week of {monday-date}

## Portfolio at a Glance

| Venture | Stage | Health | MRR | WoW MRR | Users | WoW Users |
|---------|-------|--------|-----|---------|-------|-----------|

**Total portfolio MRR:** ${total}
**Active ventures:** {count}
**Average health:** {avg}/100

## Per-Venture Review

### {Venture Name} ({stage})
**Health:** {score}/100 ({change from last week})

**This week's achievements:**
- {achievement 1}
- {achievement 2}

**Key metrics:**
| Metric | This Week | Last Week | Change |
|--------|-----------|-----------|--------|

**Decisions made:**
- {decision with rationale}

**Concerns:**
- {any issues or risks}

**Next week's focus:**
- {planned work}

{Repeat for each venture}

## Cross-Venture Insights

### Patterns
- {Patterns observed across ventures}

### Lessons Learned
- {New lessons from this week}

### Resource Allocation
- {Are we spending time on the right ventures?}

## Strategic Recommendations

{2-3 strategic recommendations for the founder based on this week's data}

## Pending Founder Decisions

| Venture | Decision Needed | Urgency | Context |
|---------|----------------|---------|---------|

## Looking Ahead

{What's coming next week across the portfolio}

Step 3: Save Review

Write to digests/weekly/{YYYY}-W{WW}.md.

Step 4: Update Knowledge

If any new cross-venture lessons were identified, append them to knowledge/lessons.md.

Step 5: Update Notion

Create a new page in the "Digests" database:

  • Title: "Weekly Review — Week of {monday-date}"
  • Type: Weekly
  • Content: Full review in Notion markdown

Step 6: Display

If triggered manually, display the review to the founder.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.