[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71EF4ACKBMM9RJQ497TKTNY":3,"skill-same:01M71EF4ACKBMM9RJQ497TKTNY":69},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M71EF4ACKBMM9RJQ497TKTNY","gale-style-editor",null,"This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for grammar, punctuation, mechanics, and style guide compliance.","JGXC100\u002FGaleHarnessCodingCLI","JGXC100","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11926809?v=4","01M71EEBHJ3EGYSNNDDSVDKXNG","JGX","01M71EEBJ995S5J2HDEQCBA268",0,"MIT","https:\u002F\u002Fgithub.com\u002FJGXC100\u002FGaleHarnessCodingCLI\u002Fblob\u002Fmain\u002Fplugins\u002Fgaleharness-cli\u002Fskills\u002Fgale-style-editor\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"style","editor","gale style editor","guide","it","copy","systematic","line","grammar","process","compliance","review process","review","style guide","when","mechanics","editing","for","2026-11-10 10:12:30",false,"---\nname: gale-style-editor\ndescription: This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for grammar, punctuation, mechanics, and style guide compliance.\n---\n\n# Every Style Editor\n\nThis skill provides a systematic approach to reviewing copy against Every's comprehensive style guide. It transforms Claude into a meticulous line editor and proofreader specializing in grammar, mechanics, and style guide compliance.\n\n## When to Use This Skill\n\nUse this skill when:\n- Reviewing articles, blog posts, newsletters, or any written content\n- Ensuring copy follows Every's specific style conventions\n- Providing feedback on grammar, punctuation, and mechanics\n- Flagging deviations from the Every style guide\n- Preparing clean copy for human editorial review\n\n## Skill Overview\n\nThis skill enables performing a comprehensive review of written content in four phases:\n\n1. **Initial Assessment** - Understanding context and document type\n2. **Detailed Line Edit** - Checking every sentence for compliance\n3. **Mechanical Review** - Verifying formatting and consistency\n4. **Recommendations** - Providing actionable improvement suggestions\n\n## How to Use This Skill\n\n### Step 1: Initial Assessment\n\nBegin by reading the entire piece to understand:\n- Document type (article, knowledge base entry, social post, etc.)\n- Target audience\n- Overall tone and voice\n- Content context\n\n### Step 2: Detailed Line Edit\n\nReview each paragraph systematically, checking for:\n- Sentence structure and grammar correctness\n- Punctuation usage (commas, semicolons, em dashes, etc.)\n- Capitalization rules (especially job titles, headlines)\n- Word choice and usage (overused words, passive voice)\n- Adherence to Every style guide rules\n\nReference the complete style guide at `references\u002FEVERY_WRITE_STYLE.md` for specific rules when in doubt.\n\n### Step 3: Mechanical Review\n\nVerify:\n- Spacing and formatting consistency\n- Style choices applied uniformly throughout\n- Special elements (lists, quotes, citations)\n- Proper use of italics and formatting\n- Number formatting (numerals vs. spelled out)\n- Link formatting and descriptions\n\n### Step 4: Output Results\n\nPresent findings using this structure:\n\n```\nDOCUMENT REVIEW SUMMARY\n=====================\nDocument Type: [type]\nWord Count: [approximate]\nOverall Assessment: [brief overview]\n\nERRORS FOUND: [total number]\n\nDETAILED CORRECTIONS\n===================\n\n[For each error found:]\n\n**Location**: [Paragraph #, Sentence #]\n**Issue Type**: [Grammar\u002FPunctuation\u002FMechanics\u002FStyle Guide]\n**Original**: \"[exact text with error]\"\n**Correction**: \"[corrected text]\"\n**Rule Reference**: [Specific style guide rule violated]\n**Explanation**: [Brief explanation of why this is an error]\n\n---\n\nRECURRING ISSUES\n===============\n[List patterns of errors that appear multiple times]\n\nSTYLE GUIDE COMPLIANCE CHECKLIST\n==============================\n✓ [Rule followed correctly]\n✗ [Rule violated - with count of violations]\n\nFINAL RECOMMENDATIONS\n===================\n[2-3 actionable suggestions for improving the draft]\n```\n\n## Style Guide Reference\n\nThe complete Every style guide is at `references\u002FEVERY_WRITE_STYLE.md`. Key areas to focus on:\n\n- **Quick Rules**: Title case for headlines, sentence case elsewhere\n- **Tone**: Active voice, avoid overused words (actually, very, just), be specific\n- **Numbers**: Spell out one through nine; use numerals for 10+\n- **Punctuation**: Oxford commas, em dashes without spaces, proper quotation mark usage\n- **Capitalization**: Lowercase job titles, company as singular (it), teams as plural (they)\n- **Emphasis**: Italics only (no bold for emphasis)\n- **Links**: 2-4 words, don't say \"click here\"\n\n## Key Principles\n\n- **Be specific**: Always quote the exact text with the error\n- **Reference rules**: Cite the specific style guide rule for each correction\n- **Maintain voice**: Preserve the author's voice while correcting errors\n- **Prioritize clarity**: Focus on changes that improve readability\n- **Be constructive**: Frame feedback to help writers improve\n- **Flag ambiguous cases**: When style guide doesn't address an issue, explain options and recommend the clearest choice\n\n## Common Areas to Focus On\n\nBased on Every's style guide, pay special attention to:\n\n- Punctuation (comma usage, semicolons, apostrophes, quotation marks)\n- Capitalization (proper nouns, titles, sentence starts)\n- Numbers (when to spell out vs. use numerals)\n- Passive voice (replace with active whenever possible)\n- Overused words (actually, very, just)\n- Lists (parallel structure, punctuation, capitalization)\n- Hyphenation (compound adjectives, except adverbs)\n- Word usage (fewer vs. less, they vs. them)\n- Company references (singular \"it\", teams as plural \"they\")\n- Job title capitalization\n\n","# Every Style Editor\n\nThis skill provides a systematic approach to reviewing copy against Every's comprehensive style guide. It transforms Claude into a meticulous line editor and proofreader specializing in grammar, mechanics, and style guide compliance.\n\n## When to Use This Skill\n\nUse this skill when:\n- Reviewing articles, blog posts, newsletters, or any written content\n- Ensuring copy follows Every's specific style conventions\n- Providing feedback on grammar, punctuation, and mechanics\n- Flagging deviations from the Every style guide\n- Preparing clean copy for human editorial review\n\n## Skill Overview\n\nThis skill enables performing a comprehensive review of written content in four phases:\n\n1. **Initial Assessment** - Understanding context and document type\n2. **Detailed Line Edit** - Checking every sentence for compliance\n3. **Mechanical Review** - Verifying formatting and consistency\n4. **Recommendations** - Providing actionable improvement suggestions\n\n## How to Use This Skill\n\n### Step 1: Initial Assessment\n\nBegin by reading the entire piece to understand:\n- Document type (article, knowledge base entry, social post, etc.)\n- Target audience\n- Overall tone and voice\n- Content context\n\n### Step 2: Detailed Line Edit\n\nReview each paragraph systematically, checking for:\n- Sentence structure and grammar correctness\n- Punctuation usage (commas, semicolons, em dashes, etc.)\n- Capitalization rules (especially job titles, headlines)\n- Word choice and usage (overused words, passive voice)\n- Adherence to Every style guide rules\n\nReference the complete style guide at `references\u002FEVERY_WRITE_STYLE.md` for specific rules when in doubt.\n\n### Step 3: Mechanical Review\n\nVerify:\n- Spacing and formatting consistency\n- Style choices applied uniformly throughout\n- Special elements (lists, quotes, citations)\n- Proper use of italics and formatting\n- Number formatting (numerals vs. spelled out)\n- Link formatting and descriptions\n\n### Step 4: Output Results\n\nPresent findings using this structure:\n\n```\nDOCUMENT REVIEW SUMMARY\n=====================\nDocument Type: [type]\nWord Count: [approximate]\nOverall Assessment: [brief overview]\n\nERRORS FOUND: [total number]\n\nDETAILED CORRECTIONS\n===================\n\n[For each error found:]\n\n**Location**: [Paragraph #, Sentence #]\n**Issue Type**: [Grammar\u002FPunctuation\u002FMechanics\u002FStyle Guide]\n**Original**: \"[exact text with error]\"\n**Correction**: \"[corrected text]\"\n**Rule Reference**: [Specific style guide rule violated]\n**Explanation**: [Brief explanation of why this is an error]\n\n---\n\nRECURRING ISSUES\n===============\n[List patterns of errors that appear multiple times]\n\nSTYLE GUIDE COMPLIANCE CHECKLIST\n==============================\n✓ [Rule followed correctly]\n✗ [Rule violated - with count of violations]\n\nFINAL RECOMMENDATIONS\n===================\n[2-3 actionable suggestions for improving the draft]\n```\n\n## Style Guide Reference\n\nThe complete Every style guide is at `references\u002FEVERY_WRITE_STYLE.md`. Key areas to focus on:\n\n- **Quick Rules**: Title case for headlines, sentence case elsewhere\n- **Tone**: Active voice, avoid overused words (actually, very, just), be specific\n- **Numbers**: Spell out one through nine; use numerals for 10+\n- **Punctuation**: Oxford commas, em dashes without spaces, proper quotation mark usage\n- **Capitalization**: Lowercase job titles, company as singular (it), teams as plural (they)\n- **Emphasis**: Italics only (no bold for emphasis)\n- **Links**: 2-4 words, don't say \"click here\"\n\n## Key Principles\n\n- **Be specific**: Always quote the exact text with the error\n- **Reference rules**: Cite the specific style guide rule for each correction\n- **Maintain voice**: Preserve the author's voice while correcting errors\n- **Prioritize clarity**: Focus on changes that improve readability\n- **Be constructive**: Frame feedback to help writers improve\n- **Flag ambiguous cases**: When style guide doesn't address an issue, explain options and recommend the clearest choice\n\n## Common Areas to Focus On\n\nBased on Every's style guide, pay special attention to:\n\n- Punctuation (comma usage, semicolons, apostrophes, quotation marks)\n- Capitalization (proper nouns, titles, sentence starts)\n- Numbers (when to spell out vs. use numerals)\n- Passive voice (replace with active whenever possible)\n- Overused words (actually, very, just)\n- Lists (parallel structure, punctuation, capitalization)\n- Hyphenation (compound adjectives, except adverbs)\n- Word usage (fewer vs. less, they vs. them)\n- Company references (singular \"it\", teams as plural \"they\")\n- Job title capitalization\n\n",{"name":5,"description":7},"main","94fc651a7c5ff227f3e8f4b9678dc4566f535677","plugins\u002Fgaleharness-cli\u002Fskills\u002Fgale-style-editor",2,"https:\u002F\u002Fgithub.com\u002FJGXC100\u002FGaleHarnessCodingCLI","https:\u002F\u002Fgithub.com\u002FJGXC100","2026-05-19 17:04:59",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add JGXC100\u002FGaleHarnessCodingCLI --skill gale-style-editor",{"tool":55,"command":56},"bunx","bunx skills add JGXC100\u002FGaleHarnessCodingCLI --skill gale-style-editor",{"tool":58,"command":59},"pnpm","pnpm dlx skills add JGXC100\u002FGaleHarnessCodingCLI --skill gale-style-editor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJGXC100\u002FGaleHarnessCodingCLI\u002Fblob\u002Fmain\u002Fplugins\u002Fgaleharness-cli\u002Fskills\u002Fgale-style-editor\u002FSKILL.md",true,[63],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002FEVERY_WRITE_STYLE.md","REFERENCE","参考文档",29243,"https:\u002F\u002Fgithub.com\u002FJGXC100\u002FGaleHarnessCodingCLI\u002Fblob\u002Fmain\u002Fplugins\u002Fgaleharness-cli\u002Fskills\u002Fgale-style-editor\u002Freferences\u002FEVERY_WRITE_STYLE.md",[70,86,100,112,120,128],{"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":81,"publishedAt":37},"01M71EJT9M91X2T91N4ZPCWHN3","skill-one","Sample skill","https:\u002F\u002Fgithub.com\u002FJGXC100\u002FGaleHarnessCodingCLI\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsample-plugin\u002Fskills\u002Fskill-one\u002FSKILL.md",[76],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[82,83,84,85],"skill one","one","sample skill","sample",{"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":93,"publishedAt":37},"01M71EJRH7M0DGZ1QXJ9PSFMB5","disabled-skill","A skill with model invocation disabled","https:\u002F\u002Fgithub.com\u002FJGXC100\u002FGaleHarnessCodingCLI\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsample-plugin\u002Fskills\u002Fdisabled-skill\u002FSKILL.md",[92],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[94,95,96,97,98,99],"disabled skill","a skill","with model","with","true","model",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":107,"publishedAt":37},"01M71EJQMRH6JC9H9V5BQWM7RJ","claude-only-skill","A skill restricted to Claude Code only","https:\u002F\u002Fgithub.com\u002FJGXC100\u002FGaleHarnessCodingCLI\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsample-plugin\u002Fskills\u002Fclaude-only-skill\u002FSKILL.md",[106],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[108,109,110,111,95],"only","claude only skill","claude only","code",{"skillNo":113,"name":114,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":37},"01M71EJPXZ0644M41M587FVKYQ","default-skill","https:\u002F\u002Fgithub.com\u002FJGXC100\u002FGaleHarnessCodingCLI\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fcustom-paths\u002Fskills\u002Fdefault-skill\u002FSKILL.md",[],[118,119],"default skill","default",{"skillNo":121,"name":122,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":37},"01M71EJP6RPF6PDAJ2SY4VMBDT","custom-skill","https:\u002F\u002Fgithub.com\u002FJGXC100\u002FGaleHarnessCodingCLI\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fcustom-paths\u002Fcustom-skills\u002Fcustom-skill\u002FSKILL.md",[],[126,127],"custom skill","custom",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":137,"publishedAt":37},"01M71EJK74AZ929S8GF55G5CDV","test-xcode","Build and test iOS apps on simulator using XcodeBuildMCP. Use after making iOS code changes, before creating a PR, or when verifying app behavior and checking for crashes on simulator.","https:\u002F\u002Fgithub.com\u002FJGXC100\u002FGaleHarnessCodingCLI\u002Fblob\u002Fmain\u002Fplugins\u002Fgaleharness-cli\u002Fskills\u002Ftest-xcode\u002FSKILL.md",[134],{"categoryNo":135,"categoryName":136,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000008","测试与质量",[138,139,140,141,142,143,144,36,119,98,145,146,147,33,111,148,149,150,151,152],"test","xcode","test xcode","apps","app","build and test","pr","xcodebuildmcp","use","scheme","changes","build","ios","name","behavior"]