dhruvaldarji/essayos
An idempotent, stateful, agentic operating system for writing application essays. It interviews you, drafts one section at a time in your voice, reviews an essay you already wrote, and checks that every claim traces to a real experience.
Review or improve an essay the user already wrote. Use when the user pastes, attaches, or points to an existing application essay, personal statement, statement of purpose, or scholarship essay and asks for a review, feedback, or revisions, or asks to make it (or one line, claim, or paragraph of it) stronger, more specific, more personal, less generic, or less like AI. Stores the text as given, grounds every claim in a real experience by asking, and proposes changes the user approves one at a time. Never invents details.
Start a new EssayOS essay workspace. Use when the user wants to begin a new application essay, personal statement, statement of purpose, scholarship essay, or cover letter from scratch.
Self-test the EssayOS package. Use when the user asks to lint, validate, or check the EssayOS package, its skills, its schemas, or its plugin manifests.
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.
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.
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.
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.
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.
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."
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.