[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M714J2MN7RRM42C0158E4KXE":3,"skill-same:01M714J2MN7RRM42C0158E4KXE":86},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":67,"commitSha":68,"skillDirectory":69,"forksCount":14,"repositoryHtmlUrl":70,"repositoryHomepageUrl":6,"ownerHtmlUrl":71,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":72,"install":73,"resources":85},"01M714J2MN7RRM42C0158E4KXE","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\".","sapsapshen\u002Fai-memory-router","sapsapshen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20347959?v=4","01M6XDQEF1DP50DKF37H81J3J5","shenmian","01M6XDQEJPE41Y3DT2763X8ZJN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Fseo-content\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"seo content","content","seo","with","check","content audit","use","true","e-e-a-t","readability","read","2026","audit","analysis","Bash","unknown","URL","when","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\".\nrisk: unknown\nsource: \"https:\u002F\u002Fgithub.com\u002FAgriciDaniel\u002Fclaude-seo\"\ndate_added: \"2026-03-21\"\nuser-invokable: true\nargument-hint: \"[url]\"\nallowed-tools:\n  - Read\n  - Grep\n  - Glob\n  - Bash\n  - WebFetch\n---\n\n# Content Quality & E-E-A-T Analysis\n\n## When to Use\n\n- Use when auditing content quality, readability, thin content risk, or E-E-A-T signals.\n- Use when the user wants a content-focused SEO review rather than a full technical audit.\n- Use when checking whether content is structured and trustworthy enough for search and AI citation.\n\n## E-E-A-T Framework (updated Sept 2025 QRG)\n\nRead `seo\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 now formally assess whether content appears AI-generated.\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.\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** launched publicly in May 2025 as a separate tab in Google Search, available in 180+ countries. Unlike AI Overviews (which appear above organic results), AI Mode provides a fully conversational search experience with **zero organic blue links**, making AI citation the only visibility mechanism.\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, FAQ (for non-Google AI platforms), and structured content schemas help AI systems parse and attribute content\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):**\nGEO is the emerging discipline of optimizing content specifically for AI-generated answers. Key GEO signals include: quotability (clear, concise extractable facts), attribution (source citations within your content), structure (well-organized heading hierarchy), and freshness (regularly updated data). Cross-reference the `seo-geo` skill for detailed GEO workflows.\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\u002F25 | ... |\n| Expertise | XX\u002F25 | ... |\n| Authoritativeness | XX\u002F25 | ... |\n| Trustworthiness | XX\u002F25 | ... |\n\n### AI Citation Readiness: XX\u002F100\n\n### Issues Found\n### Recommendations\n\n## DataForSEO Integration (Optional)\n\nIf DataForSEO MCP tools are available, use `kw_data_google_ads_search_volume` for real keyword volume data, `dataforseo_labs_bulk_keyword_difficulty` for difficulty scores, `dataforseo_labs_search_intent` for intent classification, and `content_analysis_summary` for 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","# Content Quality & E-E-A-T Analysis\n\n## When to Use\n\n- Use when auditing content quality, readability, thin content risk, or E-E-A-T signals.\n- Use when the user wants a content-focused SEO review rather than a full technical audit.\n- Use when checking whether content is structured and trustworthy enough for search and AI citation.\n\n## E-E-A-T Framework (updated Sept 2025 QRG)\n\nRead `seo\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 now formally assess whether content appears AI-generated.\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.\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** launched publicly in May 2025 as a separate tab in Google Search, available in 180+ countries. Unlike AI Overviews (which appear above organic results), AI Mode provides a fully conversational search experience with **zero organic blue links**, making AI citation the only visibility mechanism.\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, FAQ (for non-Google AI platforms), and structured content schemas help AI systems parse and attribute content\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):**\nGEO is the emerging discipline of optimizing content specifically for AI-generated answers. Key GEO signals include: quotability (clear, concise extractable facts), attribution (source citations within your content), structure (well-organized heading hierarchy), and freshness (regularly updated data). Cross-reference the `seo-geo` skill for detailed GEO workflows.\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\u002F25 | ... |\n| Expertise | XX\u002F25 | ... |\n| Authoritativeness | XX\u002F25 | ... |\n| Trustworthiness | XX\u002F25 | ... |\n\n### AI Citation Readiness: XX\u002F100\n\n### Issues Found\n### Recommendations\n\n## DataForSEO Integration (Optional)\n\nIf DataForSEO MCP tools are available, use `kw_data_google_ads_search_volume` for real keyword volume data, `dataforseo_labs_bulk_keyword_difficulty` for difficulty scores, `dataforseo_labs_search_intent` for intent classification, and `content_analysis_summary` for 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",{"name":5,"risk":47,"source":57,"date_added":58,"description":59,"allowed-tools":60,"argument-hint":65,"user-invokable":66},"https:\u002F\u002Fgithub.com\u002FAgriciDaniel\u002Fclaude-seo","2026-03-21","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",[61,62,63,46,64],"Read","Grep","Glob","WebFetch","[url]",true,"main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fcopilot\u002Fseo-content","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":74,"prompt":84,"zipAvailable":66},[75,78,81],{"tool":76,"command":77},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill seo-content",{"tool":79,"command":80},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill seo-content",{"tool":82,"command":83},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill seo-content","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Fseo-content\u002FSKILL.md",[],[87,108,131,141,154,171],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":96,"publishedAt":52},"01M71ATQRKG48SH06FQ697T5G9","wechat-search","Search WeChat Official Account articles using OpenClaw's web search and fetch capabilities with compliance-focused design.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fwechat-search-release\u002FSKILL.md",[93],{"categoryNo":94,"categoryName":95,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务",[97,98,99,100,101,102,103,104,105,106,107,35],"wechat search","wechat","search","capabilities","openclaw","design","web search","compliance","web","official","fetch",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":52},"01M71ATNAVGZB35PFYM2GC5N00","trend-tap","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend tap', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-tap\u002FSKILL.md",[],[115,116,117,118,46,119,99,120,121,122,123,49,124,125,126,127,128,42,129,130],"trend","trend tap","tap","api keys","time","trending","hacker","aggregator","do","brew","live","data","google","install","across","api",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":52},"01M71ATJ9AM5KM15AA8PS302EB","trend-radar","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend pulse', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-radar\u002FSKILL.md",[],[138,139,115,124,125,126,127,46,99,42,140,129,130,49,122,121,120,128,119,118],"trend radar","radar","pulse",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":52},"01M71ATGF095N3EJM9G8SD0BB5","tech-news-daily","每日科技新闻汇——从全球多个 RSS 源抓取最新科技新闻，翻译（英→中）、去重、排版成每日简报。当用户询问科技新闻、科技新鲜事、每日科技、技术动态、Daily Tech News 或类似表达时触发此技能。","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftech-news-daily\u002FSKILL.md",[],[148,149,150,151,152,153],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":163,"publishedAt":52},"01M71ATFAEAMQ17M70NQNY7SR8","summarize","Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsummarize\u002FSKILL.md",[160],{"categoryNo":161,"categoryName":162,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[156,105,164,165,166,35,124,167,168,169,117,170,128],"Audio","cli","youtube","images","https","files","pdfs",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":52},"01M71ATDNS3R0M4H936PACQAWZ","sonoscli","Control Sonos speakers (discover\u002Fstatus\u002Fplay\u002Fvolume\u002Fgroup).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsonoscli\u002FSKILL.md",[],[173,178,179,180,128,181,168,182,183,184,185,186],"status","play","go","latest","github","discover","control","cmd","volume"]