agentleFS
curv-institutecurv-institute/atlas/.claude/skills/snapshot/SKILL.md

snapshot

Skill0 starsChanged 4 months agoMITView on GitHub

Produce a short, plain-English status of the whole program - what's solid, what's new since the canonical state, honest negatives/obstructions, and open/next - using fast parallel reads. Explains results in lay terms, never just citing gate names. Use when the user says "/snapshot", "where do things stand", or "current status".

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    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:

    Read the canonical surfaces first and note their dates:

    line 12

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

/snapshot - plain-English status of the program

Goal: a short, simple-English briefing of the latest state. The reader may not be technical - explain what results mean, don't just cite them.

Step 1 - Orient (fast, yourself)

Read the canonical surfaces first and note their dates:

  • CURRENT_STATE.md - live claims, withdrawn register, adoptions, open work.
  • Home.md - the topic index. Then find what changed after the canonical state's date (recent commits / newest files) - those are the freshest results that may not be folded in yet. Flag them as not-yet-canonical.

Step 2 - Fan out (parallel reads)

Launch read-only agents concurrently, each with a tight scope (experiments, topic pages, and each repo listed in REPOS.md), each returning a plain-English summary: what was tested, the result, and whether it's a positive, a negative, an obstruction, or still open. Scale the fleet to the ask.

Step 3 - Synthesize

Write the briefing:

  • Headline - the single most important state right now.
  • What's solid - cleared-the-checklist claims, in lay terms (what it means).
  • What's new since canonical state - clearly marked if not yet folded in.
  • Honest negatives & obstructions - reported plainly, never buried.
  • Open / next - the live questions.

Rules: plain language (gloss any term on first use); never repeat a withdrawn number as if live; date the snapshot and name sources; separate "proven / replicated / toy-scope / open" honestly.

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.