[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69ADXGVGRWMFFEMBVSM6TJW":3,"skill-same:01M69ADXGVGRWMFFEMBVSM6TJW":74},{"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":28,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M69ADXGVGRWMFFEMBVSM6TJW","wikipedia-human-style-writing",null,"Use this skill whenever the user asks to write, rewrite, humanise, de-AI, or polish prose so it doesn't read as AI-generated — or to review a draft for signs of AI writing. Apply it before returning any substantial prose the user will publish.","microsoft\u002Fcat-agent-skills","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69A1AHE1MABT7GVP5143M5Z",103,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fwikipedia-human-style-writing\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[29,30,31],"writing","wikipedia human style writing","review","2026-11-10 10:12:30",false,"---\nname: wikipedia-human-style-writing\ndescription: Use this skill whenever the user asks to write, rewrite, humanise, de-AI, or polish prose so it doesn't read as AI-generated — or to review a draft for signs of AI writing. Apply it before returning any substantial prose the user will publish.\n---\n\n# Wikipedia Human Style Writing\n\nWrite and revise prose so it does not carry the tell-tale signs of AI-generated\ntext, using the patterns catalogued in Wikipedia's\n[Signs of AI writing](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FWikipedia:Signs_of_AI_writing).\nThe full pattern catalogue lives in `references\u002Fai-writing-tells.md` — consult it\nwhenever you need the specific words-to-watch lists, examples, or the era-by-era\n\"AI vocabulary\" breakdown.\n\n## Operating principles\n\n1. **Signs, not sins.** Every pattern below can appear in good human writing. The\n   giveaway is **density and mechanical repetition**, not a single instance. Target\n   clusters, not isolated words.\n2. **Fix the cause, not the symptom.** Most tells are surface markers of a deeper\n   problem: vagueness, puffery, or unsupported claims. Restore the specific fact or\n   cut the empty claim — don't just swap the flagged word and leave hollow content.\n3. **Preserve the truth and the voice.** Never invent or drop facts, figures,\n   quotes, dates, or sources. Keep the author's meaning, stance, and legitimate\n   emphasis. Do not \"de-AI\" a draft into corporate blandness.\n4. **Descriptive, not prescriptive.** These words and shapes are overused, not\n   banned. Use judgment over find-and-replace.\n\n## Workflow\n\n1. Read the whole draft first; note the core message, key facts, and the intended\n   voice and audience.\n2. Sweep the draft against the tell categories in `references\u002Fai-writing-tells.md`,\n   looking for **clusters**.\n3. Revise each cluster by fixing the underlying issue:\n   - Replace generic praise with the specific, concrete fact\n     (regression-to-the-mean: \"a revolutionary titan of industry\" → the actual\n     achievement).\n   - Cut empty significance\u002Flegacy flourishes and trailing \"-ing\" analysis clauses.\n   - Restore plain `is\u002Fare\u002Fhas` in place of \"serves as \u002F stands as \u002F boasts \u002F\n     features\".\n   - Name a real source or delete a vague attribution (\"experts argue\", \"observers\n     have noted\").\n   - Break up mechanical rule-of-three lists, \"not just X but Y\" parallelisms, and\n     templated \"Challenges \u002F Future prospects\" wrap-ups.\n   - Remove promotional\u002Ftravel-brochure tone (\"vibrant\", \"nestled\", \"rich tapestry\",\n     \"seamless\").\n   - Thin out an over-dense cluster of era-specific \"AI vocabulary\" words.\n4. Clean the formatting tells: sentence-case headings (not Title Case), sparing\n   boldface (not `**bold lead-in:**` on every list item), varied punctuation instead\n   of space-surrounded em-dash overuse, no emoji-as-bullets, no stray markdown or\n   copy-pasted smart-quote residue, and no \"In conclusion \u002F In summary\" filler.\n5. Re-read against the original to confirm no meaning, fact, or nuance drifted.\n\n## Guardrails\n\n- Do not add, remove, or alter facts, numbers, quotes, or citations to make text\n  \"sound less AI\".\n- Do not strip emphasis or specificity that the source genuinely supports.\n- Do not flatten a distinctive human voice into neutral mush — the goal is natural,\n  specific, human prose, not blandness.\n- One or two flagged words are usually fine; don't over-correct isolated hits.\n\n## Output\n\nReturn the revised prose first, copy-ready. When a review was requested, or when\nuseful, follow it with a short bulleted list of the notable tells you found and how\nyou addressed them.\n\n## Reference\n\n- `references\u002Fai-writing-tells.md` — the full field guide: every tell category with\n  words-to-watch, examples, the era-by-era AI-vocabulary breakdown, and formatting\n  tells. Read the relevant section whenever you need detail beyond the summary above.\n","# Wikipedia Human Style Writing\n\nWrite and revise prose so it does not carry the tell-tale signs of AI-generated\ntext, using the patterns catalogued in Wikipedia's\n[Signs of AI writing](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FWikipedia:Signs_of_AI_writing).\nThe full pattern catalogue lives in `references\u002Fai-writing-tells.md` — consult it\nwhenever you need the specific words-to-watch lists, examples, or the era-by-era\n\"AI vocabulary\" breakdown.\n\n## Operating principles\n\n1. **Signs, not sins.** Every pattern below can appear in good human writing. The\n   giveaway is **density and mechanical repetition**, not a single instance. Target\n   clusters, not isolated words.\n2. **Fix the cause, not the symptom.** Most tells are surface markers of a deeper\n   problem: vagueness, puffery, or unsupported claims. Restore the specific fact or\n   cut the empty claim — don't just swap the flagged word and leave hollow content.\n3. **Preserve the truth and the voice.** Never invent or drop facts, figures,\n   quotes, dates, or sources. Keep the author's meaning, stance, and legitimate\n   emphasis. Do not \"de-AI\" a draft into corporate blandness.\n4. **Descriptive, not prescriptive.** These words and shapes are overused, not\n   banned. Use judgment over find-and-replace.\n\n## Workflow\n\n1. Read the whole draft first; note the core message, key facts, and the intended\n   voice and audience.\n2. Sweep the draft against the tell categories in `references\u002Fai-writing-tells.md`,\n   looking for **clusters**.\n3. Revise each cluster by fixing the underlying issue:\n   - Replace generic praise with the specific, concrete fact\n     (regression-to-the-mean: \"a revolutionary titan of industry\" → the actual\n     achievement).\n   - Cut empty significance\u002Flegacy flourishes and trailing \"-ing\" analysis clauses.\n   - Restore plain `is\u002Fare\u002Fhas` in place of \"serves as \u002F stands as \u002F boasts \u002F\n     features\".\n   - Name a real source or delete a vague attribution (\"experts argue\", \"observers\n     have noted\").\n   - Break up mechanical rule-of-three lists, \"not just X but Y\" parallelisms, and\n     templated \"Challenges \u002F Future prospects\" wrap-ups.\n   - Remove promotional\u002Ftravel-brochure tone (\"vibrant\", \"nestled\", \"rich tapestry\",\n     \"seamless\").\n   - Thin out an over-dense cluster of era-specific \"AI vocabulary\" words.\n4. Clean the formatting tells: sentence-case headings (not Title Case), sparing\n   boldface (not `**bold lead-in:**` on every list item), varied punctuation instead\n   of space-surrounded em-dash overuse, no emoji-as-bullets, no stray markdown or\n   copy-pasted smart-quote residue, and no \"In conclusion \u002F In summary\" filler.\n5. Re-read against the original to confirm no meaning, fact, or nuance drifted.\n\n## Guardrails\n\n- Do not add, remove, or alter facts, numbers, quotes, or citations to make text\n  \"sound less AI\".\n- Do not strip emphasis or specificity that the source genuinely supports.\n- Do not flatten a distinctive human voice into neutral mush — the goal is natural,\n  specific, human prose, not blandness.\n- One or two flagged words are usually fine; don't over-correct isolated hits.\n\n## Output\n\nReturn the revised prose first, copy-ready. When a review was requested, or when\nuseful, follow it with a short bulleted list of the notable tells you found and how\nyou addressed them.\n\n## Reference\n\n- `references\u002Fai-writing-tells.md` — the full field guide: every tell category with\n  words-to-watch, examples, the era-by-era AI-vocabulary breakdown, and formatting\n  tells. Read the relevant section whenever you need detail beyond the summary above.\n",{"name":5,"description":7},"main","3678d23ad8fb8d098c428302a98044ac9514d5a1","submissions\u002Fwikipedia-human-style-writing",119,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-12 02:57:14",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add microsoft\u002Fcat-agent-skills --skill wikipedia-human-style-writing",{"tool":52,"command":53},"bunx","bunx skills add microsoft\u002Fcat-agent-skills --skill wikipedia-human-style-writing",{"tool":55,"command":56},"pnpm","pnpm dlx skills add microsoft\u002Fcat-agent-skills --skill wikipedia-human-style-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fwikipedia-human-style-writing\u002FSKILL.md",true,[60,66,70],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"metadata.json","REFERENCE","参考文档",494,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fwikipedia-human-style-writing\u002Fmetadata.json",{"path":67,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":68,"sourceHtmlUrl":69},"README.md",1321,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fwikipedia-human-style-writing\u002FREADME.md",{"path":71,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fai-writing-tells.md",8309,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fwikipedia-human-style-writing\u002Freferences\u002Fai-writing-tells.md",[75,102,127,160,178,194],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":32},"01M6X3P09R8SJH3QJGMTAA5N90","stakeholder-and-decision-map","Mines customer interactions to identify stakeholders, infer their likely roles and engagement, map the decision process, and highlight who or what may be missing. Use when asked to \"map a deal's buying group\", identify influential or missing stakeholders, \"assess who has gone quiet\", or \"explain how the customer will decide\". Do not use for phased engagement plans, contact sequences, choosing or drafting outreach to the single next contact, seller or team performance reviews, or contacting, scheduling, or changing records.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fstakeholder-and-decision-map\u002FSKILL.md",[],[82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101],"decision","map","decision map","stakeholder and decision map","performance","customer","team","how","decide","do","next","infer","missing","records","assess","reviews","for","single","when","sequences",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":32},"01M6X3NRES2XSZQCH015WD4JN6","sales-progress-update","Creates or refreshes a sales progress update for a manager or team about work done, deal movement, pending outcomes, supported forecast position, and help needed. Use when asked to \"create my weekly sales update\", \"refresh my sales progress deck\", \"report my forecast position\", \"where do I stand against my quarter forecast\", or \"catch my manager up on committed deals\". Do NOT use for non-sales project updates, a since-date deal change digest, momentum or blocker analysis, meeting prep, or outreach drafting.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fsales-progress-update\u002FSKILL.md",[],[109,110,111,112,113,114,115,116,88,117,118,119,120,121,122,123,124,125,126,100],"update","sales","progress","sales progress update","change","create","meeting prep","analysis","work","up","done","digest","project","my","updates","manager","weekly","catch",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":142,"publishedAt":32},"01M6X3MSDTB1E5H6DQAFAY41YP","submission-assemble","Put the checked CSR or 510(k) sections together in template order with a reviewer-facing open-items register, as a draft package for human sign-off. Use when the user asks \"assemble the CSR draft\", \"put the module together for review\", \"build the review package with the open items on top\", \"compile the 510(k) sections in order\" or \"package this up for the submission lead\". Do NOT use for assembling an unchecked draft - use consistency-check instead. Do NOT use for loading protocol, SAP or TLF sources - use source-ingest instead. Do NOT use for compiling general documents or slide decks - use the built-in docx or pptx skill instead. Do NOT use for filing or submitting to a regulator - use the sponsor's validated gateway, operated by a human, instead. Guardrail: draft for human approval only (L1); status is draft_clean or draft_open_items, never submitted.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Freg-submission-authoring\u002Fsubmission-assemble\u002FSKILL.md",[133,136,139],{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":137,"categoryName":138,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":140,"categoryName":141,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000034","行政与办公人员",[143,144,145,146,147,29,148,149,150,151,152,153,118,154,155,156,157,158,159,100],"assemble","submission","submission assemble","docx","pptx","documents","healthcare","open","reviewer","never","only","clean","guardrail","slide decks","sources","filing","loading",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":32},"01M6X3MM9TVWDQ716QGNV4DS25","source-ingest","Pull every number, date and population definition out of a study's protocol, SAP, TLF tables, investigator brochure and prior approved text into one cited fact map, keyed per config\u002Ffield-dictionary.json, before any CSR or 510(k) section is written. Use when the user asks \"here's the locked TLF set and SAP, set up the CSR\", \"load the protocol and tables before we start drafting\", \"what figures do we have from the database lock?\", \"pull the disposition counts out of Table 14.1.1\" or \"ingest the IB for the 510(k)\". Do NOT use for drafting or assembling submission sections - use section-draft or submission-assemble instead. Do NOT use for reconciling a patient's medications - use the discharge-care-transition plugin instead. Guardrail: reads and cites sources only; never estimates, rounds or invents a fact.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Freg-submission-authoring\u002Fsource-ingest\u002FSKILL.md",[],[167,168,169,170,171,116,149,172,152,153,118,83,173,155,157,174,175,176,177,100],"source ingest","ingest","source","database","SET","text","patient","number","lock","definition","transition",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":185,"publishedAt":32},"01M6X3M7ZH5ZNEHP56BQ74HAJR","section-plan","Work out which sections a CSR or 510(k) requires, from the templates in config, check each one against the cited fact map, and name what is missing before a word is drafted. Use when the user asks \"what do we still need before we can draft the CSR?\", \"which sections are ready to start?\", \"what's blocking the performance data section?\", \"do we have everything for the synopsis?\" or \"map our tables to the E3 structure\". Do NOT use for writing section language - use section-draft instead. Do NOT use for cross-checking a finished draft - use consistency-check instead. Do NOT use for outlining general Word documents or business reports - use the built-in docx skill instead. Only structures with a template in config are supported. Guardrail: plans only; never marks a section ready on a missing fact and never invents a structure.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Freg-submission-authoring\u002Fsection-plan\u002FSKILL.md",[184],{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},[186,187,188,146,29,86,148,116,149,117,152,153,189,190,191,83,155,192,193,100],"plan","section","section plan","ready","reports","structure","word documents","which",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":200,"publishedAt":32},"01M6X3M0V1MJNCR653ES9XGVMS","section-draft","Write or revise the language for one planned CSR or 510(k) section - synopsis, efficacy, safety, discussion, device description - using only figures already in the cited fact map, each with its TLF or SAP citation. Use when the user asks \"draft the Synopsis from our locked tables\", \"write up safety from Table 14.3.1\", \"give me a first pass at the discussion\", \"draft the device description for the 510(k)\" or \"tighten the wording of the Discussion section\". Do NOT use for supplying a number not already in source_facts - use source-ingest instead. Do NOT use for verifying a draft's figures - use consistency-check instead. Do NOT use for appeal letters, clinical notes or discharge summaries - use the matching HLS plugin instead. Guardrail: drafts for human approval only (L1); never asserts an unsourced number or harmonises two figures.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Freg-submission-authoring\u002Fsection-draft\u002FSKILL.md",[],[201,187,202,29,203,149,204,152,153,118,205,83,206,207,208,155,209,174,210,100],"draft","section draft","notes","write","me","human","life","clinical","drafts","at"]