[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CDD24XGHZ6BAMJMESQK4GN":3,"skill-same:01M7CDD24XGHZ6BAMJMESQK4GN":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":43,"updatedAt":44,"install":45,"resources":57},"01M7CDD24XGHZ6BAMJMESQK4GN","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\".","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fseo-content\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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- 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\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# Content Quality & E-E-A-T Analysis\n\n## When to Use\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\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":27,"allowed-tools":28,"argument-hint":34,"user-invokable":35},"unknown","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",[29,30,31,32,33],"Read","Grep","Glob","Bash","WebFetch","[url]",true,"main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fseo-content",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":35},[47,50,53],{"tool":48,"command":49},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill seo-content",{"tool":51,"command":52},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill seo-content",{"tool":54,"command":55},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill seo-content","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fseo-content\u002FSKILL.md",[],[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"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":93,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]