agentleFS
prateekjainprateekjain/ChiefOfStaff/skills/daily-digest/SKILL.md

daily-digest

Skill4 starsChanged 8 months agoMITView on GitHub

Generate a portfolio-wide daily briefing and update Notion

17 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Read portfolio/registry.md to get all active ventures (exclude KILLED, PAUSED, MATURE).

    line 24
  2. Distinctive:

    If the venture repo isn't cloned locally, use:

    line 41
  3. Very specific:

    Write the digest to digests/daily/{YYYY-MM-DD}.md.

    line 84
  4. Distinctive:

    Search for the "Digests" database in Notion and create a new page:

    line 88
  5. Distinctive:

    If this was triggered manually (not by scheduled task), display the digest to the founder.

    line 97

“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.

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

Daily Digest — Portfolio Briefing

Generate the founder's daily briefing across all ventures.

Step 1: Read Portfolio State

Read portfolio/registry.md to get all active ventures (exclude KILLED, PAUSED, MATURE).

Step 2: Gather Venture States

For each active venture, read its state. Use Bash to pull latest if the repo is cloned locally:

cd $PROJECTS_DIR/{slug} && git pull --quiet 2>/dev/null

Then read:

  • CLAUDE.md — for venture context and current focus
  • plans/current.md — for active plan and task status
  • metrics/ — for latest KPIs (if any files exist)
  • decisions/ — for recent decisions (check dates)
  • docs/changelog.md — for recent changes

If the venture repo isn't cloned locally, use:

gh repo clone {user}/{slug} $PROJECTS_DIR/{slug} -- --quiet 2>/dev/null

Step 3: Generate Digest

Spawn the reporter agent to generate the digest:

Generate a daily portfolio digest for today ({date}).

Data for each venture:
{pass the state data gathered in Step 2}

Use this format:

# Daily Briefing — {date}

## Decisions Needed
- [Venture] What needs founder input and why

## Progress Today
| Venture | Stage | Activity | Result |
|---------|-------|----------|--------|

## Key Metrics
| Venture | MRR | Users | Health | Trend |
|---------|-----|-------|--------|-------|

## Blockers
- [Venture] What's blocked and what would unblock it

## Tomorrow's Plan
- [Venture] What agents will work on next

If there are no decisions needed, omit that section.
If a venture has no metrics yet (early stage), show "—" for metrics.
Keep it concise — the founder should be able to scan this in 2 minutes.

Step 4: Save Digest

Write the digest to digests/daily/{YYYY-MM-DD}.md.

Step 5: Update Notion

Search for the "Digests" database in Notion and create a new page:

  • Title: "Daily Briefing — {date}"
  • Type: Daily
  • Content: The full digest in Notion markdown format

Also update the "Ventures" database entries with latest health scores and activity dates.

Step 6: Display to User

If this was triggered manually (not by scheduled task), display the digest 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.