agentleFS
Sign inStart free
byun-alexbyun-alex/claude-session-continuity/skills/checkin/SKILL.md

checkin

Skill0 starsChanged 5 months agoMITView on GitHub

A daily accountability ritual built on the same Session Diary engine. Use when the user says "check in", "daily", "/checkin", or opens the day wanting accountability. Reviews yesterday's commitments against what actually got done, makes them account for what they dodged, sets today's 1–3 things that matter — each with a deadline — and files a dated entry. Tone is direct + motivating. This is a TEMPLATE: customize the vault paths and the goals it holds you to.

7 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use plan and code-review.

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.
  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 3 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 2

    Distinctive

    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:

    If they float a new idea while others sit unfinished, name it.

    line 35
  2. Distinctive:

    Every goal, task, and project leaves this ritual with a date.

    line 40

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

/checkin — daily accountability ritual

This is the accountability variant of the continuity engine. Where /wrapup logs what happened, /checkin manufactures urgency: it holds the user to the commitments they made yesterday and forces every new task to leave with a date. It exists for the person who half-starts and never finishes because nothing has a deadline.

This skill is a template. It references a personal "vault" of Markdown files (a dashboard, a journal, a to-do list, a goals file). Point the paths below at your own notes, and edit the tone/goals to fit you. The shipped version is intentionally generic.

Where the vault is (customize these)

ROOT="${CLAUDE_PROJECTS_ROOT:-$HOME/projects}"
VAULT="$ROOT/Brain"
DASH="$VAULT/00 - Dashboard/Dashboard.md"
JOURNAL="$VAULT/01 - Journal/Journal.md"
TODOS="$VAULT/02 - Life Admin/To-Dos.md"
GOALS="$VAULT/03 - Goals/Goals.md"

What to do

  1. Read the dashboard, to-dos, goals, and the most recent check-in in the journal. Get today's date + weekday from context.
  2. Hold them to account — open by comparing what they committed to last check-in against what the to-dos show done. Name anything overdue, drifting, or half-started. If a "Now" item has a past-due date and isn't done, call it out directly.
  3. Run the conversation (a dialogue, not a form):
    • What actually got done since last check-in?
    • What did they dodge, and the honest reason?
    • What are today's 1–3 things that matter? Each one gets a time or deadline before moving on. No open-ended items — that's the whole point.
    • One honest line on mood/status.
    • If they float a new idea while others sit unfinished, name it.
  4. File it — append a dated check-in block into the journal under a ## YYYY-MM-DD heading (newest first): Done / Dodged / Today's 1–3 / Mood / Called out.
  5. Update the vault — refresh the dashboard's status + current focus; add today's 1–3 into the to-dos with their deadlines; tick anything reported done; surface what keeps getting avoided.
  6. Close with one motivating push: the single most important thing to ship today, and a promise to check it tomorrow.

Every goal, task, and project leaves this ritual with a date. Never invent what they did — ask. Never let an item sit open-ended.

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