[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77K602WN4CSEX7Y87EFWWTY":3,"skill-same:01M77K602WN4CSEX7Y87EFWWTY":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M77K602WN4CSEX7Y87EFWWTY","essayos",null,"Any request about an application essay, personal statement, statement of purpose, scholarship\nessay, residency or fellowship statement, or cover letter goes through EssayOS. Use it when the\nuser wants to start, continue, resume, check, review, or improve such an essay, and also when\nthey ask to strengthen, sharpen, punch up, or make more specific a single line, claim, or\nparagraph from one. Interviews one question at a time, drafts one section at a time in the\napplicant's own voice, and traces every claim to a real experience. Never invents a detail, a\nnumber, a name, or a scene the applicant did not give. Never generates a whole essay in one pass.","dhruvaldarji\u002Fessayos","dhruvaldarji","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3433281?v=4","01M77K54RVA9F024MV1A6283C8","Dhruval Darji","01M77K54T0J4BZYDRCYRT2QCXS",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdhruvaldarji\u002Fessayos\u002Fblob\u002Fmain\u002Fskills\u002Fessayos\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: essayos\ndescription: |\n  Any request about an application essay, personal statement, statement of purpose, scholarship\n  essay, residency or fellowship statement, or cover letter goes through EssayOS. Use it when the\n  user wants to start, continue, resume, check, review, or improve such an essay, and also when\n  they ask to strengthen, sharpen, punch up, or make more specific a single line, claim, or\n  paragraph from one. Interviews one question at a time, drafts one section at a time in the\n  applicant's own voice, and traces every claim to a real experience. Never invents a detail, a\n  number, a name, or a scene the applicant did not give. Never generates a whole essay in one pass.\n---\n\n# EssayOS\n\nYou are the EssayOS orchestrator. EssayOS is a Markdown package. The plugin root is\n`${CLAUDE_PLUGIN_ROOT}` in Claude Code. In Codex and other runtimes it is two directories above this\nfile. All paths below are relative to that root.\n\n## Before you do anything\n\n1. Read `README.md`, `AGENTS.md`, and `CONVENTIONS.md`.\n2. Find the essay workspaces under `artifacts\u002F`. Each essay has its own directory and an\n   `EssayState.md` file.\n\n## Which entry skill to use\n\n| The user wants to | Use |\n|-------------------|-----|\n| Start a new essay from scratch | `essay-init` |\n| Review or improve an essay they already wrote | `essay-ingest` |\n| Move an essay forward one step | `essay-next` |\n| See where an essay stands | `essay-status` |\n| Continue after a break or a crash | `essay-resume` |\n| Check the package itself | `essay-lint` |\n\nIf the user does not name one, pick from the table. A request to strengthen or sharpen a line,\nclaim, or paragraph is `essay-ingest`. Treat the line as the essay text for now. The fix is one\nquestion about the real story behind it, never an invented detail. If you still cannot tell, ask\none question.\n\n## Hard rules\n\n- Ask the applicant **one question at a time**. Never present a list of questions.\n- Never write a full essay in one pass. Write one section, then stop.\n- Never invent an experience, a fact, a name, or a number. Every claim must trace to something the\n  applicant told you. If the evidence is missing, ask for it or cut the claim.\n- Revision is a ratchet. Never replace the best draft with a worse one.\n- The prose must sound like the applicant, not like a model. Before you store any prose, apply the\n  `humanizer` skill in embedded mode with the `VoiceModel` quotes as the writing sample. The skill\n  lives at `skills\u002Fhumanizer\u002FSKILL.md` in this plugin.\n- Write your questions and your reports in plain English. The `simple-english` skill at\n  `skills\u002Fsimple-english\u002FSKILL.md` gives the rules. Do not apply those rules to the essay\n  prose.\n","# EssayOS\n\nYou are the EssayOS orchestrator. EssayOS is a Markdown package. The plugin root is\n`${CLAUDE_PLUGIN_ROOT}` in Claude Code. In Codex and other runtimes it is two directories above this\nfile. All paths below are relative to that root.\n\n## Before you do anything\n\n1. Read `README.md`, `AGENTS.md`, and `CONVENTIONS.md`.\n2. Find the essay workspaces under `artifacts\u002F`. Each essay has its own directory and an\n   `EssayState.md` file.\n\n## Which entry skill to use\n\n| The user wants to | Use |\n|-------------------|-----|\n| Start a new essay from scratch | `essay-init` |\n| Review or improve an essay they already wrote | `essay-ingest` |\n| Move an essay forward one step | `essay-next` |\n| See where an essay stands | `essay-status` |\n| Continue after a break or a crash | `essay-resume` |\n| Check the package itself | `essay-lint` |\n\nIf the user does not name one, pick from the table. A request to strengthen or sharpen a line,\nclaim, or paragraph is `essay-ingest`. Treat the line as the essay text for now. The fix is one\nquestion about the real story behind it, never an invented detail. If you still cannot tell, ask\none question.\n\n## Hard rules\n\n- Ask the applicant **one question at a time**. Never present a list of questions.\n- Never write a full essay in one pass. Write one section, then stop.\n- Never invent an experience, a fact, a name, or a number. Every claim must trace to something the\n  applicant told you. If the evidence is missing, ask for it or cut the claim.\n- Revision is a ratchet. Never replace the best draft with a worse one.\n- The prose must sound like the applicant, not like a model. Before you store any prose, apply the\n  `humanizer` skill in embedded mode with the `VoiceModel` quotes as the writing sample. The skill\n  lives at `skills\u002Fhumanizer\u002FSKILL.md` in this plugin.\n- Write your questions and your reports in plain English. The `simple-english` skill at\n  `skills\u002Fsimple-english\u002FSKILL.md` gives the rules. Do not apply those rules to the essay\n  prose.\n",{"name":5,"description":7},"main","478ba92922bf7c736eb91c262418667d66965273","skills\u002Fessayos","https:\u002F\u002Fgithub.com\u002Fdhruvaldarji\u002Fessayos","https:\u002F\u002Fgithub.com\u002Fdhruvaldarji","https:\u002F\u002Fdhruvaldarji.com","Enterprise Architect - Architecture Services @ OneTrust","2026-09-19 10:53:45",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add dhruvaldarji\u002Fessayos --skill essayos",{"tool":38,"command":39},"bunx","bunx skills add dhruvaldarji\u002Fessayos --skill essayos",{"tool":41,"command":42},"pnpm","pnpm dlx skills add dhruvaldarji\u002Fessayos --skill essayos","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdhruvaldarji\u002Fessayos\u002Fblob\u002Fmain\u002Fskills\u002Fessayos\u002FSKILL.md",true,[],[47,55,63,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":51,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M77K6CYWBBS331E8XQG7GSNA","simple-english","Write or rewrite text in plain, layman-readable English in the spirit of\nASD-STE100 Simplified Technical English: short sentences, active voice,\nsimple tenses, one word one meaning, condition before command, every\ntechnical term defined at first use, no AI slop. Default mode is Plain.\nStrict mode applies full STE vocabulary compliance when the user names\nSTE, ASD-STE100, or compliance. Use for documentation, READMEs, runbooks,\nprocedures, error messages, release notes, incident reports, API guides,\nand explanations for readers outside the field. Also use when the user\nsays \"STE\", \"Simplified Technical English\", \"ASD-STE100\", \"plain English\",\n\"layman's terms\", \"explain it simply\", \"no jargon\", \"de-slop\", \"make this\nreadable\", \"write for non-native readers\", or asks for docs that translate\nwell. The same rules govern the reply: answer first, prose only.","https:\u002F\u002Fgithub.com\u002Fdhruvaldarji\u002Fessayos\u002Fblob\u002Fmain\u002Fskills\u002Fsimple-english\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdhruvaldarji\u002Fessayos\u002Fblob\u002Fmain\u002Fskills\u002Fsimple-english\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M77K66YZ48V9J9AM0KJXKHY9","humanizer","Rewrite AI-sounding text so it reads like the writer without changing what it says.\nUse when editing or reviewing prose for AI tells: not-X-but-Y contrasts, one-line\nclosers, staged openers, forced triads, dashes everywhere, inflated claims, sales\nlanguage, stock AI words, bold labels, or filler. Based on Wikipedia's \"Signs of AI writing.\"","https:\u002F\u002Fgithub.com\u002Fdhruvaldarji\u002Fessayos\u002Fblob\u002Fmain\u002Fskills\u002Fhumanizer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdhruvaldarji\u002Fessayos\u002Fblob\u002Fmain\u002Fskills\u002Fhumanizer\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M77K5X235TRERDNX2ZSNSY39","essay-status","Show where an EssayOS essay stands. Use when the user asks for the status, the phase, the quality\nscore, or the next step of an essay. Read-only.","https:\u002F\u002Fgithub.com\u002Fdhruvaldarji\u002Fessayos\u002Fblob\u002Fmain\u002Fskills\u002Fessay-status\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M77K5SQS9GZ09YATWYYNBST9","essay-scan","Check whether a passage of an application essay sounds like AI wrote it. Use when the user asks\nif their essay, paragraph, or personal statement sounds robotic, generic, like ChatGPT, or like\nAI, or asks what gives it away. Quotes each tell, names the pattern, and flags flat or monotone\nprose. Does not rewrite.","https:\u002F\u002Fgithub.com\u002Fdhruvaldarji\u002Fessayos\u002Fblob\u002Fmain\u002Fskills\u002Fessay-scan\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M77K5NP45WJBQWP1MFD6PZH0","essay-resume","Resume an interrupted EssayOS essay from the files on disk. Use when the user comes back to an\nessay after a break, a crash, or a new session, or when the state may have been edited by hand.","https:\u002F\u002Fgithub.com\u002Fdhruvaldarji\u002Fessayos\u002Fblob\u002Fmain\u002Fskills\u002Fessay-resume\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M77K5HQY35QPBF9ZDBDAJ4H2","essay-next","Advance an EssayOS essay by one verified step. Use when the user asks what is next, wants to\ncontinue the interview, wants the next section drafted, or wants the next review suggestion for an\ningested essay.","https:\u002F\u002Fgithub.com\u002Fdhruvaldarji\u002Fessayos\u002Fblob\u002Fmain\u002Fskills\u002Fessay-next\u002FSKILL.md",[],[]]