plain-recap
Skill0 starsChanged 2 months agoMITView on GitHub
Give a plain-language status of the project — what works, what is half-finished, what is next — without file trees, git jargon or technical detail. Use when the user asks where they are, what has been done, what is left, or returns to a project after a break.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- nimishmehta/antria-officetheir own version, first seen Sep 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- nimishmehta/antria-office★ 0same 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 repository5 other files it gives its agents.
- templates/CLAUDE.mdCLAUDE.md
- error-translatorSkill
- explain-firstSkill
- plain-talkSkill
- short-answersSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
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
- Distinctive: line 8
When a non-technical user asks "where are we?", they are not asking for a changelog.
- Distinctive: line 22
Keep it tight. If a section is empty, delete it rather than writing "nothing here".
- Distinctive: line 27
Describe them as the user experiences them: If they can't click it, it's not working yet, no matter how much code exists.
- Distinctive: line 28
Half-done means half-done: Never round up to "done". If the button exists but doesn't save anything, that's half-done — say what's missing …
- Distinctive: line 29
No git: No commits, branches, merges, or "the working tree is clean".
- Distinctive: line 35
Use this only for something with a real consequence for them.
- Distinctive: line 41
If there is nothing like that, leave the section out.
- Distinctive: line 45
If the user is coming back after some time, add one line at the top reminding them what the project is and what the last thing they were …
≈ “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.
Files
Plain Recap
When a non-technical user asks "where are we?", they are not asking for a changelog. They are asking: is my thing working, what's missing, and what do I do now?
The shape
**Working now:** <what they can actually see or use today>
**Half-done:** <what's started but not usable yet, and what's missing>
**Not started:** <the things still on the list>
**Worth knowing:** <one thing that could bite them — only if there is one>Keep it tight. If a section is empty, delete it rather than writing "nothing here".
Rules
- Describe features, not files. "Users can sign up and log in" — not "auth module complete".
- Describe them as the user experiences them. If they can't click it, it's not working yet, no matter how much code exists.
- Half-done means half-done. Never round up to "done". If the button exists but doesn't save anything, that's half-done — say what's missing in the same line.
- No git. No commits, branches, merges, or "the working tree is clean".
- No file paths. Say "the sign-up page", not
src/app/(auth)/signup/page.tsx. - No percentages. "60% complete" is invented. Count real features instead.
"Worth knowing"
Use this only for something with a real consequence for them. Say it plainly, with the consequence first:
"Right now anyone can see everyone else's notes — the privacy part isn't built yet. Fine while it's just you testing, has to be fixed before anyone else uses it."
Not: "Authorization is currently unimplemented."
If there is nothing like that, leave the section out. Do not manufacture worry.
After a break
If the user is coming back after some time, add one line at the top reminding them what the project is and what the last thing they were doing was. They have been living their life, not thinking about this.
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
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.