agentleFS
Sign inStart free
Yosei-Lab-aiYosei-Lab-ai/Miragoe/checkpoint/SKILL.md

checkpoint

Skill0 starsChanged 3 months agoMITView on GitHub

Measure your Identity Alignment Score. Honest assessment of how well your actions match your declared identity.

91 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use aside, spinoff and 10 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.
  • TheKREATORSSkill

    aside

    Answer a quick side question without interrupting or losing context from the current task. Resume work automatically after answering.

    Also in 3 projects that use this

  • AhmedMerzaSkill

    spinoff

    After a branch is finished, harvest the work it made CHEAP — the helper you wrote that four other sites now hand-roll, the plumbing that turned a deferred feature small, the pattern that just split the codebase in two. Produces a follow-up backlog (0–3 candidates, feeding /issue), NEVER commits on the current branch. Invoke with /spinoff at the tail of the chain — after /fix-review has settled the review findings, before the MR merges — or when the user asks \"what else should we do while we're here / what did this unlock / anything to follow up on\". This is ship-check's optional twin — that finds what's MISSING and blocks the merge; this finds what's now CHEAP and blocks nothing. Restraint-gated: \"nothing spun off\" is the common and correct answer, and a finding that would have been equally valid before this branch is not a finding.

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-export

    Export instincts from project/global scope to a file

    Also in 3 projects that use this

  • seek888Skill

    open-gstack-browser

    Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in. Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser". Voice triggers (speech-to-text aliases): "show me the browser".

    Also in 5 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 5 projects that use this

  • seek888Skill

    design-html

    Design finalization: generates production-quality Pretext-native HTML/CSS. Works with approved mockups from /design-shotgun, CEO plans from /plan-ceo-review, design review context from /plan-design-review, or from scratch with a user description. Text actually reflows, heights are computed, layouts are dynamic. 30KB overhead, zero deps. Smart API routing: picks the right Pretext patterns for each design type. Use when: "finalize this design", "turn this into HTML", "build me a page", "implement this design", or after any planning skill. Proactively suggest when user has approved a design or has a plan ready. (gstack) Voice triggers (speech-to-text aliases): "build the design", "code the mockup", "make it real".

    Also in 5 projects that use this

  • +2 more from TheKREATORS
  • +2 more from seek888

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 85 edited versions we read keep these.

  • 3

    Distinctive

    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. Very specific:

    When implemented, /miragoe-checkpoint will:

    line 27
  2. Very specific:

    Read ~/.miragoe/state/current.md and the approved vision for identity context

    line 28
  3. Very specific:

    Read active goals from ~/.miragoe/goals/

    line 29
  4. Distinctive:

    Ask the user what they did since last checkpoint

    line 30
  5. Distinctive:

    Put any recommended identity, goal, or commitment change in a proposal and update the resume pointer without changing approved state

    line 35
  6. Very specific:

    Follow ../docs/artifact-lifecycle.md.

    line 40
  7. Distinctive:

    Never overwrite an earlier checkpoint or automatically edit vision, goals, or commitments.

    line 41

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

This skill is planned for Phase 2.

You are an Alignment Analyst — compassionate but unflinching in your assessment of how well someone's actions match their declared identity. You celebrate wins and confront gaps with equal directness.

Design Intent

/miragoe-checkpoint is the measurement heartbeat of Miragoe. Run daily or weekly, it answers the core question: "Am I living as the person I declared myself to be?" It produces an Identity Alignment Score (0-100) based on concrete evidence, not feelings.

Why This Skill Is Needed

Without measurement, identity work becomes wishful thinking. The brain defaults to recency bias: one bad day erases a good week. /miragoe-checkpoint provides an honest, persistent mirror. Over time, the trend line matters more than any single score — and seeing that trend is what sustains motivation through difficult periods.

Key Design Decisions

  • Scoring formula: Action completion (40%) + Identity congruence (30%) + Directional momentum (20%) + Self-awareness (10%)
  • Evidence-based: every score point must be backed by a specific action or observation
  • Compassionate confrontation for low scores — not punishment, not denial
  • Reports saved to ~/.miragoe/miragoe-checkpoints/{date}.md for trend analysis

Phase 2 Implementation Notes

When implemented, /miragoe-checkpoint will:

  1. Read ~/.miragoe/state/current.md and the approved vision for identity context
  2. Read active goals from ~/.miragoe/goals/
  3. Ask the user what they did since last checkpoint
  4. Score each dimension with specific evidence
  5. Calculate and present the Identity Alignment Score
  6. Save a new immutable report to ~/.miragoe/miragoe-checkpoints/{date}-{id}.md
  7. Show trend data if previous checkpoints exist
  8. Put any recommended identity, goal, or commitment change in a proposal and update the resume pointer without changing approved state

Artifact Contract

Follow ../docs/artifact-lifecycle.md. A checkpoint is an observation, not an approval. Never overwrite an earlier checkpoint or automatically edit vision, goals, or commitments.

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