agentleFS
Sign inStart free
saksham10arora-dotcomsaksham10arora-dotcom/everything-claude-codex/skills/weekly/SKILL.md

weekly

Skill74 starsChanged 9 days agoMITView on GitHub

Use when the user says "/weekly", "weekly review", "weekly", "review my week", "what shipped this week", "Sunday review", or "what slipped

17 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use capture, decide and 3 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

  • 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

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 6 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

  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 4

    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. Distinctive:

    Read in parallel, then stop reading once you have what you need:

    line 8
  2. Very specific:

    Only open a tracker (*_tracker.md) if hot.md lacks the detail.

    line 12
  3. Distinctive:

    Never invent a status or deadline.

    line 33
  4. Distinctive:

    If fewer than 7 daily notes exist, say how many were found.

    line 34
  5. Distinctive:

    If hot.md was last updated more than 2 days ago, say so.

    line 35

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

Read in parallel, then stop reading once you have what you need:

  1. daily/<date>.md for the last 7 dates, today included, skipping any file that does not exist
  2. .remember/hot.md for deadlines and active projects

Only open a tracker (*_tracker.md) if hot.md lacks the detail. Never read big trackers by default.

Output (exactly this, no intro)

WEEKLY: <start date> to <end date>

Shipped

One line per thing finished this week, taken from the daily notes. If none: "Nothing logged as shipped".

Slipped

One line per item that was planned in the daily notes or due this week and is not done. Name the file it came from.

Next week's deadlines

Date | What | Status, from hot.md for the next 7 days. If none: "None this week".

One thing to drop

One item from the slipped list or active projects that is worth stopping, with a one-line reason.

What do you want to start with next week?

Rules

  • Never invent a status or deadline. If it isn't in the files, say "unknown, check <file>".
  • If fewer than 7 daily notes exist, say how many were found.
  • If hot.md was last updated more than 2 days ago, say so.
  • At the end of the review, remind the user to run /tldr.

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.

Check your setup, free