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

weekly

Skill8 starsChanged 5 months agoMITView on GitHub

Weekly retrospective from closing reports — what shipped, decisions, patterns, next-week priorities. Use when the user asks for a weekly review or retrospective.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

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

    capture

    Capture thoughts to inbox with automatic classification

    Also in 4 projects that use this

  • lamb92009Skill

    inbox

    Use when the user runs /inbox or asks to process the inbox folder in the RDL vault. Reads unprocessed files, routes content to correct vault locations, creates or updates notes with wikilinks, and deletes processed originals.

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

  • SentrySkill

    onboard

    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

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 2

    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 all closing reports from the past 7 days: notes/daily-summaries/closing-*.md (solo workspace) plus any in per-user subfolders …

    line 12
  2. Very specific:

    Ask: "Should I update brain/context.md with next week's priorities?"

    line 50
  3. Distinctive:

    If yes, update the "This Week" section.

    line 52
  4. Distinctive:

    If fewer than 3 closing reports exist, say so and give a shorter review

    line 56

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

Generate a weekly retrospective from your closing reports.

Step 1: Gather Data

Read all closing reports from the past 7 days: notes/daily-summaries/closing-*.md (solo workspace) plus any in per-user subfolders notes/daily-summaries/*/closing-*.md (team workspace — brain/team.md lists 2+ users). A team weekly aggregates across everyone. Also read brain/context.md for current priorities.

Step 2: Generate Review

Output this format:

## Week Review — [Date Range]

### Shipped
- [Completed items across all sessions this week]

### Decided
- [Key decisions made — from "Key Decisions" sections]

### Blocked
- [Things that are stuck or waiting on someone]

### Numbers
- Sessions: [count]
- Areas touched: [list]

### Next Week
Based on what's done and what's pending:
1. [Top priority for next week]
2. [Second priority]
3. [Third priority]

### Patterns
- [Any recurring theme — e.g., "spent 60% of time on client work, only 10% on product"]
- [Anything that kept coming up as blocked]

Step 3: Update Context

Ask: "Should I update brain/context.md with next week's priorities?"

If yes, update the "This Week" section.

Rules

  • If fewer than 3 closing reports exist, say so and give a shorter review
  • "Patterns" section is the most valuable part — look for time allocation, recurring blockers, drift from stated priorities
  • Be honest about what didn't get done, not just what did
  • Max 30 lines total

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.