[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6X714CMT7GTQDV4YAYFPVVT":3,"skill-same:01M6X714CMT7GTQDV4YAYFPVVT":88},{"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":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":66,"commitSha":67,"skillDirectory":68,"forksCount":69,"repositoryHtmlUrl":70,"repositoryHomepageUrl":6,"ownerHtmlUrl":71,"ownerBlogUrl":72,"ownerDescription":73,"updatedAt":74,"install":75,"resources":87},"01M6X714CMT7GTQDV4YAYFPVVT","anti-ai-writing",null,"Detect and eliminate signs of AI-generated writing. Use when producing any user-facing text — blog posts, landing pages, docs, emails, social media, README, marketing copy. Enforces human-quality prose by flagging Wikipedia's documented AI writing tells.","Cheggin\u002Frequest-for-startups","Cheggin","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F79483996?v=4","01M6X6MGT5512GJHE8DY5B1ZQJ","Reagan Hsu","01M6X6MGY03X7ZJNVRFM3R1040",1,"GPL-3.0","https:\u002F\u002Fgithub.com\u002FCheggin\u002Frequest-for-startups\u002Fblob\u002Fmain\u002Fskills\u002Fanti-ai-writing\u002FSKILL.md",[18,23,26,31],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"anti ai writing","writing","social","when","true","posts","wikipedia","detect","pages","emails","human","use","landing","generated","README","social media","quality","text","blog","Media","2026-11-10 10:12:30",false,"---\nname: anti-ai-writing\ndescription: Detect and eliminate signs of AI-generated writing. Use when producing any user-facing text — blog posts, landing pages, docs, emails, social media, README, marketing copy. Enforces human-quality prose by flagging Wikipedia's documented AI writing tells.\nuser-invocable: true\ngroup: comms\nprerequisites: []\nnext: []\nworkflows: [all]\nalways-load: true\n---\n\n# Anti-AI Writing\n\nEvery piece of text this harness produces must read like a human wrote it. AI-generated writing has documented tells. This skill flags and fixes them.\n\nSource: Wikipedia's \"Signs of AI writing\" — the most comprehensive public catalog of AI writing patterns.\n\n## Banned Words and Phrases\n\nNever use these. They are the most documented AI tells:\n\n**Promotional fluff:** vibrant, nestled, rich heritage, groundbreaking, showcasing, diverse array, pivotal moment, stands as, testament, marks a shift, broader trends, cutting-edge, revolutionizing, game-changing, innovative\n\n**Vague intensifiers:** delve, intricate, tapestry, foster, enhance, leverage, utilize, multifaceted, comprehensive, robust, seamless\n\n**False attribution:** industry reports suggest, experts argue, researchers note, studies show (without citing specific studies)\n\n**Filler transitions:** additionally, furthermore, moreover, it's worth noting, it's important to note, in today's landscape, in the realm of\n\n**Outline conclusions:** \"Despite its [positive traits], [subject] faces challenges...\" — never use this formula\n\n## Structural Tells to Avoid\n\n1. **Rule of Three abuse** — stop listing three adjectives or three phrases for artificial comprehensiveness. Use one strong word.\n2. **Negative parallelisms** — \"Not just X, but also Y\" sounds like a press release. Say what it IS.\n3. **Elegant variation** — don't replace a word with a synonym just to avoid repetition. Repeat the word. \"The API\" is clearer than \"the interface\" the second time.\n4. **Em dash overuse** — use commas or parentheses. Em dashes in every paragraph = AI tell.\n5. **Excessive boldface** — bold is for emphasis, not decoration. One bold per paragraph max.\n6. **Title Case headings** — use sentence case: \"How to deploy\" not \"How To Deploy\"\n7. **Inline-header bullet lists** — not everything needs to be a bold-header-colon-description bullet. Write prose.\n8. **Section summaries** — never summarize what you just said at the end of a section.\n\n## Tone Rules\n\n1. **Never sound promotional.** You're explaining, not selling. \"This tool syncs your database\" not \"This powerful tool revolutionizes database synchronization.\"\n2. **Never inflate significance.** Small features are small. Don't call a config change a \"pivotal moment.\"\n3. **Never address the reader as \"you\" in docs** unless it's a tutorial with explicit steps. \"Users can configure X\" not \"You can configure X.\"\n4. **Never use collaborative language.** \"Let's explore\" and \"we'll dive into\" are chatbot patterns. State the information directly.\n5. **Be specific.** \"Reduces API calls by 40%\" beats \"significantly improves performance.\" Numbers over adjectives.\n6. **Be direct.** \"This function returns null on failure\" beats \"This function is designed to gracefully handle failure scenarios by returning a null value.\"\n\n## Verification\n\nAfter writing any text, check:\n- [ ] No banned words\u002Fphrases from the list above\n- [ ] No Rule of Three patterns (3 adjectives, 3 phrases in a row)\n- [ ] No em dashes used where commas would work\n- [ ] No promotional tone — would a technical writer approve this?\n- [ ] No vague claims without specific evidence\n- [ ] Sentence case headings, not Title Case\n- [ ] Prose over bullet lists where possible\n- [ ] No \"in conclusion\" or \"in summary\" wrapping sections\n\n## Anti-Patterns\n\n- Writing a landing page that sounds like every other AI-generated landing page\n- Blog posts that \"delve into\" topics and find them \"multifaceted\"\n- README files that describe the project as \"a robust, comprehensive solution\"\n- Emails that start with \"I hope this message finds you well\"\n- Social media posts with emoji before every bullet point\n","# Anti-AI Writing\n\nEvery piece of text this harness produces must read like a human wrote it. AI-generated writing has documented tells. This skill flags and fixes them.\n\nSource: Wikipedia's \"Signs of AI writing\" — the most comprehensive public catalog of AI writing patterns.\n\n## Banned Words and Phrases\n\nNever use these. They are the most documented AI tells:\n\n**Promotional fluff:** vibrant, nestled, rich heritage, groundbreaking, showcasing, diverse array, pivotal moment, stands as, testament, marks a shift, broader trends, cutting-edge, revolutionizing, game-changing, innovative\n\n**Vague intensifiers:** delve, intricate, tapestry, foster, enhance, leverage, utilize, multifaceted, comprehensive, robust, seamless\n\n**False attribution:** industry reports suggest, experts argue, researchers note, studies show (without citing specific studies)\n\n**Filler transitions:** additionally, furthermore, moreover, it's worth noting, it's important to note, in today's landscape, in the realm of\n\n**Outline conclusions:** \"Despite its [positive traits], [subject] faces challenges...\" — never use this formula\n\n## Structural Tells to Avoid\n\n1. **Rule of Three abuse** — stop listing three adjectives or three phrases for artificial comprehensiveness. Use one strong word.\n2. **Negative parallelisms** — \"Not just X, but also Y\" sounds like a press release. Say what it IS.\n3. **Elegant variation** — don't replace a word with a synonym just to avoid repetition. Repeat the word. \"The API\" is clearer than \"the interface\" the second time.\n4. **Em dash overuse** — use commas or parentheses. Em dashes in every paragraph = AI tell.\n5. **Excessive boldface** — bold is for emphasis, not decoration. One bold per paragraph max.\n6. **Title Case headings** — use sentence case: \"How to deploy\" not \"How To Deploy\"\n7. **Inline-header bullet lists** — not everything needs to be a bold-header-colon-description bullet. Write prose.\n8. **Section summaries** — never summarize what you just said at the end of a section.\n\n## Tone Rules\n\n1. **Never sound promotional.** You're explaining, not selling. \"This tool syncs your database\" not \"This powerful tool revolutionizes database synchronization.\"\n2. **Never inflate significance.** Small features are small. Don't call a config change a \"pivotal moment.\"\n3. **Never address the reader as \"you\" in docs** unless it's a tutorial with explicit steps. \"Users can configure X\" not \"You can configure X.\"\n4. **Never use collaborative language.** \"Let's explore\" and \"we'll dive into\" are chatbot patterns. State the information directly.\n5. **Be specific.** \"Reduces API calls by 40%\" beats \"significantly improves performance.\" Numbers over adjectives.\n6. **Be direct.** \"This function returns null on failure\" beats \"This function is designed to gracefully handle failure scenarios by returning a null value.\"\n\n## Verification\n\nAfter writing any text, check:\n- [ ] No banned words\u002Fphrases from the list above\n- [ ] No Rule of Three patterns (3 adjectives, 3 phrases in a row)\n- [ ] No em dashes used where commas would work\n- [ ] No promotional tone — would a technical writer approve this?\n- [ ] No vague claims without specific evidence\n- [ ] Sentence case headings, not Title Case\n- [ ] Prose over bullet lists where possible\n- [ ] No \"in conclusion\" or \"in summary\" wrapping sections\n\n## Anti-Patterns\n\n- Writing a landing page that sounds like every other AI-generated landing page\n- Blog posts that \"delve into\" topics and find them \"multifaceted\"\n- README files that describe the project as \"a robust, comprehensive solution\"\n- Emails that start with \"I hope this message finds you well\"\n- Social media posts with emoji before every bullet point\n",{"name":5,"next":60,"group":61,"workflows":62,"always-load":64,"description":7,"prerequisites":65,"user-invocable":64},[],"comms",[63],"all",true,[],"main","92dddf7f6e7b55d1424795ce11586b05dba9d8c8","skills\u002Fanti-ai-writing",3,"https:\u002F\u002Fgithub.com\u002FCheggin\u002Frequest-for-startups","https:\u002F\u002Fgithub.com\u002FCheggin","reaganhsu.com","MTS @datacurve-ai, prev. founding eng @browser-use ","2026-04-24 08:33:47",{"source":8,"skillName":5,"commands":76,"prompt":86,"zipAvailable":64},[77,80,83],{"tool":78,"command":79},"npx","npx skills add Cheggin\u002Frequest-for-startups --skill anti-ai-writing",{"tool":81,"command":82},"bunx","bunx skills add Cheggin\u002Frequest-for-startups --skill anti-ai-writing",{"tool":84,"command":85},"pnpm","pnpm dlx skills add Cheggin\u002Frequest-for-startups --skill anti-ai-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCheggin\u002Frequest-for-startups\u002Fblob\u002Fmain\u002Fskills\u002Fanti-ai-writing\u002FSKILL.md",[],[89,113,133,166,181,204],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":55},"01M6X7PHK069RZH25A3RXN5049","writer-memory","Agentic memory system for writers - track characters, relationships, scenes, and themes","https:\u002F\u002Fgithub.com\u002FCheggin\u002Frequest-for-startups\u002Fblob\u002Fmain\u002Fskills\u002Fwriter-memory\u002FSKILL.md",[],[96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112],"memory","writer","writer memory","system","characters","track","for","themes","memory system","scenes","relationships","query","export","status","validate","init","agentic",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":55},"01M6X7PC3G9228Z323X5YAKTVW","wiki","LLM Wiki — persistent markdown knowledge base that compounds across sessions (Karpathy model)","https:\u002F\u002Fgithub.com\u002FCheggin\u002Frequest-for-startups\u002Fblob\u002Fmain\u002Fskills\u002Fwiki\u002FSKILL.md",[],[115,120,121,122,123,124,125,126,127,128,129,130,131,107,132],"wiki lint","knowledge","model","llm wiki","markdown","wiki query","knowledge base","lint","sessions","karpathy","add","across","base",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":147,"publishedAt":55},"01M6X7P5XFW5C16H3JE4NFQ7MF","website-creation","Build production-quality SaaS websites with opinionated design presets. Use when creating any startup website. The user MUST pick a design style before building. Enforces shadcn\u002Fui, Figma design principles, specific CSS values per style, and anti-AI-writing. Load alongside anti-ai-writing skill. LIGHT MODE ONLY.","https:\u002F\u002Fgithub.com\u002FCheggin\u002Frequest-for-startups\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-creation\u002FSKILL.md",[139,142,143,146],{"categoryNo":140,"categoryName":141,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":144,"categoryName":145,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师",{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},[148,149,150,38,151,152,153,154,155,36,156,157,158,159,160,161,162,163,164,165],"website creation","website","creation","design style","mode","brand-guidelines","full","ui","design principles","only","pick","polish","audit","shadcn","figma","css","Anti-AI","design",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":55},"01M6X7P3PCEAKA2SBETXHHTNBA","visual-verdict","Structured visual QA verdict for screenshot-to-reference comparisons","https:\u002F\u002Fgithub.com\u002FCheggin\u002Frequest-for-startups\u002Fblob\u002Fmain\u002Fskills\u002Fvisual-verdict\u002FSKILL.md",[],[173,174,175,102,176,177,178,179,180],"visual verdict","verdict","visual","visual qa","structured","reference","screenshot","qa",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":195,"publishedAt":55},"01M6X7NXEWWC4NFT0ZK1RRSGES","visual-qa-pipeline","Screenshot every page with Playwright, feed to visual QA agent for design evaluation, report results to Slack. Use after every build phase to verify UI matches the chosen design preset. Integrates with the Playwright skill and the website-creation preset system.","https:\u002F\u002Fgithub.com\u002FCheggin\u002Frequest-for-startups\u002Fblob\u002Fmain\u002Fskills\u002Fvisual-qa-pipeline\u002FSKILL.md",[187,190,193,194],{"categoryNo":188,"categoryName":189,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":191,"categoryName":192,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":140,"categoryName":141,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":144,"categoryName":145,"taxonomyType":29,"taxonomyTypeDesc":30},[175,196,176,180,197,198,135,150,154,199,159,200,155,149,179,102,201,165,202,203],"pipeline","visual qa pipeline","slack","page","Evaluation","review","verify ui","phase",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":208,"categories":209,"keywords":210,"publishedAt":55},"01M6X7NSNW00RQ8J531F52YHV9","verify","Verify that a change really works before you claim completion","https:\u002F\u002Fgithub.com\u002FCheggin\u002Frequest-for-startups\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[206,211,39,212,213,51,196,214,215],"deploy-pipeline","you","claim","deploy","change"]