[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74ESY3B49B6NQ2XC780MYAW":3,"skill-same:01M74ESY3B49B6NQ2XC780MYAW":100},{"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":74,"commitSha":75,"skillDirectory":76,"forksCount":13,"repositoryHtmlUrl":77,"repositoryHomepageUrl":6,"ownerHtmlUrl":78,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":79,"install":80,"resources":93},"01M74ESY3B49B6NQ2XC780MYAW","content-quality-auditor",null,"Publish-readiness gate: 80-item CORE-EEAT audit with weighted scoring, veto checks, and fix plan. 内容质量\u002FEEAT评分","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\u002Fcontent-quality-auditor\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: content-quality-auditor\ndescription: 'Publish-readiness gate: 80-item CORE-EEAT audit with weighted scoring, veto checks, and fix plan. 内容质量\u002FEEAT评分'\nversion: \"6.0.0\"\nlicense: Apache-2.0\nallowed-tools: WebFetch\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 auditing content quality before publishing. Runs CORE-EEAT 80-item scoring with veto checks. Also when the user asks for E-E-A-T analysis or publish readiness.\"\nargument-hint: \"\u003CURL or paste content> [keyword]\"\nmetadata:\n  author: aaron-he-zhu\n  version: \"6.0.0\"\n  geo-relevance: \"high\"\n  tags:\n    - seo\n    - geo\n    - e-e-a-t\n    - core-eeat\n    - content-quality\n    - content-scoring\n    - helpful-content\n    - publish-readiness\n    - 内容质量\n    - コンテンツ品質\n    - 콘텐츠품질\n    - auditoria-eeat\n  triggers:\n    # EN-formal\n    - \"audit content quality\"\n    - \"EEAT score\"\n    - \"CORE-EEAT audit\"\n    - \"content quality check\"\n    - \"content assessment\"\n    - \"quality score\"\n    # EN-casual\n    - \"is this ready to publish\"\n    - \"grade my article\"\n    - \"check before publishing\"\n    - \"how good is my content\"\n    - \"is my content good enough to rank\"\n    - \"rate my content quality\"\n    # EN-question\n    - \"is my content ready to publish\"\n    - \"how do I improve content quality\"\n    # ZH-pro\n    - \"内容质量审计\"\n    - \"EEAT评分\"\n    - \"内容评估\"\n    # ZH-casual\n    - \"文章能发吗\"\n    - \"内容打几分\"\n    - \"文章写得怎么样\"\n    # JA\n    - \"コンテンツ品質監査\"\n    - \"E-E-A-T評価\"\n    # KO\n    - \"콘텐츠 품질 감사\"\n    - \"EEAT 점수\"\n    # ES\n    - \"auditoría de calidad de contenido\"\n    - \"puntuación EEAT\"\n    # PT\n    - \"auditoria de qualidade\"\n    # Misspellings\n    - \"EEAT scroe\"\n---\n\n# Content Quality Auditor\n\n> Based on [CORE-EEAT Content Benchmark](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fcore-eeat-content-benchmark). Full benchmark reference: [references\u002Fcore-eeat-benchmark.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Freferences\u002Fcore-eeat-benchmark.md)\n\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 cross-cutting skill is part of the protocol layer and 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 evaluates content quality across 80 standardized criteria organized in 8 dimensions. It produces a comprehensive audit report with per-item scoring, dimension and system scores, weighted totals by content type, and a prioritized action plan.\n\n**System role**: Publish Readiness Gate. It decides whether content is ready to ship, what blocks publication, and what should be promoted into durable project memory.\n\n## When This Must Trigger\n\nUse this when content needs a quality check before publishing — even if the user doesn't use audit terminology:\n\n- User asks \"is this ready to publish\" or \"how good is this\"\n- User just finished writing with seo-content-writer or content-refresher\n- **PostToolUse hook auto-triggers**: after content is written or substantially edited, the hook recommends this audit. When hook-triggered, skip setup questions — audit the content that was just produced.\n- Auditing content quality before publishing\n- Evaluating existing content for improvement opportunities\n- Benchmarking content against CORE-EEAT standards\n- Comparing content quality against competitors\n- Assessing both GEO readiness (AI citation potential) and SEO strength (source credibility)\n- Running periodic content quality checks as part of a content maintenance program\n- After writing or optimizing content with seo-content-writer or geo-content-optimizer\n\n## What This Skill Does\n\n1. **Full 80-Item Audit**: Scores every CORE-EEAT check item as Pass\u002FPartial\u002FFail\n2. **Dimension Scoring**: Calculates scores for all 8 dimensions (0-100 each)\n3. **System Scoring**: Computes GEO Score (CORE) and SEO Score (EEAT)\n4. **Weighted Totals**: Applies content-type-specific weights for final score\n5. **Veto Detection**: Flags critical trust violations (T04, C01, R10)\n6. **Priority Ranking**: Identifies Top 5 improvements sorted by impact\n7. **Action Plan**: Generates specific, actionable improvement steps\n\n## Quick Start\n\nStart with one of these prompts. Finish with a publish verdict and a 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### Audit Content\n\n```\nAudit this content against CORE-EEAT: [content text or URL]\n```\n\n```\nRun a content quality audit on [URL] as a [content type]\n```\n\n### Audit with Content Type\n\n```\nCORE-EEAT audit for this product review: [content]\n```\n\n```\nScore this how-to guide against the 80-item benchmark: [content]\n```\n\n### Comparative Audit\n\n```\nAudit my content vs competitor: [your content] vs [competitor content]\n```\n\n## Skill Contract\n\n**Gate verdict**: **SHIP** (no veto items, dimension scores above threshold) \u002F **FIX** (issues found but no veto) \u002F **BLOCK** (veto item T04, C01, or R10 failed). Always state the verdict prominently at the top of the report.\n\n**Expected output**: a CORE-EEAT audit report, a publish-readiness verdict, and a short handoff summary ready for `memory\u002Faudits\u002Fcontent\u002F`.\n\n- **Reads**: the target content, content type, supporting evidence, and any 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 audit report plus a reusable summary that can be stored under `memory\u002Faudits\u002Fcontent\u002F`.\n- **Promotes**: veto items and publish blockers to `memory\u002Fhot-cache.md` (auto-saved, no user confirmation needed). Top improvement priorities to `memory\u002Fopen-loops.md`.\n- **Next handoff**: use the `Next Best Skill` below once the verdict is clear.\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 ~~web crawler + ~~SEO tool connected:**\nAutomatically fetch page content, extract HTML structure, check schema markup, verify internal\u002Fexternal links, and pull competitor content for comparison.\n\n**With manual data only:**\nAsk the user to provide:\n1. Content text, URL, or file path\n2. Content type (if not auto-detectable): Product Review, How-to Guide, Comparison, Landing Page, Blog Post, FAQ Page, Alternative, Best-of, or Testimonial\n3. Optional: competitor content for benchmarking\n\nProceed with the full 80-item audit using provided data. Note in the output which items could not be fully evaluated due to missing access (e.g., backlink data, schema markup, site-level signals).\n\n## Decision Gates\n\nWhen stopping to ask, always: (1) state the specific value and threshold, (2) offer numbered options with outcomes.\n\n**Stop and ask the user when:**\n- Content is under minimum word count for its type (blog\u002Fguide: 300 words; product\u002Flanding page: 150 words; FAQ: fewer than 3 entries with 50+ words each) — state the actual count and offer: (1) expand to minimum, (2) continue audit with Insufficient Data flags, (3) cancel\n- Content type cannot be auto-detected — state what you detected and ask to confirm before proceeding\n- Content is primarily media (video\u002Fimage) with minimal text — ask whether to audit transcript, alt text, or skip\n- More than 50% of a dimension's items are N\u002FA — name the dimension and ask: (1) provide supplementary data, (2) mark entire dimension as Insufficient Data\n- Any veto item triggers — flag it immediately with the item ID and ask: (1) stop for immediate fix, (2) continue full audit and flag in report\n\n**Continue silently (never stop for):**\n- Individual Partial scores within a dimension\n- Missing SEO tool data (mark items as N\u002FA and continue)\n- Low overall score (the report is the deliverable, not a judgment call)\n- User not specifying content type (auto-detect and state your assumption)\n\n## Instructions\n\nWhen a user requests a content quality audit:\n\n### Step 1: Preparation\n\n```markdown\n### Audit Setup\n\n**Content**: [title or URL]\n**Content Type**: [auto-detected or user-specified]\n**Dimension Weights**: [loaded from content-type weight table]\n\n#### Veto Check (Emergency Brake)\n\n| Veto Item | Status | Action |\n|-----------|--------|--------|\n| T04: Disclosure Statements | ✅ Pass \u002F ⚠️ VETO | [If VETO: \"Add disclosure banner at page top immediately\"] |\n| C01: Intent Alignment | ✅ Pass \u002F ⚠️ VETO | [If VETO: \"Rewrite title and first paragraph\"] |\n| R10: Content Consistency | ✅ Pass \u002F ⚠️ VETO | [If VETO: \"Verify all data before publishing\"] |\n```\n\nIf any veto item triggers, flag it prominently at the top of the report and recommend immediate action before continuing the full audit.\n\n### Step 2: CORE Audit (40 items)\n\nEvaluate each item against the criteria in [references\u002Fcore-eeat-benchmark.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Freferences\u002Fcore-eeat-benchmark.md).\n\nScore each item:\n- **Pass** = 10 points (fully meets criteria)\n- **Partial** = 5 points (partially meets criteria)\n- **Fail** = 0 points (does not meet criteria)\n\n```markdown\n### C — Contextual Clarity\n\n| ID | Check Item | Score | Notes |\n|----|-----------|-------|-------|\n| C01 | Intent Alignment | Pass\u002FPartial\u002FFail | [specific observation] |\n| C02 | Direct Answer | Pass\u002FPartial\u002FFail | [specific observation] |\n| ... | ... | ... | ... |\n| C10 | Semantic Closure | Pass\u002FPartial\u002FFail | [specific observation] |\n\n**C Score**: [X]\u002F100\n```\n\nRepeat the same table format for **O** (Organization), **R** (Referenceability), and **E** (Exclusivity), scoring all 10 items per dimension.\n\n### Step 3: EEAT Audit (40 items)\n\n```markdown\n### Exp — Experience\n\n| ID | Check Item | Score | Notes |\n|----|-----------|-------|-------|\n| Exp01 | First-Person Narrative | Pass\u002FPartial\u002FFail | [specific observation] |\n| ... | ... | ... | ... |\n\n**Exp Score**: [X]\u002F100\n```\n\nRepeat the same table format for **Ept** (Expertise), **A** (Authority), and **T** (Trust), scoring all 10 items per dimension.\n\nSee [references\u002Fitem-reference.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fcross-cutting\u002Fcontent-quality-auditor\u002Freferences\u002Fitem-reference.md) for the complete 80-item ID lookup table and site-level item handling notes.\n\n### Step 4: Scoring & Report\n\nCalculate scores and generate the final report:\n\n```markdown\n## CORE-EEAT Audit Report\n\n### Overview\n\n- **Content**: [title]\n- **Content Type**: [type]\n- **Audit Date**: [date]\n- **Total Score**: [score]\u002F100 ([rating])\n- **GEO Score**: [score]\u002F100 | **SEO Score**: [score]\u002F100\n- **Veto Status**: ✅ No triggers \u002F ⚠️ [item] triggered\n\n### Dimension Scores\n\n| Dimension | Score | Rating | Weight | Weighted |\n|-----------|-------|--------|--------|----------|\n| C — Contextual Clarity | [X]\u002F100 | [rating] | [X]% | [X] |\n| O — Organization | [X]\u002F100 | [rating] | [X]% | [X] |\n| R — Referenceability | [X]\u002F100 | [rating] | [X]% | [X] |\n| E — Exclusivity | [X]\u002F100 | [rating] | [X]% | [X] |\n| Exp — Experience | [X]\u002F100 | [rating] | [X]% | [X] |\n| Ept — Expertise | [X]\u002F100 | [rating] | [X]% | [X] |\n| A — Authority | [X]\u002F100 | [rating] | [X]% | [X] |\n| T — Trust | [X]\u002F100 | [rating] | [X]% | [X] |\n| **Weighted Total** | | | | **[X]\u002F100** |\n\n**Score Calculation**:\n- GEO Score = (C + O + R + E) \u002F 4\n- SEO Score = (Exp + Ept + A + T) \u002F 4\n- Weighted Score = Σ (dimension_score × content_type_weight)\n\n**Rating Scale**: 90-100 Excellent | 75-89 Good | 60-74 Medium | 40-59 Low | 0-39 Poor\n\n### N\u002FA Item Handling\n\nWhen an item cannot be evaluated (e.g., A01 Backlink Profile requires site-level data not available):\n\n1. Mark the item as \"N\u002FA\" with reason\n2. Exclude N\u002FA items from the dimension score calculation\n3. Dimension Score = (sum of scored items) \u002F (number of scored items x 10) x 100\n4. If more than 50% of a dimension's items are N\u002FA, flag the dimension as \"Insufficient Data\" and exclude it from the weighted total\n5. Recalculate weighted total using only dimensions with sufficient data, re-normalizing weights to sum to 100%\n\n**Example**: Authority dimension with 8 N\u002FA items and 2 scored items (A05=8, A07=5):\n- Dimension score = (8+5) \u002F (2 x 10) x 100 = 65\n- But 8\u002F10 items are N\u002FA (>50%), so flag as \"Insufficient Data -- Authority\"\n- Exclude A dimension from weighted total; redistribute its weight proportionally to remaining dimensions\n\n### Per-Item Scores\n\n#### CORE — Content Body (40 Items)\n\n| ID | Check Item | Score | Notes |\n|----|-----------|-------|-------|\n| C01 | Intent Alignment | [Pass\u002FPartial\u002FFail] | [observation] |\n| C02 | Direct Answer | [Pass\u002FPartial\u002FFail] | [observation] |\n| ... | ... | ... | ... |\n\n#### EEAT — Source Credibility (40 Items)\n\n| ID | Check Item | Score | Notes |\n|----|-----------|-------|-------|\n| Exp01 | First-Person Narrative | [Pass\u002FPartial\u002FFail] | [observation] |\n| ... | ... | ... | ... |\n\n### Top 5 Priority Improvements\n\nSorted by: weight × points lost (highest impact first)\n\n1. **[ID] [Name]** — [specific modification suggestion]\n   - Current: [Fail\u002FPartial] | Potential gain: [X] weighted points\n   - Action: [concrete step]\n\n2. **[ID] [Name]** — [specific modification suggestion]\n   - Current: [Fail\u002FPartial] | Potential gain: [X] weighted points\n   - Action: [concrete step]\n\n3–5. [Same format]\n\n### Action Plan\n\n#### Quick Wins (\u003C 30 minutes each)\n- [ ] [Action 1]\n- [ ] [Action 2]\n\n#### Medium Effort (1-2 hours)\n- [ ] [Action 3]\n- [ ] [Action 4]\n\n#### Strategic (Requires planning)\n- [ ] [Action 5]\n- [ ] [Action 6]\n\n### Recommended Next Steps\n\n- For full content rewrite: use `seo-content-writer` with CORE-EEAT constraints\n- For GEO optimization: use `geo-content-optimizer` targeting failed GEO-First items\n- For content refresh: use `content-refresher` with weak dimensions as focus\n- For technical fixes: run `\u002Fseo:check-technical` for site-level issues\n```\n\n### Save Results\n\nAfter delivering findings to the user, ask:\n\n> \"Save these results for future sessions?\"\n\nIf yes, write a dated summary to the appropriate `memory\u002F` path using filename `YYYY-MM-DD-\u003Ctopic>.md` containing:\n- One-line verdict or headline finding\n- Top 3-5 actionable items\n- Open loops or blockers\n- Source data references\n\nIf any veto-level issue was found (CORE-EEAT T04, C01, R10 or CITE T03, T05, T09), also append a one-liner to `memory\u002Fhot-cache.md` without asking.\n\n## Validation Checkpoints\n\n### Input Validation\n- [ ] Content source identified (text, URL, or file path)\n- [ ] Content type confirmed (auto-detected or user-specified)\n- [ ] Content is substantial enough for meaningful audit (≥300 words)\n- [ ] If comparative audit, competitor content also provided\n\n### Output Validation\n- [ ] All 80 items scored (or marked N\u002FA with reason)\n- [ ] All 8 dimension scores calculated correctly\n- [ ] Weighted total matches content-type weight configuration\n- [ ] Veto items checked and flagged if triggered\n- [ ] Top 5 improvements sorted by weighted impact, not arbitrary\n- [ ] Every recommendation is specific and actionable (not generic advice)\n- [ ] Action plan includes concrete steps with effort estimates\n\n## Example\n\nSee [references\u002Fitem-reference.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fcross-cutting\u002Fcontent-quality-auditor\u002Freferences\u002Fitem-reference.md) for a complete scored example showing the C dimension with all 10 items, priority improvements, and weighted scoring.\n\n## Tips for Success\n\n1. **Start with veto items** — T04, C01, R10 are deal-breakers regardless of total score\n   > These veto items are consistent with the CORE-EEAT benchmark (Section 3), which defines them as items that can override the overall score.\n2. **Focus on high-weight dimensions** — Different content types prioritize different dimensions\n3. **GEO-First items matter most for AI visibility** — Prioritize items tagged GEO 🎯 if AI citation is the goal\n4. **Some EEAT items need site-level data** — Don't penalize content for things only observable at the site level (backlinks, brand recognition)\n5. **Use the weighted score, not just the raw average** — A product review with strong Exclusivity matters more than strong Authority\n6. **Re-audit after improvements** — Run again to verify score improvements and catch regressions\n7. **Pair with CITE for domain-level context** — A high content score on a low-authority domain signals a different priority than the reverse; run [domain-authority-auditor](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fcross-cutting\u002Fdomain-authority-auditor\u002FSKILL.md) for the full 120-item picture\n\n## Reference Materials\n\n- [CORE-EEAT Content Benchmark](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Freferences\u002Fcore-eeat-benchmark.md) — Full 80-item benchmark with dimension definitions, scoring criteria, and GEO-First item markers\n- [references\u002Fitem-reference.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fcross-cutting\u002Fcontent-quality-auditor\u002Freferences\u002Fitem-reference.md) — All 80 item IDs in a compact lookup table + site-level item handling notes + scored example report\n\n## Next Best Skill\n\n- **Primary**: [content-refresher](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Foptimize\u002Fcontent-refresher\u002FSKILL.md) — turn failed checks into a concrete rewrite plan.\n","# Content Quality Auditor\n\n> Based on [CORE-EEAT Content Benchmark](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fcore-eeat-content-benchmark). Full benchmark reference: [references\u002Fcore-eeat-benchmark.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Freferences\u002Fcore-eeat-benchmark.md)\n\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 cross-cutting skill is part of the protocol layer and 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 evaluates content quality across 80 standardized criteria organized in 8 dimensions. It produces a comprehensive audit report with per-item scoring, dimension and system scores, weighted totals by content type, and a prioritized action plan.\n\n**System role**: Publish Readiness Gate. It decides whether content is ready to ship, what blocks publication, and what should be promoted into durable project memory.\n\n## When This Must Trigger\n\nUse this when content needs a quality check before publishing — even if the user doesn't use audit terminology:\n\n- User asks \"is this ready to publish\" or \"how good is this\"\n- User just finished writing with seo-content-writer or content-refresher\n- **PostToolUse hook auto-triggers**: after content is written or substantially edited, the hook recommends this audit. When hook-triggered, skip setup questions — audit the content that was just produced.\n- Auditing content quality before publishing\n- Evaluating existing content for improvement opportunities\n- Benchmarking content against CORE-EEAT standards\n- Comparing content quality against competitors\n- Assessing both GEO readiness (AI citation potential) and SEO strength (source credibility)\n- Running periodic content quality checks as part of a content maintenance program\n- After writing or optimizing content with seo-content-writer or geo-content-optimizer\n\n## What This Skill Does\n\n1. **Full 80-Item Audit**: Scores every CORE-EEAT check item as Pass\u002FPartial\u002FFail\n2. **Dimension Scoring**: Calculates scores for all 8 dimensions (0-100 each)\n3. **System Scoring**: Computes GEO Score (CORE) and SEO Score (EEAT)\n4. **Weighted Totals**: Applies content-type-specific weights for final score\n5. **Veto Detection**: Flags critical trust violations (T04, C01, R10)\n6. **Priority Ranking**: Identifies Top 5 improvements sorted by impact\n7. **Action Plan**: Generates specific, actionable improvement steps\n\n## Quick Start\n\nStart with one of these prompts. Finish with a publish verdict and a 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### Audit Content\n\n```\nAudit this content against CORE-EEAT: [content text or URL]\n```\n\n```\nRun a content quality audit on [URL] as a [content type]\n```\n\n### Audit with Content Type\n\n```\nCORE-EEAT audit for this product review: [content]\n```\n\n```\nScore this how-to guide against the 80-item benchmark: [content]\n```\n\n### Comparative Audit\n\n```\nAudit my content vs competitor: [your content] vs [competitor content]\n```\n\n## Skill Contract\n\n**Gate verdict**: **SHIP** (no veto items, dimension scores above threshold) \u002F **FIX** (issues found but no veto) \u002F **BLOCK** (veto item T04, C01, or R10 failed). Always state the verdict prominently at the top of the report.\n\n**Expected output**: a CORE-EEAT audit report, a publish-readiness verdict, and a short handoff summary ready for `memory\u002Faudits\u002Fcontent\u002F`.\n\n- **Reads**: the target content, content type, supporting evidence, and any 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 audit report plus a reusable summary that can be stored under `memory\u002Faudits\u002Fcontent\u002F`.\n- **Promotes**: veto items and publish blockers to `memory\u002Fhot-cache.md` (auto-saved, no user confirmation needed). Top improvement priorities to `memory\u002Fopen-loops.md`.\n- **Next handoff**: use the `Next Best Skill` below once the verdict is clear.\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 ~~web crawler + ~~SEO tool connected:**\nAutomatically fetch page content, extract HTML structure, check schema markup, verify internal\u002Fexternal links, and pull competitor content for comparison.\n\n**With manual data only:**\nAsk the user to provide:\n1. Content text, URL, or file path\n2. Content type (if not auto-detectable): Product Review, How-to Guide, Comparison, Landing Page, Blog Post, FAQ Page, Alternative, Best-of, or Testimonial\n3. Optional: competitor content for benchmarking\n\nProceed with the full 80-item audit using provided data. Note in the output which items could not be fully evaluated due to missing access (e.g., backlink data, schema markup, site-level signals).\n\n## Decision Gates\n\nWhen stopping to ask, always: (1) state the specific value and threshold, (2) offer numbered options with outcomes.\n\n**Stop and ask the user when:**\n- Content is under minimum word count for its type (blog\u002Fguide: 300 words; product\u002Flanding page: 150 words; FAQ: fewer than 3 entries with 50+ words each) — state the actual count and offer: (1) expand to minimum, (2) continue audit with Insufficient Data flags, (3) cancel\n- Content type cannot be auto-detected — state what you detected and ask to confirm before proceeding\n- Content is primarily media (video\u002Fimage) with minimal text — ask whether to audit transcript, alt text, or skip\n- More than 50% of a dimension's items are N\u002FA — name the dimension and ask: (1) provide supplementary data, (2) mark entire dimension as Insufficient Data\n- Any veto item triggers — flag it immediately with the item ID and ask: (1) stop for immediate fix, (2) continue full audit and flag in report\n\n**Continue silently (never stop for):**\n- Individual Partial scores within a dimension\n- Missing SEO tool data (mark items as N\u002FA and continue)\n- Low overall score (the report is the deliverable, not a judgment call)\n- User not specifying content type (auto-detect and state your assumption)\n\n## Instructions\n\nWhen a user requests a content quality audit:\n\n### Step 1: Preparation\n\n```markdown\n### Audit Setup\n\n**Content**: [title or URL]\n**Content Type**: [auto-detected or user-specified]\n**Dimension Weights**: [loaded from content-type weight table]\n\n#### Veto Check (Emergency Brake)\n\n| Veto Item | Status | Action |\n|-----------|--------|--------|\n| T04: Disclosure Statements | ✅ Pass \u002F ⚠️ VETO | [If VETO: \"Add disclosure banner at page top immediately\"] |\n| C01: Intent Alignment | ✅ Pass \u002F ⚠️ VETO | [If VETO: \"Rewrite title and first paragraph\"] |\n| R10: Content Consistency | ✅ Pass \u002F ⚠️ VETO | [If VETO: \"Verify all data before publishing\"] |\n```\n\nIf any veto item triggers, flag it prominently at the top of the report and recommend immediate action before continuing the full audit.\n\n### Step 2: CORE Audit (40 items)\n\nEvaluate each item against the criteria in [references\u002Fcore-eeat-benchmark.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Freferences\u002Fcore-eeat-benchmark.md).\n\nScore each item:\n- **Pass** = 10 points (fully meets criteria)\n- **Partial** = 5 points (partially meets criteria)\n- **Fail** = 0 points (does not meet criteria)\n\n```markdown\n### C — Contextual Clarity\n\n| ID | Check Item | Score | Notes |\n|----|-----------|-------|-------|\n| C01 | Intent Alignment | Pass\u002FPartial\u002FFail | [specific observation] |\n| C02 | Direct Answer | Pass\u002FPartial\u002FFail | [specific observation] |\n| ... | ... | ... | ... |\n| C10 | Semantic Closure | Pass\u002FPartial\u002FFail | [specific observation] |\n\n**C Score**: [X]\u002F100\n```\n\nRepeat the same table format for **O** (Organization), **R** (Referenceability), and **E** (Exclusivity), scoring all 10 items per dimension.\n\n### Step 3: EEAT Audit (40 items)\n\n```markdown\n### Exp — Experience\n\n| ID | Check Item | Score | Notes |\n|----|-----------|-------|-------|\n| Exp01 | First-Person Narrative | Pass\u002FPartial\u002FFail | [specific observation] |\n| ... | ... | ... | ... |\n\n**Exp Score**: [X]\u002F100\n```\n\nRepeat the same table format for **Ept** (Expertise), **A** (Authority), and **T** (Trust), scoring all 10 items per dimension.\n\nSee [references\u002Fitem-reference.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fcross-cutting\u002Fcontent-quality-auditor\u002Freferences\u002Fitem-reference.md) for the complete 80-item ID lookup table and site-level item handling notes.\n\n### Step 4: Scoring & Report\n\nCalculate scores and generate the final report:\n\n```markdown\n## CORE-EEAT Audit Report\n\n### Overview\n\n- **Content**: [title]\n- **Content Type**: [type]\n- **Audit Date**: [date]\n- **Total Score**: [score]\u002F100 ([rating])\n- **GEO Score**: [score]\u002F100 | **SEO Score**: [score]\u002F100\n- **Veto Status**: ✅ No triggers \u002F ⚠️ [item] triggered\n\n### Dimension Scores\n\n| Dimension | Score | Rating | Weight | Weighted |\n|-----------|-------|--------|--------|----------|\n| C — Contextual Clarity | [X]\u002F100 | [rating] | [X]% | [X] |\n| O — Organization | [X]\u002F100 | [rating] | [X]% | [X] |\n| R — Referenceability | [X]\u002F100 | [rating] | [X]% | [X] |\n| E — Exclusivity | [X]\u002F100 | [rating] | [X]% | [X] |\n| Exp — Experience | [X]\u002F100 | [rating] | [X]% | [X] |\n| Ept — Expertise | [X]\u002F100 | [rating] | [X]% | [X] |\n| A — Authority | [X]\u002F100 | [rating] | [X]% | [X] |\n| T — Trust | [X]\u002F100 | [rating] | [X]% | [X] |\n| **Weighted Total** | | | | **[X]\u002F100** |\n\n**Score Calculation**:\n- GEO Score = (C + O + R + E) \u002F 4\n- SEO Score = (Exp + Ept + A + T) \u002F 4\n- Weighted Score = Σ (dimension_score × content_type_weight)\n\n**Rating Scale**: 90-100 Excellent | 75-89 Good | 60-74 Medium | 40-59 Low | 0-39 Poor\n\n### N\u002FA Item Handling\n\nWhen an item cannot be evaluated (e.g., A01 Backlink Profile requires site-level data not available):\n\n1. Mark the item as \"N\u002FA\" with reason\n2. Exclude N\u002FA items from the dimension score calculation\n3. Dimension Score = (sum of scored items) \u002F (number of scored items x 10) x 100\n4. If more than 50% of a dimension's items are N\u002FA, flag the dimension as \"Insufficient Data\" and exclude it from the weighted total\n5. Recalculate weighted total using only dimensions with sufficient data, re-normalizing weights to sum to 100%\n\n**Example**: Authority dimension with 8 N\u002FA items and 2 scored items (A05=8, A07=5):\n- Dimension score = (8+5) \u002F (2 x 10) x 100 = 65\n- But 8\u002F10 items are N\u002FA (>50%), so flag as \"Insufficient Data -- Authority\"\n- Exclude A dimension from weighted total; redistribute its weight proportionally to remaining dimensions\n\n### Per-Item Scores\n\n#### CORE — Content Body (40 Items)\n\n| ID | Check Item | Score | Notes |\n|----|-----------|-------|-------|\n| C01 | Intent Alignment | [Pass\u002FPartial\u002FFail] | [observation] |\n| C02 | Direct Answer | [Pass\u002FPartial\u002FFail] | [observation] |\n| ... | ... | ... | ... |\n\n#### EEAT — Source Credibility (40 Items)\n\n| ID | Check Item | Score | Notes |\n|----|-----------|-------|-------|\n| Exp01 | First-Person Narrative | [Pass\u002FPartial\u002FFail] | [observation] |\n| ... | ... | ... | ... |\n\n### Top 5 Priority Improvements\n\nSorted by: weight × points lost (highest impact first)\n\n1. **[ID] [Name]** — [specific modification suggestion]\n   - Current: [Fail\u002FPartial] | Potential gain: [X] weighted points\n   - Action: [concrete step]\n\n2. **[ID] [Name]** — [specific modification suggestion]\n   - Current: [Fail\u002FPartial] | Potential gain: [X] weighted points\n   - Action: [concrete step]\n\n3–5. [Same format]\n\n### Action Plan\n\n#### Quick Wins (\u003C 30 minutes each)\n- [ ] [Action 1]\n- [ ] [Action 2]\n\n#### Medium Effort (1-2 hours)\n- [ ] [Action 3]\n- [ ] [Action 4]\n\n#### Strategic (Requires planning)\n- [ ] [Action 5]\n- [ ] [Action 6]\n\n### Recommended Next Steps\n\n- For full content rewrite: use `seo-content-writer` with CORE-EEAT constraints\n- For GEO optimization: use `geo-content-optimizer` targeting failed GEO-First items\n- For content refresh: use `content-refresher` with weak dimensions as focus\n- For technical fixes: run `\u002Fseo:check-technical` for site-level issues\n```\n\n### Save Results\n\nAfter delivering findings to the user, ask:\n\n> \"Save these results for future sessions?\"\n\nIf yes, write a dated summary to the appropriate `memory\u002F` path using filename `YYYY-MM-DD-\u003Ctopic>.md` containing:\n- One-line verdict or headline finding\n- Top 3-5 actionable items\n- Open loops or blockers\n- Source data references\n\nIf any veto-level issue was found (CORE-EEAT T04, C01, R10 or CITE T03, T05, T09), also append a one-liner to `memory\u002Fhot-cache.md` without asking.\n\n## Validation Checkpoints\n\n### Input Validation\n- [ ] Content source identified (text, URL, or file path)\n- [ ] Content type confirmed (auto-detected or user-specified)\n- [ ] Content is substantial enough for meaningful audit (≥300 words)\n- [ ] If comparative audit, competitor content also provided\n\n### Output Validation\n- [ ] All 80 items scored (or marked N\u002FA with reason)\n- [ ] All 8 dimension scores calculated correctly\n- [ ] Weighted total matches content-type weight configuration\n- [ ] Veto items checked and flagged if triggered\n- [ ] Top 5 improvements sorted by weighted impact, not arbitrary\n- [ ] Every recommendation is specific and actionable (not generic advice)\n- [ ] Action plan includes concrete steps with effort estimates\n\n## Example\n\nSee [references\u002Fitem-reference.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fcross-cutting\u002Fcontent-quality-auditor\u002Freferences\u002Fitem-reference.md) for a complete scored example showing the C dimension with all 10 items, priority improvements, and weighted scoring.\n\n## Tips for Success\n\n1. **Start with veto items** — T04, C01, R10 are deal-breakers regardless of total score\n   > These veto items are consistent with the CORE-EEAT benchmark (Section 3), which defines them as items that can override the overall score.\n2. **Focus on high-weight dimensions** — Different content types prioritize different dimensions\n3. **GEO-First items matter most for AI visibility** — Prioritize items tagged GEO 🎯 if AI citation is the goal\n4. **Some EEAT items need site-level data** — Don't penalize content for things only observable at the site level (backlinks, brand recognition)\n5. **Use the weighted score, not just the raw average** — A product review with strong Exclusivity matters more than strong Authority\n6. **Re-audit after improvements** — Run again to verify score improvements and catch regressions\n7. **Pair with CITE for domain-level context** — A high content score on a low-authority domain signals a different priority than the reverse; run [domain-authority-auditor](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fcross-cutting\u002Fdomain-authority-auditor\u002FSKILL.md) for the full 120-item picture\n\n## Reference Materials\n\n- [CORE-EEAT Content Benchmark](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Freferences\u002Fcore-eeat-benchmark.md) — Full 80-item benchmark with dimension definitions, scoring criteria, and GEO-First item markers\n- [references\u002Fitem-reference.md](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Fcross-cutting\u002Fcontent-quality-auditor\u002Freferences\u002Fitem-reference.md) — All 80 item IDs in a compact lookup table + site-level item handling notes + scored example report\n\n## Next Best Skill\n\n- **Primary**: [content-refresher](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\u002Fblob\u002Fmain\u002Foptimize\u002Fcontent-refresher\u002FSKILL.md) — turn failed checks into a concrete rewrite plan.\n",{"name":5,"license":14,"version":23,"homepage":24,"metadata":25,"description":7,"when_to_use":70,"allowed-tools":71,"argument-hint":72,"compatibility":73},"6.0.0","https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills",{"tags":26,"author":39,"version":23,"triggers":40,"geo-relevance":69},[27,28,29,30,31,32,33,34,35,36,37,38],"seo","geo","e-e-a-t","core-eeat","content-quality","content-scoring","helpful-content","publish-readiness","内容质量","コンテンツ品質","콘텐츠품질","auditoria-eeat","aaron-he-zhu",[41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68],"audit content quality","EEAT score","CORE-EEAT audit","content quality check","content assessment","quality score","is this ready to publish","grade my article","check before publishing","how good is my content","is my content good enough to rank","rate my content quality","is my content ready to publish","how do I improve content quality","内容质量审计","EEAT评分","内容评估","文章能发吗","内容打几分","文章写得怎么样","コンテンツ品質監査","E-E-A-T評価","콘텐츠 품질 감사","EEAT 점수","auditoría de calidad de contenido","puntuación EEAT","auditoria de qualidade","EEAT scroe","high","Use when auditing content quality before publishing. Runs CORE-EEAT 80-item scoring with veto checks. Also when the user asks for E-E-A-T analysis or publish readiness.","WebFetch","\u003CURL or paste content> [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\u002Fcontent-quality-auditor","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim","https:\u002F\u002Fgithub.com\u002Flzy18001500226","2026-08-31 23:29:00",{"source":8,"skillName":5,"commands":81,"prompt":91,"zipAvailable":92},[82,85,88],{"tool":83,"command":84},"npx","npx skills add lzy18001500226\u002FMoSim --skill content-quality-auditor",{"tool":86,"command":87},"bunx","bunx skills add lzy18001500226\u002FMoSim --skill content-quality-auditor",{"tool":89,"command":90},"pnpm","pnpm dlx skills add lzy18001500226\u002FMoSim --skill content-quality-auditor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FMemory\u002FSurfSense\u002F.cursor\u002Fskills\u002Fcontent-quality-auditor\u002FSKILL.md",true,[94],{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fitem-reference.md","REFERENCE","参考文档",5516,"https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FMemory\u002FSurfSense\u002F.cursor\u002Fskills\u002Fcontent-quality-auditor\u002Freferences\u002Fitem-reference.md",[101,110,118,126,134,142],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":109},"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":109},"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":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":109},"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":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":130,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":109},"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":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":138,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":109},"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":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":146,"licenseFileUrl":147,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":151},"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"]