agentleFS
Sign inStart free
CaskeyCodingCaskeyCoding/specself-starter/.claude/skills/weekly/SKILL.md

weekly

Skill0 starsChanged 4 months agoMITView on GitHub

Weekly review (~20 min) — cluster the week, run the six-check coherence pass, surface candidate updates, write the weekly review. Use for the weekly tier.

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

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

  • 0

    Common

    Most of the 14 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. Distinctive:

    Run the SpecSelf weekly tier as Coach + Journalist.

    line 6
  2. Very specific:

    Facts (Journalist): Read this week's your-life/journal/ entries.

    line 11
  3. Very specific:

    Coherence check: Run all six checks from steering/coherence.md against your-life/ (orphans, contradictions, starved areas, over-capacity, …

    line 15
  4. Distinctive:

    Read the written report's Trend section back into the wrap: a finding on a streak ("starved: area:health, 3rd consecutive report") outranks …

    line 20

“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

Run the SpecSelf weekly tier as Coach + Journalist. Honor AGENTS.md.

Read first: steering/cadence.md (weekly row), steering/coherence.md, steering/methodology.md, steering/tone.md; personas coach.md + journalist.md.

  1. Facts (Journalist). Read this week's your-life/journal/ entries; build the timeline.
  2. Execution vs intent (Coach). Where the week matched stated priorities; which project moved, which did not. Fact-check commitments.
  3. Coherence check. Run all six checks from steering/coherence.md against your-life/ (orphans, contradictions, starved areas, over-capacity, staleness, drift) and produce the compact ranked coherence report, not a flat dump. Persist it so this week remembers the last one: python scripts/coherence.py your-life --write your-life/reviews/coherence --tier weekly. Read the written report's Trend section back into the wrap: a finding on a streak ("starved: area:health, 3rd consecutive report") outranks a fresh one, so let the ONE question come from a streak when the trend shows one. The dated report is machine-derived and regenerable; never cite it as Evidence for a principle.
  4. Candidates. Surface candidate principles/habits/edits. Write each into its target file as a <!-- CANDIDATE - edit or delete --> block, clearly labeled, never committed.
  5. Hydrate templates/review-weekly.md to your-life/reviews/<YYYY-Www>.md.
  6. End with the ONE sharpest question and ask for next week's short commitments.

Recommend status transitions with their evidence; make none. The human confirms each.

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