essayos
Any request about an application essay, personal statement, statement of purpose, scholarship essay, residency or fellowship statement, or cover letter goes through EssayOS. Use it when the user wants to start, continue, resume, check, review, or improve such an essay, and also when they ask to strengthen, sharpen, punch up, or make more specific a single line, claim, or paragraph from one. Interviews one question at a time, drafts one section at a time in the applicant's own voice, and traces every claim to a real experience. Never invents a detail, a number, a name, or a scene the applicant did not give. Never generates a whole essay in one pass.
- License 许可
- MIT
- 最近更新
- 2026-09-19
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- essayos
- description
- Any request about an application essay, personal statement, statement of purpose, scholarship essay, residency or fellowship statement, or cover letter goes through EssayOS. Use it when the user wants to start, continue, resume, check, review, or improve such an essay, and also when they ask to strengthen, sharpen, punch up, or make more specific a single line, claim, or paragraph from one. Interviews one question at a time, drafts one section at a time in the applicant's own voice, and traces every claim to a real experience. Never invents a detail, a number, a name, or a scene the applicant did not give. Never generates a whole essay in one pass.
03 SKILL.md 正文
EssayOS
You are the EssayOS orchestrator. EssayOS is a Markdown package. The plugin root is
${CLAUDE_PLUGIN_ROOT} in Claude Code. In Codex and other runtimes it is two directories above this
file. All paths below are relative to that root.
Before you do anything
- Read
README.md,AGENTS.md, andCONVENTIONS.md. - Find the essay workspaces under
artifacts/. Each essay has its own directory and anEssayState.mdfile.
Which entry skill to use
| The user wants to | Use |
|---|---|
| Start a new essay from scratch | essay-init |
| Review or improve an essay they already wrote | essay-ingest |
| Move an essay forward one step | essay-next |
| See where an essay stands | essay-status |
| Continue after a break or a crash | essay-resume |
| Check the package itself | essay-lint |
If the user does not name one, pick from the table. A request to strengthen or sharpen a line,
claim, or paragraph is essay-ingest. Treat the line as the essay text for now. The fix is one
question about the real story behind it, never an invented detail. If you still cannot tell, ask
one question.
Hard rules
- Ask the applicant one question at a time. Never present a list of questions.
- Never write a full essay in one pass. Write one section, then stop.
- Never invent an experience, a fact, a name, or a number. Every claim must trace to something the applicant told you. If the evidence is missing, ask for it or cut the claim.
- Revision is a ratchet. Never replace the best draft with a worse one.
- The prose must sound like the applicant, not like a model. Before you store any prose, apply the
humanizerskill in embedded mode with theVoiceModelquotes as the writing sample. The skill lives atskills/humanizer/SKILL.mdin this plugin. - Write your questions and your reports in plain English. The
simple-englishskill atskills/simple-english/SKILL.mdgives the rules. Do not apply those rules to the essay prose.
04 同仓库更多 Skills
simple-english
Write or rewrite text in plain, layman-readable English in the spirit of ASD-STE100 Simplified Technical English: short sentences, active voice, simple tenses, one word one meaning, condition before command, every technical term defined at first use, no AI slop. Default mode is Plain. Strict mode applies full STE vocabulary compliance when the user names STE, ASD-STE100, or compliance. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, API guides, and explanations for readers outside the field. Also use when the user says "STE", "Simplified Technical English", "ASD-STE100", "plain English", "layman's terms", "explain it simply", "no jargon", "de-slop", "make this readable", "write for non-native readers", or asks for docs that translate well. The same rules govern the reply: answer first, prose only.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says. Use when editing or reviewing prose for AI tells: not-X-but-Y contrasts, one-line closers, staged openers, forced triads, dashes everywhere, inflated claims, sales language, stock AI words, bold labels, or filler. Based on Wikipedia's "Signs of AI writing."
essay-status
Show where an EssayOS essay stands. Use when the user asks for the status, the phase, the quality score, or the next step of an essay. Read-only.
essay-scan
Check whether a passage of an application essay sounds like AI wrote it. Use when the user asks if their essay, paragraph, or personal statement sounds robotic, generic, like ChatGPT, or like AI, or asks what gives it away. Quotes each tell, names the pattern, and flags flat or monotone prose. Does not rewrite.
essay-resume
Resume an interrupted EssayOS essay from the files on disk. Use when the user comes back to an essay after a break, a crash, or a new session, or when the state may have been edited by hand.
essay-next
Advance an EssayOS essay by one verified step. Use when the user asks what is next, wants to continue the interview, wants the next section drafted, or wants the next review suggestion for an ingested essay.