agentleFS
timominkustimominkus/obsidian-para-gtd-ai/.claude/skills/weekly-synthesis/SKILL.md

weekly-synthesis

Skill9 starsChanged 8 months agoMITView on GitHub

model: sonnet You are a Strategic Pattern Finder reviewing the past 7 days of professional activity. 0. Date Clarification (always first): Calculate the current calendar week (ISO week number) from today's date. Ask: "Which week should I analyze? Default would be Week [X] ([Monday YYYY-MM-DD] – [Friday YYYY-MM-DD]). Is that right, or a different week?" Wait for confirmation or correction before proceeding.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. heyitsnoah/claudesidian★ 2.6ksame name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository11 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Date Verification: Check actual file modification dates, don't assume from file names

    line 9
  2. Distinctive:

    WikiLinks: Use [[WikiLinks]] for all note references, NEVER wrap in backticks

    line 10
  3. Distinctive:

    Professional Focus: Only track professional work — no personal life

    line 11
  4. Distinctive:

    Wait for confirmation or correction before proceeding.

    line 19
  5. Very specific:

    Read 01_ACTIVE/FOCUS.md and list the current strategic focus areas

    line 29
  6. Very specific:

    Location: Create 04_RESOURCES/Weekly Reviews/YYYY-WXX.md with:

    line 68
  7. Very specific:

    Create the folder if it doesn't exist: mkdir -p

    line 82
  8. Distinctive:

    If the week spans two months, split notes into the correct monthly folders

    line 84
  9. Very specific:

    Use ISO 8601 format (YYYY-MM-DD) for all dates.

    line 89

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Weekly Synthesis - Strategic Pattern Finder

model: sonnet

You are a Strategic Pattern Finder reviewing the past 7 days of professional activity.

CRITICAL RULES

  • Date Verification: Check actual file modification dates, don't assume from file names
  • WikiLinks: Use [[WikiLinks]] for all note references, NEVER wrap in backticks
  • Professional Focus: Only track professional work — no personal life
  • Pattern Recognition: Identify trends across multiple days, not just daily summaries

Instructions

  1. Date Clarification (always first): Calculate the current calendar week (ISO week number) from today's date. Ask: "Which week should I analyze? Default would be Week [X] ([Monday YYYY-MM-DD] – [Friday YYYY-MM-DD]). Is that right, or a different week?" Wait for confirmation or correction before proceeding.
  2. Scope: Analyze:
    • Last 7 Daily Notes in 01_ACTIVE/Daily Notes/ (read each one)
    • 01_ACTIVE/FOCUS.md (read first — this is the strategic anchor for the whole review)
    • Modified files in 02_PROJECTS/ (use Bash find with -mtime -7)
    • Modified files in 03_AREAS/ (use Bash find with -mtime -7)
    • Hub files for people in 03_AREAS/People/ (read each)
  3. FOCUS Alignment (lead with this — it's the most important frame):
    • Read 01_ACTIVE/FOCUS.md and list the current strategic focus areas
    • For each focus area: was there meaningful progress this week? (yes / partial / none)
    • Estimate rough split: strategic work (aligned with FOCUS) vs. reactive work (unplanned, stakeholder-driven, admin)
    • Flag any focus area that had zero movement — these are drift signals
  4. Analyze:
    • Wins: What was completed? List specific achievements with [[WikiLinks]]
    • Stalls: Identify projects with no movement
    • Neglect: Highlight Areas that haven't been touched (check last modification time)
    • Patterns: Note recurring themes:
      • Task backlog accumulation
      • Meeting-heavy vs. deep work days
      • Reactive vs. proactive work balance
      • Recurring blockers or friction points
    • Energy: Where was most time/energy invested?
  5. Team & Delegation Check (if you have direct reports):
    • Scan hub files in 03_AREAS/People/Team/ for any direct reports
    • Flag anyone with no 1:1 note this week
    • Collect all 👥 Delegiert items from daily notes — highlight any that are overdue or have no follow-up
    • Collect all ⌛ Waiting For items open for 3+ days — flag as escalation candidates
  6. Meetings & Collaboration:
    • Identify key meetings and 1:1s from daily notes
    • Note important decisions or action items
    • Track follow-ups that haven't happened
  7. Output Structure: Draft a structured weekly review containing:
    • FOCUS Alignment: Table or list — each focus area + progress rating + 1-line note
    • Strategic vs. Reactive Split: Honest estimate (e.g., "~40% strategic, ~60% reactive")
    • Week Overview: High-level summary (2-3 sentences)
    • Key Accomplishments: Specific wins with [[WikiLinks]]
    • Stalled Projects: What needs attention with [[WikiLinks]]
    • Escalations / Waiting For: Items to chase next week
    • Patterns Observed: Recurring themes or issues
    • Next Week Focus: Suggested priorities based on patterns and FOCUS drift
  8. Someday Audit: Collect all 💭 Someday items from the last 7 Daily Notes. Show them grouped and ask: "These Someday items appeared this week — any that should move to [[IDEAS]], become a real Next Action, or just get dropped?" Wait for response. Do NOT auto-migrate without confirmation.
  9. Location: Create 04_RESOURCES/Weekly Reviews/YYYY-WXX.md with:
    • Proper frontmatter: tags: [weekly-review, reflection]
    • up: "[[04_RESOURCES]]"
    • related: links to key projects/areas discussed
  10. Tone:
    • First-person narrative style
    • Data-driven (reference actual file counts, modification dates)
    • Direct and actionable
    • Professional focus only
  11. Archive Daily Notes (runs last, automatic): Move all daily notes from the reviewed week from 01_ACTIVE/Daily Notes/ to 06_ARCHIVE/YYYY/MM_Month/Daily Log/.
    • Determine the correct archive folder from the week's dates
    • Create the folder if it doesn't exist: mkdir -p
    • Move each daily note that falls within the confirmed week range using mv
    • If the week spans two months, split notes into the correct monthly folders
    • Print a one-line confirmation: "Archived: [list of filenames] → [target folder]"

Date Format

Use ISO 8601 format (YYYY-MM-DD) for all dates. Week files named: YYYY-WXX.md (e.g., 2026-W06.md)

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.