agentleFS
CaskeyCodingCaskeyCoding/specself-starter/.claude/skills/monthly/SKILL.md

monthly

Skill0 starsChanged 4 months agoMITView on GitHub

Monthly deep review (~60 min) — synthesize candidate principles from the month's evidence, pressure borrowed ones, run a full-stack coherence pass. Supersedes the generic /review monthly. Use for the monthly tier.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. gaiaaiagent/regen-heartbeat★ 2same name
    2. KKenny0/Tracework★ 2same 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 repository9 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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 monthly tier as Skeptic + Therapist.

    line 6
  2. Very specific:

    Run the full six-check coherence pass from steering/coherence.md across the whole stack.

    line 15
  3. Distinctive:

    Read the report's Trend section back into the wrap: a finding on a streak outranks a fresh one, so let the ONE question come from a streak …

    line 18
  4. Very specific:

    Write candidates as <!-- CANDIDATE - edit or delete --> blocks.

    line 24

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

Run the SpecSelf monthly tier as Skeptic + Therapist. Honor AGENTS.md.

Read first: steering/cadence.md (monthly row), steering/methodology.md, steering/coherence.md, steering/tone.md; personas skeptic.md + therapist.md.

  1. Synthesize the month's reviews and evidence into candidate principles. Pressure any that sound borrowed rather than lived (Skeptic); make room for what is hard to say (Therapist).
  2. For each candidate principle: rate confidence and write a falsification criterion.
  3. Run the full six-check coherence pass from steering/coherence.md across the whole stack; produce the ranked report. Persist it: python scripts/coherence.py your-life --write your-life/reviews/coherence --tier monthly. Read the report's Trend section back into the wrap: a finding on a streak 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. Hydrate templates/review-monthly.md to your-life/reviews/.

Write candidates as <!-- CANDIDATE - edit or delete --> blocks. Promote nothing without the human's sign-off; recommend transitions with evidence, make none.

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.