[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MEBCV21CBCG9EP5PKPGFSA":3,"skill-same:01M6MEBCV21CBCG9EP5PKPGFSA":92},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":32,"publishedAt":53,"linkOnly":54,"markdownContent":55,"markdownBody":56,"frontMatter":57,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":67,"repositoryHtmlUrl":68,"repositoryHomepageUrl":69,"ownerHtmlUrl":70,"ownerBlogUrl":71,"ownerDescription":72,"updatedAt":73,"install":74,"resources":86},"01M6MEBCV21CBCG9EP5PKPGFSA","seo-content",null,"Content quality and E-E-A-T analysis with AI citation readiness assessment. Use when user says \"content quality\", \"E-E-A-T\", \"content analysis\", \"readability check\", \"thin content\", or \"content audit\".","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favalonreset\u002Fseo-dungeon\u002Fskills\u002Fseo-content\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favalonreset\u002Fseo-dungeon\u002Fskills\u002Fseo-content\u002FSKILL.md",[19,24,29],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":25,"categoryName":26,"taxonomyType":27,"taxonomyTypeDesc":28},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",{"categoryNo":30,"categoryName":31,"taxonomyType":27,"taxonomyTypeDesc":28},"01JBSEEDCAT000000000000036","内容创作者",[33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52],"seo content","content","seo","when","Citation","user","quality","readiness","with","check","content audit","use","true","e-e-a-t","readability","audit","analysis","URL","content analysis","assessment","2026-11-10 10:12:30",false,"---\nname: seo-content\ndescription: >\n  Content quality and E-E-A-T analysis with AI citation readiness assessment.\n  Use when user says \"content quality\", \"E-E-A-T\", \"content analysis\",\n  \"readability check\", \"thin content\", or \"content audit\".\nuser-invocable: true\nargument-hint: \"[url]\"\nlicense: MIT\nmetadata:\n  author: AgriciDaniel\n  version: \"2.2.7\"\n  category: seo\n---\n\n# Content Quality & E-E-A-T Analysis\n\n## Google's \"Who \u002F How \u002F Why\" Test (canonical heuristic)\n\nBefore scoring E-E-A-T sub-factors, every page audit should pass Google's\nown three-question heuristic from the helpful-content guide:\n\n| Question | What to look for |\n|---|---|\n| **Who** created it? | Visible byline, author bio page, professional credentials. Required where readers expect it; non-negotiable for YMYL. |\n| **How** was it created? | Process disclosure where readers would reasonably ask, especially for AI-assisted content. Original research \u002F first-hand evidence \u002F lived experience. |\n| **Why** does it exist? | \"To help people\" rather than \"to attract search clicks.\" Watch for niche entry without expertise, content churn for freshness signals, content written to a word-count target. |\n\nPrimary source:\nhttps:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Ffundamentals\u002Fcreating-helpful-content\n\nWhen all three answers are weak, the page is at risk under the core ranking\nsystem's helpfulness signals (formerly the standalone Helpful Content System,\nmerged into core during the March 2024 update).\n\n## E-E-A-T Framework (updated Sept 2025 QRG)\n\nRead `skills\u002Fseo\u002Freferences\u002Feeat-framework.md` for full criteria.\n\n### Experience (first-hand signals)\n- Original research, case studies, before\u002Fafter results\n- Personal anecdotes, process documentation\n- Unique data, proprietary insights\n- Photos\u002Fvideos from direct experience\n\n### Expertise\n- Author credentials, certifications, bio\n- Professional background relevant to topic\n- Technical depth appropriate for audience\n- Accurate, well-sourced claims\n\n### Authoritativeness\n- External citations, backlinks from authoritative sources\n- Brand mentions, industry recognition\n- Published in recognized outlets\n- Cited by other experts\n\n### Trustworthiness\n- Contact information, physical address\n- Privacy policy, terms of service\n- Customer testimonials, reviews\n- Date stamps, transparent corrections\n- Secure site (HTTPS)\n\n## Content Metrics\n\n### Word Count Analysis\nCompare against page type minimums:\n| Page Type | Minimum |\n|-----------|---------|\n| Homepage | 500 |\n| Service page | 800 |\n| Blog post | 1,500 |\n| Product page | 300+ (400+ for complex products) |\n| Location page | 500-600 |\n\n> **Important:** These are **topical coverage floors**, not targets. Google has confirmed word count is NOT a direct ranking factor. The goal is comprehensive topical coverage; a 500-word page that thoroughly answers the query will outrank a 2,000-word page that doesn't. Use these as guidelines for adequate coverage depth, not rigid requirements.\n\n### Readability\n- Flesch Reading Ease: target 60-70 for general audience\n\n> **Note:** Flesch Reading Ease is a useful proxy for content accessibility but is NOT a direct Google ranking factor. John Mueller has confirmed Google does not use basic readability scores for ranking. Yoast deprioritized Flesch scores in v19.3. Use readability analysis as a content quality indicator, not as an SEO metric to optimize directly.\n- Grade level: match target audience\n- Sentence length: average 15-20 words\n- Paragraph length: 2-4 sentences\n\n### Keyword Optimization\n- Primary keyword in title, H1, first 100 words\n- Natural density (1-3%)\n- Semantic variations present\n- No keyword stuffing\n\n### Content Structure\n- Logical heading hierarchy (H1 -> H2 -> H3)\n- Scannable sections with descriptive headings\n- Bullet\u002Fnumbered lists where appropriate\n- Table of contents for long-form content\n\n### Multimedia\n- Relevant images with proper alt text\n- Videos where appropriate\n- Infographics for complex data\n- Charts\u002Fgraphs for statistics\n\n### Internal Linking\n- 3-5 relevant internal links per 1000 words\n- Descriptive anchor text\n- Links to related content\n- No orphan pages\n\n### External Linking\n- Cite authoritative sources\n- Open in new tab for user experience\n- Reasonable count (not excessive)\n\n## AI Content Assessment (Sept 2025 QRG addition)\n\nGoogle's raters assess low-quality, scaled, copied, or AI-generated main content patterns rather than AI authorship as a standalone issue.\n\n### Acceptable AI Content\n- Demonstrates genuine E-E-A-T\n- Provides unique value\n- Has human oversight and editing\n- Contains original insights\n\n### Low-Quality AI Content Markers\n- Generic phrasing, lack of specificity\n- No original insight\n- Repetitive structure across pages\n- No author attribution\n- Factual inaccuracies\n\n> **Helpful Content System (March 2024):** The Helpful Content System was merged into Google's core ranking algorithm during the March 2024 core update. It no longer operates as a standalone classifier. Helpfulness signals are now weighted within every core update. The same principles apply (people-first content, demonstrating E-E-A-T, satisfying user intent), but enforcement is continuous rather than through separate HCU updates. Google now also documents **continuous, smaller unannounced core updates** between major ones (changelog 2025-12-09).\n\n> **Gen-AI optimization is SEO (Google docs, 2026-06-29):** the official \"optimizing for generative AI features\" guide states you do **not** need new AI files, markup, Markdown, content chunking, or AI-specific rewrites; chasing inauthentic \"mentions\" is unhelpful. AEO\u002FGEO is rebranded SEO rooted in core ranking\u002Fquality.\n\n> **Honest scoping (Google docs, 2026-06-05):** per \"Using third-party SEO tools, services, and advice,\" no tool guarantees rankings and third-party tools have no access to Google's internal ranking data. claude-seo's scores are **heuristics**, not Google-internal signals, so say so in reports, and validate GEO\u002FAEO findings against Google's official guidance (Search Console is the first-party source).\n\n## AI Citation Readiness (GEO signals)\n\nOptimize for AI search engines (ChatGPT, Perplexity, Google AI Overviews):\n\n- Clear, quotable statements with statistics\u002Ffacts\n- Structured data (especially for data points)\n- Strong heading hierarchy (H1->H2->H3 flow)\n- Answer-first formatting for key questions\n- Tables and lists for comparative data\n- Clear attribution and source citations\n\n### AI Search Visibility & GEO (2025-2026)\n\n**Google AI Mode** is Google's conversational AI search surface. Google's last official model naming for AI Mode \u002F AI Overviews is a custom version of **Gemini 2.5**. Treat third-party AI Mode usage, citation, and link-share figures as methodology-dependent unless primary-sourced, and optimize for both AI Mode and AI Overviews (see the `seo-geo` skill).\n\n**Key optimization strategies for AI citation:**\n- **Structured answers:** Clear question-answer formats, definition patterns, and step-by-step instructions that AI systems can extract and cite\n- **First-party data:** Original research, statistics, case studies, and unique datasets are highly cited by AI systems\n- **Schema markup:** Article and other relevant structured content. FAQPage no longer produces Google FAQ rich results; use QAPage only for genuine user Q&A where appropriate\n- **Topical authority:** AI systems preferentially cite sources that demonstrate deep expertise. Build content clusters, not isolated pages\n- **Entity clarity:** Ensure brand, authors, and key concepts are clearly defined with structured data (Organization, Person schema)\n- **Multi-platform tracking:** Monitor visibility across Google AI Overviews, AI Mode, ChatGPT, Perplexity, and Bing Copilot, not just traditional rankings. Treat AI citation as a standalone KPI alongside organic rankings and traffic.\n\n**Generative Engine Optimization (GEO):**\nPer Google's AI optimization guide, \"AEO\" and \"GEO\" are rebranded labels for SEO: AI Overviews and AI Mode are grounded in the same ranking and quality systems as classic Search. The optimization signals that matter (quotability, attribution, heading hierarchy, freshness) are SEO fundamentals applied to AI-search surfaces, not a separate discipline. Cross-reference the `seo-geo` skill for detailed workflows; both surfaces share the primary-source synthesis in `skills\u002Fseo-geo\u002Freferences\u002Fgoogle-ai-optimization-guide.md`.\n\n## Content Freshness\n\n- Publication date visible\n- Last updated date if content has been revised\n- Flag content older than 12 months without update for fast-changing topics\n\n## Output\n\n### Content Quality Score: XX\u002F100\n\n### E-E-A-T Breakdown\n| Factor | Score | Key Signals |\n|--------|-------|-------------|\n| Experience | XX\u002F20 | ... |\n| Expertise | XX\u002F25 | ... |\n| Authoritativeness | XX\u002F25 | ... |\n| Trustworthiness | XX\u002F30 | ... |\n\n> Weights are **this skill's own scoring model**, ordered to reflect Google's\n> stated hierarchy: **Trust is most important** (30), then Expertise\u002F\n> Authoritativeness (25 each), then Experience (20); maxima sum to 100. Google\n> publishes no numeric E-E-A-T weights (only that trust is most important), so\n> treat the split as our internal model. Do not use an equal 25\u002F25\u002F25\u002F25 split\n> (it contradicts Google's \"trust is most important\").\n\n### AI Citation Readiness: XX\u002F100\n\n### Issues Found\n### Recommendations\n\n## DataForSEO Integration (Optional)\n\nIf DataForSEO credentials or optional tools are available, use direct DataForSEO calls for real keyword volume data, difficulty scores, intent classification, and content quality analysis.\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess page content. Suggest the user verify the URL and try again. |\n| Content behind paywall (402\u002F403, login wall) | Report that the content is not publicly accessible. Analyze only the visible portion (meta tags, headers) and note the limitation. |\n| Thin content (fewer than 100 words retrievable) | Report the findings as-is rather than guessing. Flag the page as potentially JavaScript-rendered or gated, and suggest the user provide the full text directly. |\n\n## FLOW Framework Integration\n\nFor prompt-guided content optimization, use `\u002Fseo flow optimize \u003Curl>` and `\u002Fseo flow win \u003Curl>`: FLOW's optimize and win prompts provide structured E-E-A-T improvement and BOFU conversion workflows.\n","# Content Quality & E-E-A-T Analysis\n\n## Google's \"Who \u002F How \u002F Why\" Test (canonical heuristic)\n\nBefore scoring E-E-A-T sub-factors, every page audit should pass Google's\nown three-question heuristic from the helpful-content guide:\n\n| Question | What to look for |\n|---|---|\n| **Who** created it? | Visible byline, author bio page, professional credentials. Required where readers expect it; non-negotiable for YMYL. |\n| **How** was it created? | Process disclosure where readers would reasonably ask, especially for AI-assisted content. Original research \u002F first-hand evidence \u002F lived experience. |\n| **Why** does it exist? | \"To help people\" rather than \"to attract search clicks.\" Watch for niche entry without expertise, content churn for freshness signals, content written to a word-count target. |\n\nPrimary source:\nhttps:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Ffundamentals\u002Fcreating-helpful-content\n\nWhen all three answers are weak, the page is at risk under the core ranking\nsystem's helpfulness signals (formerly the standalone Helpful Content System,\nmerged into core during the March 2024 update).\n\n## E-E-A-T Framework (updated Sept 2025 QRG)\n\nRead `skills\u002Fseo\u002Freferences\u002Feeat-framework.md` for full criteria.\n\n### Experience (first-hand signals)\n- Original research, case studies, before\u002Fafter results\n- Personal anecdotes, process documentation\n- Unique data, proprietary insights\n- Photos\u002Fvideos from direct experience\n\n### Expertise\n- Author credentials, certifications, bio\n- Professional background relevant to topic\n- Technical depth appropriate for audience\n- Accurate, well-sourced claims\n\n### Authoritativeness\n- External citations, backlinks from authoritative sources\n- Brand mentions, industry recognition\n- Published in recognized outlets\n- Cited by other experts\n\n### Trustworthiness\n- Contact information, physical address\n- Privacy policy, terms of service\n- Customer testimonials, reviews\n- Date stamps, transparent corrections\n- Secure site (HTTPS)\n\n## Content Metrics\n\n### Word Count Analysis\nCompare against page type minimums:\n| Page Type | Minimum |\n|-----------|---------|\n| Homepage | 500 |\n| Service page | 800 |\n| Blog post | 1,500 |\n| Product page | 300+ (400+ for complex products) |\n| Location page | 500-600 |\n\n> **Important:** These are **topical coverage floors**, not targets. Google has confirmed word count is NOT a direct ranking factor. The goal is comprehensive topical coverage; a 500-word page that thoroughly answers the query will outrank a 2,000-word page that doesn't. Use these as guidelines for adequate coverage depth, not rigid requirements.\n\n### Readability\n- Flesch Reading Ease: target 60-70 for general audience\n\n> **Note:** Flesch Reading Ease is a useful proxy for content accessibility but is NOT a direct Google ranking factor. John Mueller has confirmed Google does not use basic readability scores for ranking. Yoast deprioritized Flesch scores in v19.3. Use readability analysis as a content quality indicator, not as an SEO metric to optimize directly.\n- Grade level: match target audience\n- Sentence length: average 15-20 words\n- Paragraph length: 2-4 sentences\n\n### Keyword Optimization\n- Primary keyword in title, H1, first 100 words\n- Natural density (1-3%)\n- Semantic variations present\n- No keyword stuffing\n\n### Content Structure\n- Logical heading hierarchy (H1 -> H2 -> H3)\n- Scannable sections with descriptive headings\n- Bullet\u002Fnumbered lists where appropriate\n- Table of contents for long-form content\n\n### Multimedia\n- Relevant images with proper alt text\n- Videos where appropriate\n- Infographics for complex data\n- Charts\u002Fgraphs for statistics\n\n### Internal Linking\n- 3-5 relevant internal links per 1000 words\n- Descriptive anchor text\n- Links to related content\n- No orphan pages\n\n### External Linking\n- Cite authoritative sources\n- Open in new tab for user experience\n- Reasonable count (not excessive)\n\n## AI Content Assessment (Sept 2025 QRG addition)\n\nGoogle's raters assess low-quality, scaled, copied, or AI-generated main content patterns rather than AI authorship as a standalone issue.\n\n### Acceptable AI Content\n- Demonstrates genuine E-E-A-T\n- Provides unique value\n- Has human oversight and editing\n- Contains original insights\n\n### Low-Quality AI Content Markers\n- Generic phrasing, lack of specificity\n- No original insight\n- Repetitive structure across pages\n- No author attribution\n- Factual inaccuracies\n\n> **Helpful Content System (March 2024):** The Helpful Content System was merged into Google's core ranking algorithm during the March 2024 core update. It no longer operates as a standalone classifier. Helpfulness signals are now weighted within every core update. The same principles apply (people-first content, demonstrating E-E-A-T, satisfying user intent), but enforcement is continuous rather than through separate HCU updates. Google now also documents **continuous, smaller unannounced core updates** between major ones (changelog 2025-12-09).\n\n> **Gen-AI optimization is SEO (Google docs, 2026-06-29):** the official \"optimizing for generative AI features\" guide states you do **not** need new AI files, markup, Markdown, content chunking, or AI-specific rewrites; chasing inauthentic \"mentions\" is unhelpful. AEO\u002FGEO is rebranded SEO rooted in core ranking\u002Fquality.\n\n> **Honest scoping (Google docs, 2026-06-05):** per \"Using third-party SEO tools, services, and advice,\" no tool guarantees rankings and third-party tools have no access to Google's internal ranking data. claude-seo's scores are **heuristics**, not Google-internal signals, so say so in reports, and validate GEO\u002FAEO findings against Google's official guidance (Search Console is the first-party source).\n\n## AI Citation Readiness (GEO signals)\n\nOptimize for AI search engines (ChatGPT, Perplexity, Google AI Overviews):\n\n- Clear, quotable statements with statistics\u002Ffacts\n- Structured data (especially for data points)\n- Strong heading hierarchy (H1->H2->H3 flow)\n- Answer-first formatting for key questions\n- Tables and lists for comparative data\n- Clear attribution and source citations\n\n### AI Search Visibility & GEO (2025-2026)\n\n**Google AI Mode** is Google's conversational AI search surface. Google's last official model naming for AI Mode \u002F AI Overviews is a custom version of **Gemini 2.5**. Treat third-party AI Mode usage, citation, and link-share figures as methodology-dependent unless primary-sourced, and optimize for both AI Mode and AI Overviews (see the `seo-geo` skill).\n\n**Key optimization strategies for AI citation:**\n- **Structured answers:** Clear question-answer formats, definition patterns, and step-by-step instructions that AI systems can extract and cite\n- **First-party data:** Original research, statistics, case studies, and unique datasets are highly cited by AI systems\n- **Schema markup:** Article and other relevant structured content. FAQPage no longer produces Google FAQ rich results; use QAPage only for genuine user Q&A where appropriate\n- **Topical authority:** AI systems preferentially cite sources that demonstrate deep expertise. Build content clusters, not isolated pages\n- **Entity clarity:** Ensure brand, authors, and key concepts are clearly defined with structured data (Organization, Person schema)\n- **Multi-platform tracking:** Monitor visibility across Google AI Overviews, AI Mode, ChatGPT, Perplexity, and Bing Copilot, not just traditional rankings. Treat AI citation as a standalone KPI alongside organic rankings and traffic.\n\n**Generative Engine Optimization (GEO):**\nPer Google's AI optimization guide, \"AEO\" and \"GEO\" are rebranded labels for SEO: AI Overviews and AI Mode are grounded in the same ranking and quality systems as classic Search. The optimization signals that matter (quotability, attribution, heading hierarchy, freshness) are SEO fundamentals applied to AI-search surfaces, not a separate discipline. Cross-reference the `seo-geo` skill for detailed workflows; both surfaces share the primary-source synthesis in `skills\u002Fseo-geo\u002Freferences\u002Fgoogle-ai-optimization-guide.md`.\n\n## Content Freshness\n\n- Publication date visible\n- Last updated date if content has been revised\n- Flag content older than 12 months without update for fast-changing topics\n\n## Output\n\n### Content Quality Score: XX\u002F100\n\n### E-E-A-T Breakdown\n| Factor | Score | Key Signals |\n|--------|-------|-------------|\n| Experience | XX\u002F20 | ... |\n| Expertise | XX\u002F25 | ... |\n| Authoritativeness | XX\u002F25 | ... |\n| Trustworthiness | XX\u002F30 | ... |\n\n> Weights are **this skill's own scoring model**, ordered to reflect Google's\n> stated hierarchy: **Trust is most important** (30), then Expertise\u002F\n> Authoritativeness (25 each), then Experience (20); maxima sum to 100. Google\n> publishes no numeric E-E-A-T weights (only that trust is most important), so\n> treat the split as our internal model. Do not use an equal 25\u002F25\u002F25\u002F25 split\n> (it contradicts Google's \"trust is most important\").\n\n### AI Citation Readiness: XX\u002F100\n\n### Issues Found\n### Recommendations\n\n## DataForSEO Integration (Optional)\n\nIf DataForSEO credentials or optional tools are available, use direct DataForSEO calls for real keyword volume data, difficulty scores, intent classification, and content quality analysis.\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess page content. Suggest the user verify the URL and try again. |\n| Content behind paywall (402\u002F403, login wall) | Report that the content is not publicly accessible. Analyze only the visible portion (meta tags, headers) and note the limitation. |\n| Thin content (fewer than 100 words retrievable) | Report the findings as-is rather than guessing. Flag the page as potentially JavaScript-rendered or gated, and suggest the user provide the full text directly. |\n\n## FLOW Framework Integration\n\nFor prompt-guided content optimization, use `\u002Fseo flow optimize \u003Curl>` and `\u002Fseo flow win \u003Curl>`: FLOW's optimize and win prompts provide structured E-E-A-T improvement and BOFU conversion workflows.\n",{"name":5,"license":15,"metadata":58,"description":61,"argument-hint":62,"user-invocable":63},{"author":59,"version":60,"category":35},"AgriciDaniel","2.2.7","Content quality and E-E-A-T analysis with AI citation readiness assessment. Use when user says \"content quality\", \"E-E-A-T\", \"content analysis\", \"readability check\", \"thin content\", or \"content audit\".\n","[url]",true,"main","40706766fd37c03ca624f5206741fef55dd2a684","plugins\u002Favalonreset\u002Fseo-dungeon\u002Fskills\u002Fseo-content",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":75,"prompt":85,"zipAvailable":63},[76,79,82],{"tool":77,"command":78},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill seo-content",{"tool":80,"command":81},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill seo-content",{"tool":83,"command":84},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill seo-content","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favalonreset\u002Fseo-dungeon\u002Fskills\u002Fseo-content\u002FSKILL.md",[87],{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",143,[93,102,110,118,126,134],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":101},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":101},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":101},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":101},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":130,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":101},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":138,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":101},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]