agentleFS
ozgurkarahanozgurkarahan/ai-agent-memory/.claude/skills/close-week/SKILL.md

close-week

Skill8 starsChanged 4 months agoMITView on GitHub

Close out the working ISO week: aggregate ops/activity.jsonl events, regenerate the activity table between BEGIN/END sentinels, draft Friday review (wins, misses, lessons to graduate, seed for next week), freeze the week file. Trigger: 'close week', 'Friday review', '/close-week'.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the user says "close week", "Friday review", or "/close-week":

    line 8

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Close Week

When the user says "close week", "Friday review", or "/close-week":

Resolve the memory root

Resolve WIKI_ROOT using memory/schema.md, then schema.md, then the pointer in AGENT.md. Stop with the missing path if none contains both schema.md and index.md. All paths below are relative to WIKI_ROOT.

  1. Resolve active ISO week (TZ Europe/Paris) → ops/weekly/2026-W{NN}.md.
  2. Aggregate ops/activity.jsonl events for that week — group by topic, count touches, list days, find last. Sort by touches desc.
  3. Regenerate the activity block between the sentinels (wholesale replace):
    <!-- BEGIN GENERATED ACTIVITY -->
    ...table...
    <!-- END GENERATED ACTIVITY -->
    Wikilink rule: [[topic]] only if resolved: true; else plain text + *(unresolved)*.
  4. Optional connected-source pull for "what shipped" — sent mail, collaboration decisions, meetings, or modified files. Skip when no work-data tool is available.
  5. Draft Friday review sections: Wins · Misses · Lessons → graduate (propose ingest targets, don't auto-run) · Seed for W+1 (top-3 carry-over per topic).
  6. Freeze: status: closed, bump date_updated, append log.md entry: ... CLOSE-WEEK | 2026-W{NN} | events: N | topics: [...] | wins: N | lessons-promoted: N.
  7. (Optional) Seed W+1 — create ops/weekly/{next}.md skeleton.

Anti-patterns:

  • ❌ Do not edit outside the sentinels on regenerate.
  • ❌ Do not auto-/ingest lessons — explicit user confirm per item.
  • ❌ Do not reopen a closed week. Late events → current open week with a note.
  • ❌ ops/activity.jsonl is append-only — never delete events at close.

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.