agentleFS
matteo-strategamatteo-stratega/claude-cortex/.claude/skills/brief/SKILL.md

brief

Skill8 starsChanged 5 months agoMITView on GitHub

Quick daily status overview (~20 lines) — focus, priorities, blockers, key numbers. Use when the user asks for a brief, a daily status, or "what's on today".

81 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use capture, strategy and 8 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.
  • toneron2Skill

    capture

    Capture thoughts to inbox with automatic classification

    Also in 6 projects that use this

  • EpistatesSkill

    strategy

    Plan weekly or monthly X content strategy. Use when the user wants to plan their content calendar, set growth goals, build a content pipeline, or think strategically about their X presence.

    Also in 4 projects that use this

  • aleksander-dytkoSkill

    decision

    Make a product decision with full context from the vault and available sources

    Also in 3 projects that use this

  • dirienSkill

    decide

    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 5 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 7 projects that use this

  • howellsSkill

    reconcile

    Audit a project against current plugin conventions and offer to update structure.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 74 edited versions we read keep these.

  • 3

    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
  1. Very specific:

    Read the latest closing report: notes/daily-summaries/closing-*.md (solo workspace), or the most recent under …

    line 13
  2. Distinctive:

    If no closing report exists, skip "Yesterday" section

    line 43
  3. Distinctive:

    Don't load area context files — the brief uses the index only

    line 44
  4. Distinctive:

    If no numerical data in context, omit "Quick Numbers" rather than guessing

    line 45

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

Generate a quick status overview:

Step 1: Load Context

  1. Read brain/context.md
  2. Read the latest closing report: notes/daily-summaries/closing-*.md (solo workspace), or the most recent under notes/daily-summaries/*/closing-*.md (team workspace — brain/team.md lists 2+ users)

Step 2: Generate Brief

Output this format:

## Brief — [Today's Date]

**Focus:** [Main area from context]

### Yesterday
- [Key completions from last closing report]

### Today's Priorities
1. [From "This Week" in context — what's most urgent]
2. [Second priority]
3. [Third priority]

### Blockers
- [Anything waiting on someone else or stuck]

### Quick Numbers
- [Any key metrics from context: MRR, pipeline, deadlines]

Rules

  • Max 20 lines total. This is a glance, not a report.
  • Priorities come from context.md "This Week" section
  • If no closing report exists, skip "Yesterday" section
  • Don't load area context files — the brief uses the index only
  • If no numerical data in context, omit "Quick Numbers" rather than guessing

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.