[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7341PCPKMHPVNSC69T42ESK":3,"skill-same:01M7341PCPKMHPVNSC69T42ESK":51},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M7341PCPKMHPVNSC69T42ESK","ask-text-writing",null,"Text Writing: Writes emails, posts, articles, bios, READMEs, and docs that sound human and avoid AI writing patterns. Use when drafting or rewriting prose. Common triggers: anti-slop, make this sound human, sound human, not AI, does not read like AI, write a tweet, draft email, write an email, cover letter, linkedin post, newsletter, blog post, copywriting, schrijf als mens, niet AI, menselijk laten klinken, text-writing, text writing, schrijf de tekst, schrijf de teksten, herschrijf de tekst, teksten herschrijven.","MarkBovee\u002Fagent-skills-kit","MarkBovee","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1203948?v=4","01M733X7T9ZYGXR05VBXNZEH36","Mark Bovee","01M733X7V1Q57ZK772WYENHFAV",1,"MIT","https:\u002F\u002Fgithub.com\u002FMarkBovee\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fask-text-writing\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: \"ask-text-writing\"\ndescription: \"Text Writing: Writes emails, posts, articles, bios, READMEs, and docs that sound human and avoid AI writing patterns. Use when drafting or rewriting prose. Common triggers: anti-slop, make this sound human, sound human, not AI, does not read like AI, write a tweet, draft email, write an email, cover letter, linkedin post, newsletter, blog post, copywriting, schrijf als mens, niet AI, menselijk laten klinken, text-writing, text writing, schrijf de tekst, schrijf de teksten, herschrijf de tekst, teksten herschrijven.\"\ndisable-model-invocation: true\n---\n# Human-First Writing\n\nProduce text that does not read as AI-generated. Every piece of text — tweets, emails, articles, reports, messages — follows these constraints. Apply them silently; never mention the rules or the guidelines.\n\n## Banned vocabulary\n\nLoad and respect the list in `references\u002Fbanned-words.md`. Never use any banned word, phrase, or opener. Replace it with a concrete specific alternative or restructure the sentence.\n\n## Structure\n\n- **No rule of three.** Use two, four, one, five. Never three by default.\n- **Vary sentence length.** No three consecutive same-length sentences. Mix 4-word sentences with 30-word ones — the most measurable AI signal.\n- **No parataxis.** Do not chain short declarative sentences. Connect related thoughts with clauses, conjunctions, semicolons, or commas.\n- **No hedging seesaw.** Pick a side; state it plainly. One sentence max for counterpoints.\n- **No corporate pep talk.** Write like someone with experience, including the frustrating parts.\n- **Vary paragraph shape.** Do not always open with topic sentence, then explanation, then example, then transition. Some paragraphs are one sentence; some just stop.\n- **Active voice.** No \"is being done,\" \"was found to be.\" Write direct.\n- **No \"As [role], I...\"** Say the thing without announcing credentials.\n\n## Punctuation\n\n- One em dash max per 500 words — the most cited AI tell. Use commas, semicolons, colons, parentheses.\n- One exclamation mark max per 1000 words. Enthusiasm comes from word choice.\n- Ellipses only when genuinely trailing off, one per piece.\n- Use semicolons and colons; good writers use them naturally.\n\n## Be specific\n\n- Concrete beats general: \"Three clicks from wallet connect to your first risk score\" beats \"a seamless user experience.\"\n- Real numbers beat claims: \"34 users in week one, 12 returned\" beats \"significant growth.\"\n- Name real things: \"Solana, specifically\" beats \"various blockchain networks.\"\n- Include friction and mess: \"The RPC kept timing out at 3am\" beats \"a rewarding journey.\"\n- Use contractions: \"don't\", \"can't\", \"it's\".\n- Ground in time, place, context: \"last Tuesday,\" \"at 2am.\"\n- Fragment or run on when the thought is unfinished. Ugly is human.\n- Reach past the first word that comes to mind.\n\n## Accuracy\n\n- Never invent data, studies, statistics, or quotes. Say \"roughly\" or acknowledge uncertainty.\n- Take clear positions when evidence is solid; qualify only genuine uncertainty.\n- Use real verifiable names, companies, dates: \"OakNorth\" beats \"a major bank.\"\n\n## Formatting\n\n- No markdown headers, bold, or asterisks in emails, DMs, SMS, social. Plain text only.\n- No emoji as bullet points, no emoji per line, no \"🧵\" openers, no hashtag stacks.\n- No \"Thread:\" or \"Let's dive in\" openers.\n\n## Voice calibration\n\nFor a specific person, match their voice: swearing, slang, sentence length, humour, what they would never say. Default: direct, slightly informal, contractions, occasionally \"And\"\u002F\"But\" starts, does not over-explain.\n\n## Self-check before output\n\n1. Banned words or openers? Replace.\n2. Three same-length sentences in a row? Vary.\n3. Three short declaratives in a row? Merge or connect.\n4. Grouped in threes? Break it.\n5. Hedging? Pick a side.\n6. More than one em dash? Cut.\n7. Passive construction? Make active.\n8. Every paragraph ends with a transition? Cut some.\n9. Fabricated specifics? Remove or mark hypothetical.\n10. Could any AI have written this for anyone? Add something specific.\n\n## Use with\n\n- `design` for web copy inside a design, then `design-review` before showing it\n- `design-review` to review existing copy for AI-default patterns\n- `write-skill` if writing quality reveals a reusable gap worth capturing\n- `session-review` to file follow-up improvements\n\n## Avoid\n\n- Surfacing the rules to the reader — apply silently\n- Rule-of-three lists, uniform rhythm, passive voice, invented specifics\n- Treating this as a style guide for design — that is `design-review`'s job\n\n---\n\n*Adapted from [jalaalrd\u002Fanti-ai-slop-writing](https:\u002F\u002Fgithub.com\u002Fjalaalrd\u002Fanti-ai-slop-writing) (MIT).*\n","# Human-First Writing\n\nProduce text that does not read as AI-generated. Every piece of text — tweets, emails, articles, reports, messages — follows these constraints. Apply them silently; never mention the rules or the guidelines.\n\n## Banned vocabulary\n\nLoad and respect the list in `references\u002Fbanned-words.md`. Never use any banned word, phrase, or opener. Replace it with a concrete specific alternative or restructure the sentence.\n\n## Structure\n\n- **No rule of three.** Use two, four, one, five. Never three by default.\n- **Vary sentence length.** No three consecutive same-length sentences. Mix 4-word sentences with 30-word ones — the most measurable AI signal.\n- **No parataxis.** Do not chain short declarative sentences. Connect related thoughts with clauses, conjunctions, semicolons, or commas.\n- **No hedging seesaw.** Pick a side; state it plainly. One sentence max for counterpoints.\n- **No corporate pep talk.** Write like someone with experience, including the frustrating parts.\n- **Vary paragraph shape.** Do not always open with topic sentence, then explanation, then example, then transition. Some paragraphs are one sentence; some just stop.\n- **Active voice.** No \"is being done,\" \"was found to be.\" Write direct.\n- **No \"As [role], I...\"** Say the thing without announcing credentials.\n\n## Punctuation\n\n- One em dash max per 500 words — the most cited AI tell. Use commas, semicolons, colons, parentheses.\n- One exclamation mark max per 1000 words. Enthusiasm comes from word choice.\n- Ellipses only when genuinely trailing off, one per piece.\n- Use semicolons and colons; good writers use them naturally.\n\n## Be specific\n\n- Concrete beats general: \"Three clicks from wallet connect to your first risk score\" beats \"a seamless user experience.\"\n- Real numbers beat claims: \"34 users in week one, 12 returned\" beats \"significant growth.\"\n- Name real things: \"Solana, specifically\" beats \"various blockchain networks.\"\n- Include friction and mess: \"The RPC kept timing out at 3am\" beats \"a rewarding journey.\"\n- Use contractions: \"don't\", \"can't\", \"it's\".\n- Ground in time, place, context: \"last Tuesday,\" \"at 2am.\"\n- Fragment or run on when the thought is unfinished. Ugly is human.\n- Reach past the first word that comes to mind.\n\n## Accuracy\n\n- Never invent data, studies, statistics, or quotes. Say \"roughly\" or acknowledge uncertainty.\n- Take clear positions when evidence is solid; qualify only genuine uncertainty.\n- Use real verifiable names, companies, dates: \"OakNorth\" beats \"a major bank.\"\n\n## Formatting\n\n- No markdown headers, bold, or asterisks in emails, DMs, SMS, social. Plain text only.\n- No emoji as bullet points, no emoji per line, no \"🧵\" openers, no hashtag stacks.\n- No \"Thread:\" or \"Let's dive in\" openers.\n\n## Voice calibration\n\nFor a specific person, match their voice: swearing, slang, sentence length, humour, what they would never say. Default: direct, slightly informal, contractions, occasionally \"And\"\u002F\"But\" starts, does not over-explain.\n\n## Self-check before output\n\n1. Banned words or openers? Replace.\n2. Three same-length sentences in a row? Vary.\n3. Three short declaratives in a row? Merge or connect.\n4. Grouped in threes? Break it.\n5. Hedging? Pick a side.\n6. More than one em dash? Cut.\n7. Passive construction? Make active.\n8. Every paragraph ends with a transition? Cut some.\n9. Fabricated specifics? Remove or mark hypothetical.\n10. Could any AI have written this for anyone? Add something specific.\n\n## Use with\n\n- `design` for web copy inside a design, then `design-review` before showing it\n- `design-review` to review existing copy for AI-default patterns\n- `write-skill` if writing quality reveals a reusable gap worth capturing\n- `session-review` to file follow-up improvements\n\n## Avoid\n\n- Surfacing the rules to the reader — apply silently\n- Rule-of-three lists, uniform rhythm, passive voice, invented specifics\n- Treating this as a style guide for design — that is `design-review`'s job\n\n---\n\n*Adapted from [jalaalrd\u002Fanti-ai-slop-writing](https:\u002F\u002Fgithub.com\u002Fjalaalrd\u002Fanti-ai-slop-writing) (MIT).*\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","cef5fa0ba7fd07c76ac37b31c2d09db85419e0b9",".github\u002Fskills\u002Fask-text-writing",0,"https:\u002F\u002Fgithub.com\u002FMarkBovee\u002Fagent-skills-kit","https:\u002F\u002Fgithub.com\u002FMarkBovee","2026-11-09 02:17:08",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add MarkBovee\u002Fagent-skills-kit --skill ask-text-writing",{"tool":38,"command":39},"bunx","bunx skills add MarkBovee\u002Fagent-skills-kit --skill ask-text-writing",{"tool":41,"command":42},"pnpm","pnpm dlx skills add MarkBovee\u002Fagent-skills-kit --skill ask-text-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMarkBovee\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fask-text-writing\u002FSKILL.md",[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fbanned-words.md","REFERENCE","参考文档",2715,"https:\u002F\u002Fgithub.com\u002FMarkBovee\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fask-text-writing\u002Freferences\u002Fbanned-words.md",[52,59,66,72,79,86],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7343K5655Z7JCBPJKXMC24K","ask-write-skill","Write Skill: Creates and revises skills and guardrails from reusable workflow gaps. Use when making a skill or when agent behavior exposes a routing gap.","https:\u002F\u002Fgithub.com\u002FMarkBovee\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002Fskills\u002Fask-write-skill\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7343G7HSVYVB1BKK49ZD04R","ask-verification","Verification: Proves work is fixed or ready and cleans up changed repos. Use before claiming something works or handing off.","https:\u002F\u002Fgithub.com\u002FMarkBovee\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002Fskills\u002Fask-verification\u002FSKILL.md",[],[],{"skillNo":67,"name":5,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7343D2RDXYZRRQWJKW15MHW","Text Writing: Writes emails, posts, articles, bios, READMEs, and docs that sound human and avoid AI writing patterns. Use when drafting or rewriting prose.","https:\u002F\u002Fgithub.com\u002FMarkBovee\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002Fskills\u002Fask-text-writing\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7343A980X77TDWV0FZAYBS2","ask-summary","Summary: Explains what changed and what is proven, walks through code, or re-pitches unclear output. Use when work is done or the user asks what changed.","https:\u002F\u002Fgithub.com\u002FMarkBovee\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002Fskills\u002Fask-summary\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M73438ARMNM8W991A7EPGRG1","ask-session-review","Session Review: Reflects on skill usage and gaps and files GitHub issues from bugs, findings, or follow-ups. Use after completing work.","https:\u002F\u002Fgithub.com\u002FMarkBovee\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002Fskills\u002Fask-session-review\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M734362MZYM4CT488AAFX84G","ask-research","Research: Does bounded fact-finding across the repository, docs, code, or external sources. Use when a question needs evidence before an answer or decision.","https:\u002F\u002Fgithub.com\u002FMarkBovee\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002Fskills\u002Fask-research\u002FSKILL.md",[],[]]