reader-pov
Skill0 starsChanged 35 days agoMITView on GitHub
Read a finished application packet as the human who actually receives it, not as a rules checker. Use for /reader, and before any final submission.
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- application-typesSkill
- application-writingSkill
- honesty-guardSkill
- interviewing-youSkill
- mock-interviewSkill
- no-slop-writingSkill
- org-researchSkill
- unasked-questionsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Run it on the whole packet at once, not one answer at a time.
- Very specific: line 16
Read the packet three times, once as each.
- Distinctive: line 50
The same shape four times: Read every "why us" answer in a row.
- Distinctive: line 67
Density of one theme: If one subject appears in five of ten answers, that is a texture observation, not automatically a problem.
- Distinctive: line 91
If a piece of the finding survives for a different reason, keep that piece and say plainly which part you are withdrawing and why.
≈ “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
Reading as the reader
This is not a rules check. A rules check tells you the answer is 12 words over and contains a banned phrase. This tells you what a person will notice, feel, and decide.
Run it on the whole packet at once, not one answer at a time. Most of what this catches only exists across answers.
The three people
Read the packet three times, once as each. Who these three are depends on the type,
so load application-types and read the matching reference/ file first. The roles
below hold across types even though the people change.
The filter. Whoever decides you are worth more than a minute. A sophomore officer at 11pm with 200 left. A recruiter scanning against a requisition. A program officer checking eligibility before anything else.
Report: which answer would make them stop, where their attention drops, whether the first sentence of each answer earned the second, and whether anything made them uneasy in a way they could not articulate.
The specialist doing diligence. The person who actually knows the domain and will interview you if you pass. The officer who ran the project you mentioned. The hiring manager. The faculty member whose lab you named. They read for whether the claims hold.
Report: every number they would ask "how did you get that," every claim that reads bigger than it probably is, every place where the same fact appears differently in two answers or between an answer and the resume.
The person who has to live with the decision. Deciding whether they want to be assigned to a project with you for fifteen weeks, manage you for two years, advise you for five, or defend the grant when it is audited.
Report: do you sound like a person or a candidate, is there one moment of actual warmth or humor, does anything read as someone who cannot be told they are wrong, and would they be glad or tired to see your name.
That third reader is weighted differently by type. For student-org and grad-school
it is close to decisive, because the reader is choosing a person they will actually work
beside. For grant it is the weakest of the three, because they are funding a plan.
What to look for that a rules check misses
The same shape four times. Read every "why us" answer in a row. If they all run "here is what I built, here is what I lack, teach me," the reader notices the pattern even if each one is good. Vary at least one.
Weight with nowhere to land. A hard subject raised inside a word limit too small to resolve it. The reader gets the weight and none of the resolution, and closes the tab uneasy. This is a container problem, not a subject problem: same story, bigger question, works fine.
The unexplained hook. "After the year I just had." Points at something the reader does not know, and a stranger reads it as a warning rather than as depth. Say the thing or drop the reference.
Tonal whiplash. A joke immediately after something heavy. The fun questions come after the serious ones on most forms, and the reader's shoulders have just come down. Notice where the room changes.
Density of one theme. If one subject appears in five of ten answers, that is a texture observation, not automatically a problem. Reusing your strongest material across different orgs is what every applicant does and what orgs expect. Say what you noticed, give a read, and let the applicant decide. Do not argue that a reader going through 200 applications is cross-referencing one person, because they are not.
Answers that are too short. Anything under 60 percent of the limit next to answers at 95 percent reads as declining interest by the end of the form.
How to write the report
Numbered findings, most consequential first. For each:
- What the reader notices, in their words.
- Which answer, quoted.
- Whether you would change it, and your actual recommendation. Not "consider whether."
End with the one change that would most improve the packet, and be specific about which answer and what to do.
When they push back
They know their life. If they say a finding is wrong, they are usually right, and the right response is to withdraw the argument in writing rather than restate it softer. If a piece of the finding survives for a different reason, keep that piece and say plainly which part you are withdrawing and why.
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.

