[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71SWS4QFMMTR9P5GS9N0582":3,"skill-same:01M71SWS4QFMMTR9P5GS9N0582":55},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":14,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":40,"install":41,"resources":54},"01M71SWS4QFMMTR9P5GS9N0582","cleanup-editor",null,"Self-edit a draft for clarity, contradictions, answerable open questions. Use after initial draft.","rnortman\u002Fclaude-plugins","rnortman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6696883?v=4","01M71SWK8WWGC18QBBAZXEE58G","Randall Nortman","01M71SWK9MR2T328ZWX1BETDZV",0,"MIT","https:\u002F\u002Fgithub.com\u002Frnortman\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freview-chain\u002Fskills\u002Fcleanup-editor\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"editor","cleanup","cleanup editor","open","clarity","edit","use","self","draft","questions","for","2026-11-10 13:02:02",false,"---\nname: cleanup-editor\ndescription: Self-edit a draft for clarity, contradictions, answerable open questions. Use after initial draft.\n---\n\nJust wrote a draft? Run yourself through this pass before handing off. Goal: clean linear story — final claims direct, contradictions resolved, open questions either answered or genuinely user-judgment.\n\nEdit the draft in place.\n\n## Find + fix\n\n### Thought-process prose\n\nDoc narrates your deliberation (\"I considered X, then realized Y, but then thought about Z and decided…\") instead of stating the final plan. Rewrite as \"here is what we will do.\" Reader doesn't need the path.\n\n### \"But wait\" \u002F \"actually\" reversals\n\nMid-prose stream-of-consciousness reversals where you discover your error and correct mid-paragraph. Drop the wrong half, keep the correct claim. Correct answer not obvious from surrounding text → contradiction (next item) — investigate, don't just delete.\n\n### Contradictions between sections\n\nSection A says X; section B says ¬X. Find the truth (re-read code\u002Fspec\u002Fprior section). Rewrite both to agree. Don't paper over by hedging both — pick the right answer.\n\n### Open questions you can answer\n\nDraft poses a question that investigation would resolve — read a file, grep, check schema, look up an API. Investigate, answer, update doc. Final draft's open questions = **genuine user-judgment calls only** (taste, prioritization, \"what does the user want?\"). Anything answerable through investigation is your job.\n\n### Approval requests masquerading as open questions\n\nCut on sight, every time: \"confirm this direction\", \"approve X before proceeding\", \"the spec reserved this call so the user confirms here\", \"sign off that the earlier answer still holds\", or anything else whose only answers are \"yes, go ahead\" and \"no, change it\". The doc already goes to a user gate — approval is the workflow, not a question, and asking for it burns the user's attention on a decision they were about to make anyway. If the reasoning eliminated every alternative, the author *made* the call: promote it to a stated decision with the reasoning that forced it, and delete the question. Also delete notes that merely observe an already-answered question stays answered. Pruning empties the section → remove the section.\n\n### Terminology drift\n\nSame concept named two ways. Pick one, normalize. Can't tell if they mean the same thing → contradiction → investigate.\n\n### Promised but missing sections\n\nOutline \u002F earlier section promises something the doc doesn't deliver (\"we'll cover X below…\" with no X). Either write the content or remove the promise.\n\n### Speculative \u002F unverified claims\n\n\"I think this should…\", \"probably this means…\". Matters? Verify. Doesn't matter? Cut.\n\n### Filler\n\nThroat-clearing intros, restated context the reader already has, \"as mentioned above\" cross-references earning nothing. Cut.\n\n## Preserve\n\n- All substantive technical content. Don't trim detail to shorten — only trim process narration, redundancy, filler.\n- Genuine user-judgment open questions.\n- Any \"Human-review delta\" block explaining what changed since user last read.\n- Domain terminology + your authorial voice on substance.\n\n## Operate\n\n1. Re-read draft top to bottom.\n2. Per issue: prose (rewrite in place) or substance (investigate + resolve)?\n3. Do prose edits.\n4. Do substance work — read what you need, update with the answer.\n5. Done: no thought-process prose, no contradictions, no answerable open questions, no promised-but-missing sections.\n\nYou're not creating a separate cleanup report. Improve your own draft directly.\n","Just wrote a draft? Run yourself through this pass before handing off. Goal: clean linear story — final claims direct, contradictions resolved, open questions either answered or genuinely user-judgment.\n\nEdit the draft in place.\n\n## Find + fix\n\n### Thought-process prose\n\nDoc narrates your deliberation (\"I considered X, then realized Y, but then thought about Z and decided…\") instead of stating the final plan. Rewrite as \"here is what we will do.\" Reader doesn't need the path.\n\n### \"But wait\" \u002F \"actually\" reversals\n\nMid-prose stream-of-consciousness reversals where you discover your error and correct mid-paragraph. Drop the wrong half, keep the correct claim. Correct answer not obvious from surrounding text → contradiction (next item) — investigate, don't just delete.\n\n### Contradictions between sections\n\nSection A says X; section B says ¬X. Find the truth (re-read code\u002Fspec\u002Fprior section). Rewrite both to agree. Don't paper over by hedging both — pick the right answer.\n\n### Open questions you can answer\n\nDraft poses a question that investigation would resolve — read a file, grep, check schema, look up an API. Investigate, answer, update doc. Final draft's open questions = **genuine user-judgment calls only** (taste, prioritization, \"what does the user want?\"). Anything answerable through investigation is your job.\n\n### Approval requests masquerading as open questions\n\nCut on sight, every time: \"confirm this direction\", \"approve X before proceeding\", \"the spec reserved this call so the user confirms here\", \"sign off that the earlier answer still holds\", or anything else whose only answers are \"yes, go ahead\" and \"no, change it\". The doc already goes to a user gate — approval is the workflow, not a question, and asking for it burns the user's attention on a decision they were about to make anyway. If the reasoning eliminated every alternative, the author *made* the call: promote it to a stated decision with the reasoning that forced it, and delete the question. Also delete notes that merely observe an already-answered question stays answered. Pruning empties the section → remove the section.\n\n### Terminology drift\n\nSame concept named two ways. Pick one, normalize. Can't tell if they mean the same thing → contradiction → investigate.\n\n### Promised but missing sections\n\nOutline \u002F earlier section promises something the doc doesn't deliver (\"we'll cover X below…\" with no X). Either write the content or remove the promise.\n\n### Speculative \u002F unverified claims\n\n\"I think this should…\", \"probably this means…\". Matters? Verify. Doesn't matter? Cut.\n\n### Filler\n\nThroat-clearing intros, restated context the reader already has, \"as mentioned above\" cross-references earning nothing. Cut.\n\n## Preserve\n\n- All substantive technical content. Don't trim detail to shorten — only trim process narration, redundancy, filler.\n- Genuine user-judgment open questions.\n- Any \"Human-review delta\" block explaining what changed since user last read.\n- Domain terminology + your authorial voice on substance.\n\n## Operate\n\n1. Re-read draft top to bottom.\n2. Per issue: prose (rewrite in place) or substance (investigate + resolve)?\n3. Do prose edits.\n4. Do substance work — read what you need, update with the answer.\n5. Done: no thought-process prose, no contradictions, no answerable open questions, no promised-but-missing sections.\n\nYou're not creating a separate cleanup report. Improve your own draft directly.\n",{"name":5,"description":7},"main","8af8a1248b8b0aabe0e7f836de08d844b5fd6d0f","plugins\u002Freview-chain\u002Fskills\u002Fcleanup-editor","https:\u002F\u002Fgithub.com\u002Frnortman\u002Fclaude-plugins","https:\u002F\u002Fgithub.com\u002Frnortman","2026-09-16 18:21:03",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add rnortman\u002Fclaude-plugins --skill cleanup-editor",{"tool":47,"command":48},"bunx","bunx skills add rnortman\u002Fclaude-plugins --skill cleanup-editor",{"tool":50,"command":51},"pnpm","pnpm dlx skills add rnortman\u002Fclaude-plugins --skill cleanup-editor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frnortman\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freview-chain\u002Fskills\u002Fcleanup-editor\u002FSKILL.md",true,[],[56,87,107,117,130,150],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":67,"publishedAt":30},"01M71SX1ZBSPB9CEM1ANWJAMGW","setup-project","Bootstrap a project for the review-chain workflow — set the orchestrator as default agent, add a \"Working With Claude Code\" section to CLAUDE.md, install the TODO.md + TODO(slug) tracking convention, and optionally wire an auto-format hook. Take it or leave it; the review-chain agents work without any of this.","https:\u002F\u002Fgithub.com\u002Frnortman\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsetup-project\u002Fskills\u002Fsetup-project\u002FSKILL.md",[62],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,29,83,84,85,86],"setup","project","setup project","format","orchestrator","work","todo","code","with","review","bootstrap","SET","working with claude code","as","chain","section","default","auto","workflow",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":30},"01M71SWZYBZRDX66X7RTFJNHZV","usage-wall","Ride the 5-hour usage window into the wall — schedule a post-reset wakeup, then resume stalled subagents. No watchdog, no throttling.","https:\u002F\u002Fgithub.com\u002Frnortman\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freview-chain\u002Fskills\u002Fusage-wall\u002FSKILL.md",[],[94,95,96,97,98,99,100,101,102,103,104,105,106],"usage wall","wall","usage","ride","resume","watchdog","true","post","window","throttling","schedule","reset","subagents",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":30},"01M71SWYXV00J8K4GX6MZH3ABA","usage-guard","Arm a background watchdog on the account's 5-hour usage window","https:\u002F\u002Fgithub.com\u002Frnortman\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freview-chain\u002Fskills\u002Fusage-guard\u002FSKILL.md",[],[114,115,96,100,116,99,102],"guard","usage guard","background",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":30},"01M71SWX43FHC2G18TRSEC2EHN","simplify","Review changed code for reuse, quality, efficiency; fix issues found.","https:\u002F\u002Fgithub.com\u002Frnortman\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freview-chain\u002Fskills\u002Fsimplify\u002FSKILL.md",[],[119,124,125,29,75,126,77,127,128,129],"fix issues","reuse","quality","efficiency","fix","issues",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":30},"01M71SWTWTABSQVE4NFYWKWF8J","configure-models","Generate or edit local per-agent model overrides for review-chain agents (.claude\u002Freview-chain-models.conf) — re-pin a model without editing agent files or publishing.","https:\u002F\u002Fgithub.com\u002Frnortman\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freview-chain\u002Fskills\u002Fconfigure-models\u002FSKILL.md",[],[137,138,139,140,141,82,142,143,29,144,145,24,146,147,148,149,77],"models","configure models","configure","files","overrides","generate","model","editing","re","local","publishing","pin","conf",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":30},"01M71SWQSBCWKN9CR6GE4KZW6M","clarify","Restate your most recent response more clearly and concisely","https:\u002F\u002Fgithub.com\u002Frnortman\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freview-chain\u002Fskills\u002Fclarify\u002FSKILL.md",[],[152,100,157,158,159],"concisely","more","restate"]