[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74EWF164539Q60N5FPEPCMF":3,"skill-same:01M74EWF164539Q60N5FPEPCMF":126},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":92,"commitSha":93,"skillDirectory":94,"forksCount":13,"repositoryHtmlUrl":95,"repositoryHomepageUrl":6,"ownerHtmlUrl":96,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":97,"install":98,"resources":111},"01M74EWF164539Q60N5FPEPCMF","seo-content-writer",null,"Write SEO blog posts, articles, landing pages with keyword integration, header optimization, and snippet targeting. SEO文章写作\u002F内容优化","lzy18001500226\u002FMoSim","lzy18001500226","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F152623587?v=4","01M71ZMEX36NK05B642131DEEK","01M71ZMEXSMX72KPVNJ572G0CM",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FMemory\u002FSurfSense\u002F.cursor\u002Fskills\u002Fseo-content-writer\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: seo-content-writer\ndescription: 'Write SEO blog posts, articles, landing pages with keyword integration, header optimization, and snippet targeting. SEO文章写作\u002F内容优化'\nversion: \"6.0.0\"\nlicense: Apache-2.0\ncompatibility: \"Claude Code ≥1.0, skills.sh marketplace, ClawHub marketplace, Vercel Labs skills ecosystem. No system packages required. Optional: MCP network access for SEO tool integrations.\"\nhomepage: \"https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\"\nwhen_to_use: \"Use when writing SEO-optimized articles, blog posts, landing pages, or product descriptions. Also when the user asks to create content targeting a specific keyword.\"\nargument-hint: \"\u003Ctopic> \u003Ctarget keyword>\"\nmetadata:\n  author: aaron-he-zhu\n  version: \"6.0.0\"\n  geo-relevance: \"medium\"\n  tags:\n    - seo\n    - content-writing\n    - blog-writing\n    - seo-copywriting\n    - content-creation\n    - featured-snippet-optimization\n    - article-writing\n    - landing-page\n    - surferSEO-alternative\n    - clearscope-alternative\n    - SEO文章\n    - 博客写作\n    - SEOライティング\n    - SEO글쓰기\n    - redaccion-seo\n  triggers:\n    # EN-formal\n    - \"write SEO content\"\n    - \"create blog post\"\n    - \"write an article\"\n    - \"content writing\"\n    - \"draft optimized content\"\n    - \"write for SEO\"\n    - \"SEO copywriting\"\n    - \"blog writing\"\n    # EN-casual\n    - \"write me a blog post\"\n    - \"write me an article\"\n    - \"help me write about\"\n    - \"draft an article about\"\n    - \"I need a blog post\"\n    - \"create content for my site\"\n    # EN-question\n    - \"how do I write content that ranks\"\n    - \"how to write SEO friendly content\"\n    - \"what makes content rank well\"\n    # EN-competitor\n    - \"SurferSEO alternative\"\n    - \"Clearscope alternative\"\n    - \"Jasper AI alternative for SEO\"\n    # ZH-pro\n    - \"SEO文章写作\"\n    - \"SEO内容创作\"\n    - \"博客写作\"\n    - \"内容优化\"\n    - \"内容创作\"\n    # ZH-casual\n    - \"帮我写文章\"\n    - \"写一篇博客\"\n    - \"排名上不去\"\n    - \"帮我写SEO文章\"\n    - \"写一篇SEO文章\"\n    # JA\n    - \"SEOライティング\"\n    - \"SEO記事作成\"\n    - \"ブログ記事作成\"\n    - \"SEOコンテンツ\"\n    # KO\n    - \"SEO 글쓰기\"\n    - \"블로그 작성\"\n    - \"SEO 콘텐츠 작성\"\n    - \"블로그 글 작성해줘\"\n    - \"이 주제로 글 써봐\"\n    # ES\n    - \"redacción SEO\"\n    - \"escribir artículo SEO\"\n    - \"contenido optimizado\"\n    # PT\n    - \"redação SEO\"\n    - \"escrever artigo SEO\"\n    # Misspellings\n    - \"SEO copywritting\"\n    - \"writting SEO content\"\n---\n\n# SEO Content Writer\n\n> **[SEO & GEO Skills Library](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills)** · 20 skills for SEO + GEO · [ClawHub](https:\u002F\u002Fclawhub.ai\u002Fu\u002Faaron-he-zhu) · [skills.sh](https:\u002F\u002Fskills.sh\u002Faaron-he-zhu\u002Fseo-geo-claude-skills)\n> **System Mode**: This build skill follows the shared [Skill Contract](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Freferences\u002Fskill-contract.md) and [State Model](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Freferences\u002Fstate-model.md).\n\n\nThis skill creates search-engine-optimized content that ranks well while providing genuine value to readers. It applies proven SEO copywriting techniques, proper keyword integration, and optimal content structure.\n\n**System role**: Build layer skill. It turns briefs and signals into assets that other skills can review, publish, and monitor.\n\n## When This Must Trigger\n\nUse this when the conversation involves any of these situations — even if the user does not use SEO terminology:\n\nUse this whenever the task needs a shippable asset or transformation that should feed directly into quality review, deployment, or monitoring.\n\n- Writing blog posts targeting specific keywords\n- Creating landing pages optimized for search\n- Developing pillar content for topic clusters\n- Writing product descriptions for e-commerce\n- Creating service pages for local SEO\n- Producing how-to guides and tutorials\n- Writing comparison and review articles\n\n## What This Skill Does\n\n1. **Keyword Integration**: Naturally incorporates target and related keywords\n2. **Structure Optimization**: Creates scannable, well-organized content\n3. **Title & Meta Creation**: Writes compelling, click-worthy titles\n4. **Header Optimization**: Uses strategic H1-H6 hierarchy\n5. **Internal Linking**: Suggests relevant internal link opportunities\n6. **Readability Enhancement**: Ensures content is accessible and engaging\n7. **Featured Snippet Optimization**: Formats for SERP feature opportunities\n\n## Quick Start\n\nStart with one of these prompts. Finish with a short handoff summary using the repository format in [Skill Contract](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Freferences\u002Fskill-contract.md).\n\n### Basic Content Creation\n\n```\nWrite an SEO-optimized article about [topic] targeting the keyword [keyword]\n```\n\n```\nCreate a blog post for [topic] with these keywords: [keyword list]\n```\n\n### With Specific Requirements\n\n```\nWrite a 2,000-word guide about [topic] targeting [keyword],\ninclude FAQ section for featured snippets\n```\n\n### Content Briefs\n\n```\nHere's my content brief: [brief]. Write SEO-optimized content following this outline.\n```\n\n## Skill Contract\n\n**Expected output**: a ready-to-use asset or implementation-ready transformation plus a short handoff summary ready for `memory\u002Fcontent\u002F`.\n\n- **Reads**: the brief, target keywords, entity inputs, quality constraints, and prior decisions from [CLAUDE.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002FCLAUDE.md) and the shared [State Model](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Freferences\u002Fstate-model.md) when available.\n- **Writes**: a user-facing content, metadata, or schema deliverable plus a reusable summary that can be stored under `memory\u002Fcontent\u002F`.\n- **Promotes**: approved angles, messaging choices, missing evidence, and publish blockers to `CLAUDE.md`, `memory\u002Fdecisions.md`, and `memory\u002Fopen-loops.md`.\n- **Next handoff**: use the `Next Best Skill` below when the asset is ready for review or deployment.\n\n## Data Sources\n\n> See [CONNECTORS.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002FCONNECTORS.md) for tool category placeholders.\n\n**With ~~SEO tool + ~~search console connected:**\nAutomatically pull keyword metrics (search volume, difficulty, CPC), competitor content analysis (top-ranking pages, content length, common topics), SERP features (featured snippets, PAA questions), and keyword opportunities (related keywords, question-based queries).\n\n**With manual data only:**\nAsk the user to provide:\n1. Target primary keyword and 3-5 secondary keywords\n2. Target audience and search intent (informational\u002Fcommercial\u002Ftransactional)\n3. Target word count and desired tone\n4. Any competitor URLs or content examples to reference\n\nProceed with the full workflow using provided data. Note in the output which metrics are from automated collection vs. user-provided data.\n\n## Instructions\n\nWhen a user requests SEO content:\n\n1. **Gather Requirements**\n\n   Confirm or ask for:\n\n   ```markdown\n   ### Content Requirements\n\n   **Primary Keyword**: [main keyword]\n   **Secondary Keywords**: [2-5 related keywords]\n   **Target Word Count**: [length]\n   **Content Type**: [blog\u002Fguide\u002Flanding page\u002Fetc.]\n   **Target Audience**: [who is this for]\n   **Search Intent**: [informational\u002Fcommercial\u002Ftransactional]\n   **Tone**: [professional\u002Fcasual\u002Ftechnical\u002Ffriendly]\n   **CTA Goal**: [what action should readers take]\n   **Competitor URLs**: [top ranking content to beat]\n   ```\n\n2. **Load CORE-EEAT Quality Constraints**\n\n   Before writing, load content quality standards from the [CORE-EEAT Benchmark](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Freferences\u002Fcore-eeat-benchmark.md):\n\n   ```markdown\n   ### CORE-EEAT Pre-Write Checklist\n\n   **Content Type**: [identified from requirements above]\n   **Loaded Constraints** (high-weight items for this content type):\n\n   Apply these standards while writing:\n\n   | ID | Standard | How to Apply |\n   |----|----------|-------------|\n   | C01 | Intent Alignment | Title promise must match content delivery |\n   | C02 | Direct Answer | Core answer in first 150 words |\n   | C06 | Audience Targeting | State \"this article is for...\" |\n   | C10 | Semantic Closure | Conclusion answers opening question + next steps |\n   | O01 | Heading Hierarchy | H1→H2→H3, no level skipping |\n   | O02 | Summary Box | Include TL;DR or Key Takeaways |\n   | O06 | Section Chunking | Each section single topic; paragraphs 3–5 sentences |\n   | O09 | Information Density | No filler; consistent terminology |\n   | R01 | Data Precision | ≥5 precise numbers with units |\n   | R02 | Citation Density | ≥1 external citation per 500 words |\n   | R04 | Evidence-Claim Mapping | Every claim backed by evidence |\n   | R07 | Entity Precision | Full names for people\u002Forgs\u002Fproducts |\n   | C03 | Query Coverage | Cover ≥3 query variants (synonyms, long-tail) |\n   | O08 | Anchor Navigation | Table of contents with jump links |\n   | O10 | Multimedia Structure | Images\u002Fvideos have captions and carry information |\n   | E07 | Practical Tools | Include downloadable templates, checklists, or calculators |\n\n   _These 16 items apply across all content types. For content-type-specific dimension weights, see the Content-Type Weight Table in [core-eeat-benchmark.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Freferences\u002Fcore-eeat-benchmark.md)._\n   _Full 80-item benchmark: [references\u002Fcore-eeat-benchmark.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Freferences\u002Fcore-eeat-benchmark.md)_\n   _For complete content quality audit: use [content-quality-auditor](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fcross-cutting\u002Fcontent-quality-auditor\u002FSKILL.md)_\n   ```\n\n3. **Research and Plan**\n\n   Before writing:\n\n   ```markdown\n   ### Content Research\n\n   **SERP Analysis**:\n   - Top results format: [what's ranking]\n   - Average word count: [X] words\n   - Common sections: [list]\n   - SERP features: [snippets, PAA, etc.]\n\n   **Keyword Map**:\n   - Primary: [keyword] - use in title, H1, intro, conclusion\n   - Secondary: [keywords] - use in H2s, body paragraphs\n   - LSI\u002FRelated: [terms] - sprinkle naturally throughout\n   - Questions: [PAA questions] - use as H2\u002FH3s or FAQ\n\n   **Content Angle**:\n   [What unique perspective or value will this content provide?]\n   ```\n\n4. **Create Optimized Title**\n\n   ```markdown\n   ### Title Optimization\n\n   **Requirements**:\n   - Include primary keyword (preferably at start)\n   - Under 60 characters for full SERP display\n   - Compelling and click-worthy\n   - Match search intent\n\n   **Title Options**:\n\n   1. [Title option 1] ([X] chars)\n      - Keyword position: [front\u002Fmiddle]\n      - Power words: [list]\n\n   2. [Title option 2] ([X] chars)\n      - Keyword position: [front\u002Fmiddle]\n      - Power words: [list]\n\n   **Recommended**: [Best option with reasoning]\n   ```\n\n5. **Write Meta Description**\n\n   ```markdown\n   ### Meta Description\n\n   **Requirements**:\n   - 150-160 characters\n   - Include primary keyword naturally\n   - Include call-to-action\n   - Compelling and specific\n\n   **Meta Description**:\n   \"[Description text]\" ([X] characters)\n\n   **Elements included**:\n   - ✅ Primary keyword\n   - ✅ Value proposition\n   - ✅ CTA or curiosity hook\n   ```\n\n6. **Structure Content and Write**\n\n   Structure: H1 (primary keyword, one per page) > Introduction (100-150 words, hook + promise + keyword in first 100 words) > H2 sections (secondary keywords\u002Fquestions) > H3 sub-topics > FAQ section > Conclusion (summary + keyword + CTA).\n\n7. **Apply On-Page SEO Best Practices**\n\n   Follow the on-page SEO checklist (keyword placement, content quality, readability, technical elements) and the content writing template (H1 with keyword, hook, sections with H2\u002FH3, FAQ, conclusion with CTA).\n\n   > **Reference**: See [references\u002Fseo-writing-checklist.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fbuild\u002Fseo-content-writer\u002Freferences\u002Fseo-writing-checklist.md) for the full on-page SEO checklist, content writing template, and featured snippet optimization patterns.\n\n   Key requirements while writing:\n   - Primary keyword in title, H1, first 100 words, at least one H2, and conclusion\n   - Paragraphs of 3-5 sentences; varied sentence length; bullet points and bold key phrases\n   - Internal links (2-5) and external authoritative links (2-3)\n   - FAQ section with 40-60 word answers for featured snippet opportunity\n   - Optimize for definition, list, table, and how-to snippets where applicable\n\n8. **Add Internal\u002FExternal Links**\n\n   ```markdown\n   ### Link Recommendations\n\n   **Internal Links** (include 2-5):\n   1. \"[anchor text]\" → [\u002Fyour-page-url] (relevant because: [reason])\n   2. \"[anchor text]\" → [\u002Fyour-page-url] (relevant because: [reason])\n\n   **External Links** (include 2-3 authoritative sources):\n   1. \"[anchor text]\" → [authoritative-source.com] (supports: [claim])\n   2. \"[anchor text]\" → [authoritative-source.com] (supports: [claim])\n   ```\n\n9. **Final SEO Review and CORE-EEAT Self-Check**\n\n    Score content across 10 SEO factors (title, meta description, H1, keyword placement, H2s, internal links, external links, FAQ, readability, word count) and produce an Overall SEO Score out of 10.\n\n    Then verify the 16 CORE-EEAT pre-write constraints (C01, C02, C06, C10, O01, O02, O06, O09, R01, R02, R04, R07, C03, O08, O10, E07) with pass\u002Fwarning\u002Ffail status. List items needing attention.\n\n    _For full 80-item audit, use [content-quality-auditor](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fcross-cutting\u002Fcontent-quality-auditor\u002FSKILL.md)_\n\n#### Issue Classification\n\nWhen the self-check reveals issues, classify and handle them:\n\n**Auto-correct (fix silently, then document in a `### Changes Made` block after the final content):**\n- Meta description exceeds 160 characters → rewrite to fit while preserving primary keyword and CTA\n- Title tag exceeds 60 characters → shorten while preserving primary keyword\n- Missing alt text on images → generate descriptive alt text\n- Duplicate H2 headings → differentiate with modifiers\n- Keyword density above 2% → replace some instances with semantic variants\n- Missing table of contents → generate TOC with anchor links for articles with 3+ H2 sections\n- Paragraphs exceeding 5 sentences → split at the most natural break point\n\nUse this format for the Changes Made block:\n\n```markdown\n### Changes Made During Self-Check\n\n| Item | Original | Fixed |\n|------|----------|-------|\n| Meta description | 185 chars | 158 chars — removed non-essential qualifier |\n| Keyword density | 2.4% | 1.8% — replaced 3 instances with semantic variants |\n```\n\n**Needs your decision (ask before changing):**\n- H1 wording changes (may affect brand voice)\n- Keyword density below 0.5% (may need structural rewrite)\n- Tone adjustments (formal ↔ casual)\n- Claim strength (e.g., \"best\" → \"top-rated\" for compliance)\n- Content length significantly above\u002Fbelow target (±30%)\n- Removing\u002Freplacing external links\n- Statistics or data claims that cannot be verified against the cited source\n\n## Validation Checkpoints\n\n### Input Validation\n- [ ] Primary keyword confirmed and matches search intent\n- [ ] Target word count specified (minimum 800 words for substantive content)\n- [ ] Content type and audience clearly defined\n- [ ] Competitor URLs reviewed or target SERP features identified\n\n### Output Validation\n- [ ] Keyword density within 1-2% for primary keyword (Note: Keyword density is a guideline, not a hard rule. Modern search engines prioritize semantic relevance and natural language over exact density targets. Focus on covering the topic comprehensively with semantic variants rather than hitting a specific percentage.)\n- [ ] All sections from outline covered completely\n- [ ] Internal links included (2-5 relevant links)\n- [ ] FAQ section present with at least 3 questions\n- [ ] Readability score appropriate for target audience\n- [ ] Source of each data point clearly stated (~~SEO tool data, user-provided, or estimated)\n\n## Example\n\n**User**: \"Write an SEO-optimized article about 'email marketing best practices' targeting small businesses\"\n\n> **Reference**: See [references\u002Fseo-writing-checklist.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fbuild\u002Fseo-content-writer\u002Freferences\u002Fseo-writing-checklist.md) for the full example output demonstrating a complete SEO article with meta description, H1\u002FH2\u002FH3 hierarchy, statistics with citations, comparison tables, FAQ section, and conclusion with CTA.\n\nThe example output demonstrates: keyword in H1 and first 100 words, statistics with sources (DMA, Emarsys), comparison tables, bullet-point lists, pro tips, FAQ section with 40-60 word answers, and a clear CTA in the conclusion.\n\n## Content Type Templates\n\n### How-To Guide\n\n```\nWrite a how-to guide for [task] targeting [keyword]\n```\n\n### Comparison Article\n\n```\nWrite a comparison article: [Option A] vs [Option B] for [keyword]\n```\n\n### Listicle\n\n```\nWrite a list post: \"X Best [Items] for [Audience\u002FPurpose]\" targeting [keyword]\n```\n\n### Ultimate Guide\n\n```\nWrite an ultimate guide about [topic] (3,000+ words) targeting [keyword]\n```\n\n## Tips for Success\n\n1. **Match search intent** - Informational queries need guides, not sales pages\n2. **Front-load value** - Put key information early for readers and snippets\n3. **Use data and examples** - Specific beats generic every time\n4. **Write for humans first** - SEO optimization should feel natural\n5. **Include visual elements** - Break up text with images, tables, lists\n6. **Update regularly** - Fresh content signals to search engines\n\n\n### Save Results\n\nAfter delivering content or optimization output to the user, ask:\n\n> \"Save these results for future sessions?\"\n\nIf yes, write a dated summary to `memory\u002Fcontent\u002FYYYY-MM-DD-\u003Ctopic>.md` containing:\n- One-line description of what was created\n- Target keyword and content type\n- Open loops or items needing review\n- Source data references\n\n**Gate check recommended**: Run content-quality-auditor before publishing (PostToolUse hook will remind automatically).\n\nIf any findings should influence ongoing strategy, recommend promoting key conclusions to `memory\u002Fhot-cache.md`.\n\n## Reference Materials\n\n- [Title Formulas](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fbuild\u002Fseo-content-writer\u002Freferences\u002Ftitle-formulas.md) - Proven headline formulas, power words, CTR patterns\n- [Content Structure Templates](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fbuild\u002Fseo-content-writer\u002Freferences\u002Fcontent-structure-templates.md) - Templates for blog posts, comparisons, listicles, how-tos, pillar pages\n\n## Next Best Skill\n\n- **Primary**: [content-quality-auditor](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fcross-cutting\u002Fcontent-quality-auditor\u002FSKILL.md) — gate the draft before publishing or handing it off.\n","# SEO Content Writer\n\n> **[SEO & GEO Skills Library](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills)** · 20 skills for SEO + GEO · [ClawHub](https:\u002F\u002Fclawhub.ai\u002Fu\u002Faaron-he-zhu) · [skills.sh](https:\u002F\u002Fskills.sh\u002Faaron-he-zhu\u002Fseo-geo-claude-skills)\n> **System Mode**: This build skill follows the shared [Skill Contract](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Freferences\u002Fskill-contract.md) and [State Model](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Freferences\u002Fstate-model.md).\n\n\nThis skill creates search-engine-optimized content that ranks well while providing genuine value to readers. It applies proven SEO copywriting techniques, proper keyword integration, and optimal content structure.\n\n**System role**: Build layer skill. It turns briefs and signals into assets that other skills can review, publish, and monitor.\n\n## When This Must Trigger\n\nUse this when the conversation involves any of these situations — even if the user does not use SEO terminology:\n\nUse this whenever the task needs a shippable asset or transformation that should feed directly into quality review, deployment, or monitoring.\n\n- Writing blog posts targeting specific keywords\n- Creating landing pages optimized for search\n- Developing pillar content for topic clusters\n- Writing product descriptions for e-commerce\n- Creating service pages for local SEO\n- Producing how-to guides and tutorials\n- Writing comparison and review articles\n\n## What This Skill Does\n\n1. **Keyword Integration**: Naturally incorporates target and related keywords\n2. **Structure Optimization**: Creates scannable, well-organized content\n3. **Title & Meta Creation**: Writes compelling, click-worthy titles\n4. **Header Optimization**: Uses strategic H1-H6 hierarchy\n5. **Internal Linking**: Suggests relevant internal link opportunities\n6. **Readability Enhancement**: Ensures content is accessible and engaging\n7. **Featured Snippet Optimization**: Formats for SERP feature opportunities\n\n## Quick Start\n\nStart with one of these prompts. Finish with a short handoff summary using the repository format in [Skill Contract](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Freferences\u002Fskill-contract.md).\n\n### Basic Content Creation\n\n```\nWrite an SEO-optimized article about [topic] targeting the keyword [keyword]\n```\n\n```\nCreate a blog post for [topic] with these keywords: [keyword list]\n```\n\n### With Specific Requirements\n\n```\nWrite a 2,000-word guide about [topic] targeting [keyword],\ninclude FAQ section for featured snippets\n```\n\n### Content Briefs\n\n```\nHere's my content brief: [brief]. Write SEO-optimized content following this outline.\n```\n\n## Skill Contract\n\n**Expected output**: a ready-to-use asset or implementation-ready transformation plus a short handoff summary ready for `memory\u002Fcontent\u002F`.\n\n- **Reads**: the brief, target keywords, entity inputs, quality constraints, and prior decisions from [CLAUDE.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002FCLAUDE.md) and the shared [State Model](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Freferences\u002Fstate-model.md) when available.\n- **Writes**: a user-facing content, metadata, or schema deliverable plus a reusable summary that can be stored under `memory\u002Fcontent\u002F`.\n- **Promotes**: approved angles, messaging choices, missing evidence, and publish blockers to `CLAUDE.md`, `memory\u002Fdecisions.md`, and `memory\u002Fopen-loops.md`.\n- **Next handoff**: use the `Next Best Skill` below when the asset is ready for review or deployment.\n\n## Data Sources\n\n> See [CONNECTORS.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002FCONNECTORS.md) for tool category placeholders.\n\n**With ~~SEO tool + ~~search console connected:**\nAutomatically pull keyword metrics (search volume, difficulty, CPC), competitor content analysis (top-ranking pages, content length, common topics), SERP features (featured snippets, PAA questions), and keyword opportunities (related keywords, question-based queries).\n\n**With manual data only:**\nAsk the user to provide:\n1. Target primary keyword and 3-5 secondary keywords\n2. Target audience and search intent (informational\u002Fcommercial\u002Ftransactional)\n3. Target word count and desired tone\n4. Any competitor URLs or content examples to reference\n\nProceed with the full workflow using provided data. Note in the output which metrics are from automated collection vs. user-provided data.\n\n## Instructions\n\nWhen a user requests SEO content:\n\n1. **Gather Requirements**\n\n   Confirm or ask for:\n\n   ```markdown\n   ### Content Requirements\n\n   **Primary Keyword**: [main keyword]\n   **Secondary Keywords**: [2-5 related keywords]\n   **Target Word Count**: [length]\n   **Content Type**: [blog\u002Fguide\u002Flanding page\u002Fetc.]\n   **Target Audience**: [who is this for]\n   **Search Intent**: [informational\u002Fcommercial\u002Ftransactional]\n   **Tone**: [professional\u002Fcasual\u002Ftechnical\u002Ffriendly]\n   **CTA Goal**: [what action should readers take]\n   **Competitor URLs**: [top ranking content to beat]\n   ```\n\n2. **Load CORE-EEAT Quality Constraints**\n\n   Before writing, load content quality standards from the [CORE-EEAT Benchmark](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Freferences\u002Fcore-eeat-benchmark.md):\n\n   ```markdown\n   ### CORE-EEAT Pre-Write Checklist\n\n   **Content Type**: [identified from requirements above]\n   **Loaded Constraints** (high-weight items for this content type):\n\n   Apply these standards while writing:\n\n   | ID | Standard | How to Apply |\n   |----|----------|-------------|\n   | C01 | Intent Alignment | Title promise must match content delivery |\n   | C02 | Direct Answer | Core answer in first 150 words |\n   | C06 | Audience Targeting | State \"this article is for...\" |\n   | C10 | Semantic Closure | Conclusion answers opening question + next steps |\n   | O01 | Heading Hierarchy | H1→H2→H3, no level skipping |\n   | O02 | Summary Box | Include TL;DR or Key Takeaways |\n   | O06 | Section Chunking | Each section single topic; paragraphs 3–5 sentences |\n   | O09 | Information Density | No filler; consistent terminology |\n   | R01 | Data Precision | ≥5 precise numbers with units |\n   | R02 | Citation Density | ≥1 external citation per 500 words |\n   | R04 | Evidence-Claim Mapping | Every claim backed by evidence |\n   | R07 | Entity Precision | Full names for people\u002Forgs\u002Fproducts |\n   | C03 | Query Coverage | Cover ≥3 query variants (synonyms, long-tail) |\n   | O08 | Anchor Navigation | Table of contents with jump links |\n   | O10 | Multimedia Structure | Images\u002Fvideos have captions and carry information |\n   | E07 | Practical Tools | Include downloadable templates, checklists, or calculators |\n\n   _These 16 items apply across all content types. For content-type-specific dimension weights, see the Content-Type Weight Table in [core-eeat-benchmark.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Freferences\u002Fcore-eeat-benchmark.md)._\n   _Full 80-item benchmark: [references\u002Fcore-eeat-benchmark.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Freferences\u002Fcore-eeat-benchmark.md)_\n   _For complete content quality audit: use [content-quality-auditor](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fcross-cutting\u002Fcontent-quality-auditor\u002FSKILL.md)_\n   ```\n\n3. **Research and Plan**\n\n   Before writing:\n\n   ```markdown\n   ### Content Research\n\n   **SERP Analysis**:\n   - Top results format: [what's ranking]\n   - Average word count: [X] words\n   - Common sections: [list]\n   - SERP features: [snippets, PAA, etc.]\n\n   **Keyword Map**:\n   - Primary: [keyword] - use in title, H1, intro, conclusion\n   - Secondary: [keywords] - use in H2s, body paragraphs\n   - LSI\u002FRelated: [terms] - sprinkle naturally throughout\n   - Questions: [PAA questions] - use as H2\u002FH3s or FAQ\n\n   **Content Angle**:\n   [What unique perspective or value will this content provide?]\n   ```\n\n4. **Create Optimized Title**\n\n   ```markdown\n   ### Title Optimization\n\n   **Requirements**:\n   - Include primary keyword (preferably at start)\n   - Under 60 characters for full SERP display\n   - Compelling and click-worthy\n   - Match search intent\n\n   **Title Options**:\n\n   1. [Title option 1] ([X] chars)\n      - Keyword position: [front\u002Fmiddle]\n      - Power words: [list]\n\n   2. [Title option 2] ([X] chars)\n      - Keyword position: [front\u002Fmiddle]\n      - Power words: [list]\n\n   **Recommended**: [Best option with reasoning]\n   ```\n\n5. **Write Meta Description**\n\n   ```markdown\n   ### Meta Description\n\n   **Requirements**:\n   - 150-160 characters\n   - Include primary keyword naturally\n   - Include call-to-action\n   - Compelling and specific\n\n   **Meta Description**:\n   \"[Description text]\" ([X] characters)\n\n   **Elements included**:\n   - ✅ Primary keyword\n   - ✅ Value proposition\n   - ✅ CTA or curiosity hook\n   ```\n\n6. **Structure Content and Write**\n\n   Structure: H1 (primary keyword, one per page) > Introduction (100-150 words, hook + promise + keyword in first 100 words) > H2 sections (secondary keywords\u002Fquestions) > H3 sub-topics > FAQ section > Conclusion (summary + keyword + CTA).\n\n7. **Apply On-Page SEO Best Practices**\n\n   Follow the on-page SEO checklist (keyword placement, content quality, readability, technical elements) and the content writing template (H1 with keyword, hook, sections with H2\u002FH3, FAQ, conclusion with CTA).\n\n   > **Reference**: See [references\u002Fseo-writing-checklist.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fbuild\u002Fseo-content-writer\u002Freferences\u002Fseo-writing-checklist.md) for the full on-page SEO checklist, content writing template, and featured snippet optimization patterns.\n\n   Key requirements while writing:\n   - Primary keyword in title, H1, first 100 words, at least one H2, and conclusion\n   - Paragraphs of 3-5 sentences; varied sentence length; bullet points and bold key phrases\n   - Internal links (2-5) and external authoritative links (2-3)\n   - FAQ section with 40-60 word answers for featured snippet opportunity\n   - Optimize for definition, list, table, and how-to snippets where applicable\n\n8. **Add Internal\u002FExternal Links**\n\n   ```markdown\n   ### Link Recommendations\n\n   **Internal Links** (include 2-5):\n   1. \"[anchor text]\" → [\u002Fyour-page-url] (relevant because: [reason])\n   2. \"[anchor text]\" → [\u002Fyour-page-url] (relevant because: [reason])\n\n   **External Links** (include 2-3 authoritative sources):\n   1. \"[anchor text]\" → [authoritative-source.com] (supports: [claim])\n   2. \"[anchor text]\" → [authoritative-source.com] (supports: [claim])\n   ```\n\n9. **Final SEO Review and CORE-EEAT Self-Check**\n\n    Score content across 10 SEO factors (title, meta description, H1, keyword placement, H2s, internal links, external links, FAQ, readability, word count) and produce an Overall SEO Score out of 10.\n\n    Then verify the 16 CORE-EEAT pre-write constraints (C01, C02, C06, C10, O01, O02, O06, O09, R01, R02, R04, R07, C03, O08, O10, E07) with pass\u002Fwarning\u002Ffail status. List items needing attention.\n\n    _For full 80-item audit, use [content-quality-auditor](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fcross-cutting\u002Fcontent-quality-auditor\u002FSKILL.md)_\n\n#### Issue Classification\n\nWhen the self-check reveals issues, classify and handle them:\n\n**Auto-correct (fix silently, then document in a `### Changes Made` block after the final content):**\n- Meta description exceeds 160 characters → rewrite to fit while preserving primary keyword and CTA\n- Title tag exceeds 60 characters → shorten while preserving primary keyword\n- Missing alt text on images → generate descriptive alt text\n- Duplicate H2 headings → differentiate with modifiers\n- Keyword density above 2% → replace some instances with semantic variants\n- Missing table of contents → generate TOC with anchor links for articles with 3+ H2 sections\n- Paragraphs exceeding 5 sentences → split at the most natural break point\n\nUse this format for the Changes Made block:\n\n```markdown\n### Changes Made During Self-Check\n\n| Item | Original | Fixed |\n|------|----------|-------|\n| Meta description | 185 chars | 158 chars — removed non-essential qualifier |\n| Keyword density | 2.4% | 1.8% — replaced 3 instances with semantic variants |\n```\n\n**Needs your decision (ask before changing):**\n- H1 wording changes (may affect brand voice)\n- Keyword density below 0.5% (may need structural rewrite)\n- Tone adjustments (formal ↔ casual)\n- Claim strength (e.g., \"best\" → \"top-rated\" for compliance)\n- Content length significantly above\u002Fbelow target (±30%)\n- Removing\u002Freplacing external links\n- Statistics or data claims that cannot be verified against the cited source\n\n## Validation Checkpoints\n\n### Input Validation\n- [ ] Primary keyword confirmed and matches search intent\n- [ ] Target word count specified (minimum 800 words for substantive content)\n- [ ] Content type and audience clearly defined\n- [ ] Competitor URLs reviewed or target SERP features identified\n\n### Output Validation\n- [ ] Keyword density within 1-2% for primary keyword (Note: Keyword density is a guideline, not a hard rule. Modern search engines prioritize semantic relevance and natural language over exact density targets. Focus on covering the topic comprehensively with semantic variants rather than hitting a specific percentage.)\n- [ ] All sections from outline covered completely\n- [ ] Internal links included (2-5 relevant links)\n- [ ] FAQ section present with at least 3 questions\n- [ ] Readability score appropriate for target audience\n- [ ] Source of each data point clearly stated (~~SEO tool data, user-provided, or estimated)\n\n## Example\n\n**User**: \"Write an SEO-optimized article about 'email marketing best practices' targeting small businesses\"\n\n> **Reference**: See [references\u002Fseo-writing-checklist.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fbuild\u002Fseo-content-writer\u002Freferences\u002Fseo-writing-checklist.md) for the full example output demonstrating a complete SEO article with meta description, H1\u002FH2\u002FH3 hierarchy, statistics with citations, comparison tables, FAQ section, and conclusion with CTA.\n\nThe example output demonstrates: keyword in H1 and first 100 words, statistics with sources (DMA, Emarsys), comparison tables, bullet-point lists, pro tips, FAQ section with 40-60 word answers, and a clear CTA in the conclusion.\n\n## Content Type Templates\n\n### How-To Guide\n\n```\nWrite a how-to guide for [task] targeting [keyword]\n```\n\n### Comparison Article\n\n```\nWrite a comparison article: [Option A] vs [Option B] for [keyword]\n```\n\n### Listicle\n\n```\nWrite a list post: \"X Best [Items] for [Audience\u002FPurpose]\" targeting [keyword]\n```\n\n### Ultimate Guide\n\n```\nWrite an ultimate guide about [topic] (3,000+ words) targeting [keyword]\n```\n\n## Tips for Success\n\n1. **Match search intent** - Informational queries need guides, not sales pages\n2. **Front-load value** - Put key information early for readers and snippets\n3. **Use data and examples** - Specific beats generic every time\n4. **Write for humans first** - SEO optimization should feel natural\n5. **Include visual elements** - Break up text with images, tables, lists\n6. **Update regularly** - Fresh content signals to search engines\n\n\n### Save Results\n\nAfter delivering content or optimization output to the user, ask:\n\n> \"Save these results for future sessions?\"\n\nIf yes, write a dated summary to `memory\u002Fcontent\u002FYYYY-MM-DD-\u003Ctopic>.md` containing:\n- One-line description of what was created\n- Target keyword and content type\n- Open loops or items needing review\n- Source data references\n\n**Gate check recommended**: Run content-quality-auditor before publishing (PostToolUse hook will remind automatically).\n\nIf any findings should influence ongoing strategy, recommend promoting key conclusions to `memory\u002Fhot-cache.md`.\n\n## Reference Materials\n\n- [Title Formulas](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fbuild\u002Fseo-content-writer\u002Freferences\u002Ftitle-formulas.md) - Proven headline formulas, power words, CTR patterns\n- [Content Structure Templates](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fbuild\u002Fseo-content-writer\u002Freferences\u002Fcontent-structure-templates.md) - Templates for blog posts, comparisons, listicles, how-tos, pillar pages\n\n## Next Best Skill\n\n- **Primary**: [content-quality-auditor](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fcross-cutting\u002Fcontent-quality-auditor\u002FSKILL.md) — gate the draft before publishing or handing it off.\n",{"name":5,"license":14,"version":23,"homepage":24,"metadata":25,"description":7,"when_to_use":89,"argument-hint":90,"compatibility":91},"6.0.0","https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills",{"tags":26,"author":42,"version":23,"triggers":43,"geo-relevance":88},[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"seo","content-writing","blog-writing","seo-copywriting","content-creation","featured-snippet-optimization","article-writing","landing-page","surferSEO-alternative","clearscope-alternative","SEO文章","博客写作","SEOライティング","SEO글쓰기","redaccion-seo","aaron-he-zhu",[44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,38,66,67,68,69,70,71,72,39,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87],"write SEO content","create blog post","write an article","content writing","draft optimized content","write for SEO","SEO copywriting","blog writing","write me a blog post","write me an article","help me write about","draft an article about","I need a blog post","create content for my site","how do I write content that ranks","how to write SEO friendly content","what makes content rank well","SurferSEO alternative","Clearscope alternative","Jasper AI alternative for SEO","SEO文章写作","SEO内容创作","内容优化","内容创作","帮我写文章","写一篇博客","排名上不去","帮我写SEO文章","写一篇SEO文章","SEO記事作成","ブログ記事作成","SEOコンテンツ","SEO 글쓰기","블로그 작성","SEO 콘텐츠 작성","블로그 글 작성해줘","이 주제로 글 써봐","redacción SEO","escribir artículo SEO","contenido optimizado","redação SEO","escrever artigo SEO","SEO copywritting","writting SEO content","medium","Use when writing SEO-optimized articles, blog posts, landing pages, or product descriptions. Also when the user asks to create content targeting a specific keyword.","\u003Ctopic> \u003Ctarget keyword>","Claude Code ≥1.0, skills.sh marketplace, ClawHub marketplace, Vercel Labs skills ecosystem. No system packages required. Optional: MCP network access for SEO tool integrations.","main","e0ec177d00f087cb04e90206b2f7d3aa2f5a1350","References\u002FAgent\u002FMemory\u002FSurfSense\u002F.cursor\u002Fskills\u002Fseo-content-writer","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim","https:\u002F\u002Fgithub.com\u002Flzy18001500226","2026-08-31 23:29:00",{"source":8,"skillName":5,"commands":99,"prompt":109,"zipAvailable":110},[100,103,106],{"tool":101,"command":102},"npx","npx skills add lzy18001500226\u002FMoSim --skill seo-content-writer",{"tool":104,"command":105},"bunx","bunx skills add lzy18001500226\u002FMoSim --skill seo-content-writer",{"tool":107,"command":108},"pnpm","pnpm dlx skills add lzy18001500226\u002FMoSim --skill seo-content-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FMemory\u002FSurfSense\u002F.cursor\u002Fskills\u002Fseo-content-writer\u002FSKILL.md",true,[112,118,122],{"path":113,"resourceType":114,"resourceTypeDesc":115,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002Fcontent-structure-templates.md","REFERENCE","参考文档",17653,"https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FMemory\u002FSurfSense\u002F.cursor\u002Fskills\u002Fseo-content-writer\u002Freferences\u002Fcontent-structure-templates.md",{"path":119,"resourceType":114,"resourceTypeDesc":115,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Fseo-writing-checklist.md",7786,"https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FMemory\u002FSurfSense\u002F.cursor\u002Fskills\u002Fseo-content-writer\u002Freferences\u002Fseo-writing-checklist.md",{"path":123,"resourceType":114,"resourceTypeDesc":115,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Ftitle-formulas.md",10400,"https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FMemory\u002FSurfSense\u002F.cursor\u002Fskills\u002Fseo-content-writer\u002Freferences\u002Ftitle-formulas.md",[127,136,144,152,160,168],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":131,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":135},"01M78RK6JGRPTD3TDSMTQWDQ9P","skill-installer","Install Codex skills into $CODEX_HOME\u002Fskills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-installer\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-installer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":140,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":135},"01M78RK29KVRDQXSMVZX1GQTJN","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-creator\u002Flicense.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":148,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":135},"01M78RJPF3210Y5DA9VJ6JMMG6","openai-docs","Use for Codex models\u002Fpricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs\u002Fproducts and ChatGPT Work. Also use for model choice\u002Fmigration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat\u002FWork\u002FCodex comparisons. Do not use for generic app\u002Fsoftware tasks that merely mention Codex.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fopenai-docs\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fopenai-docs\u002FSKILL.md",[],[],{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":156,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":135},"01M78RJH7X67C5AY8ZVS7RQNWJ","imagegen","Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG\u002Fvector\u002Fcode-native assets, extending an established icon or logo system, or building the visual directly in HTML\u002FCSS\u002Fcanvas.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fimagegen\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fimagegen\u002FSKILL.md",[],[],{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":164,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":135},"01M78RBBAYMJ6T3ZMAYHCFM6G7","skill-creator-cc","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fskill-creator-cc\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fskill-creator-cc\u002FSKILL.md",[],[],{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":172,"licenseFileUrl":173,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":177},"01M76VV9V2R9FZTVGMJZV7Y996","prd-writing-guide","Write complete, unambiguous PRDs that development teams can implement without guesswork. Includes requirement discovery framework, structured documentation methodology, completeness checklists, and common pitfall avoidance. Use when: writing new PRDs, reviewing PRD drafts, validating requirement completeness, preparing for engineering handoff. Triggers: 'write PRD', '写PRD', '产品需求文档', '需求文档', '需求规格', '需求评审', '完善需求', 'create requirements doc', 'product requirements', 'feature spec', 'requirements document'. Anti-triggers: 'technical design doc', 'architecture design', 'implementation plan', 'API design', '架构设计', '技术方案', '实现方案', '接口设计'.","MIT","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fprd-writing-guide\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fprd-writing-guide\u002FSKILL.md",[],[],"2026-11-12 13:55:43"]