[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CDB37RVKSMFS7P0FJX5TCG":3,"skill-same:01M7CDB37RVKSMFS7P0FJX5TCG":50},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7CDB37RVKSMFS7P0FJX5TCG","seo-aeo-schema-generator",null,"Generates valid JSON-LD structured data for 10 schema types with rich result eligibility validation and implementation-ready script blocks. Activate when the user wants to generate schema markup, JSON-LD, or structured data for any page.","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-aeo-schema-generator\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: seo-aeo-schema-generator\ndescription: \"Generates valid JSON-LD structured data for 10 schema types with rich result eligibility validation and implementation-ready script blocks. Activate when the user wants to generate schema markup, JSON-LD, or structured data for any page.\"\nrisk: safe\nsource: community\ndate_added: \"2026-04-01\"\n---\n\n# SEO-AEO Schema Generator\n\n## Overview\n\nGenerates implementation-ready JSON-LD schema markup for 10 schema types including FAQPage, Article, Product, HowTo, and BreadcrumbList. Validates all required fields against Google rich result eligibility rules, flags missing fields with exact fix instructions, and outputs one clean `\u003Cscript>` block per schema type ready to paste into the page `\u003Chead>`.\n\nPart of the [SEO-AEO Engine](https:\u002F\u002Fgithub.com\u002Fmrprewsh\u002Fseo-aeo-engine).\n\n## When to Use This Skill\n\n- Use when adding structured data to a new landing page or blog post\n- Use when a page needs FAQ rich results or product star ratings in search\n- Use when validating existing schema for Google rich result eligibility\n- Use after the content-quality-auditor flags missing schema\n\n## Supported Schema Types\n\n| Type | Rich Result Unlocked |\n|------|---------------------|\n| FAQPage | FAQ accordion in SERP — AEO critical |\n| Article | Article rich result, Top Stories |\n| Product | Price, availability, rating in SERP |\n| HowTo | Step-by-step rich result |\n| Review | Star rating in SERP |\n| AggregateRating | Star rating with review count |\n| BreadcrumbList | Breadcrumb path in SERP URL |\n| Organization | Brand knowledge panel signals |\n| WebPage | Enhanced page understanding |\n| WebSite | Sitelinks Searchbox |\n\n## How It Works\n\n### Step 1: Recommend Schema Types\nIf schema types are not specified, recommend the appropriate types based on the page type. Landing pages get FAQPage + Product + BreadcrumbList. Blog posts get Article + FAQPage + BreadcrumbList.\n\n### Step 2: Use Built-In Schema Templates\nUsing your knowledge of schema.org and Google's rich result requirements, construct the JSON-LD template for each requested schema type. Use the required and recommended fields listed in the Google Rich Results documentation for that type.\n\n### Step 3: Populate Fields\nMap all page data to template placeholders. Check every required field against the rich result eligibility rules.\n\n### Step 4: Validate\nFlag any missing required field as a Critical issue. Flag missing recommended fields as warnings. Do not output schema with missing required fields.\n\n### Step 5: Output Script Blocks\nWrite one `\u003Cscript type=\"application\u002Fld+json\">` block per schema type. Include implementation instructions and testing tool links.\n\n## Examples\n\n### Example: FAQPage Schema Output\n```html\n\u003Cscript type=\"application\u002Fld+json\">\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What is Syncro?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Syncro is a remote-first project management platform for distributed engineering teams. It centralises task tracking, async communication, and sprint planning in one tool.\"\n      }\n    }\n  ]\n}\n\u003C\u002Fscript>\n```\n\n## Best Practices\n\n- ✅ **Do:** Always include FAQPage schema on any page with a FAQ section — it is the strongest AEO signal\n- ✅ **Do:** Use one `\u003Cscript>` block per schema type — never combine multiple types\n- ✅ **Do:** Test every output in Google's Rich Results Test before deploying\n- ❌ **Don't:** Use relative URLs anywhere in schema — all URLs must start with `https:\u002F\u002F`\n- ❌ **Don't:** Leave placeholder text in any field before deploying\n- ❌ **Don't:** Use HTML tags inside JSON-LD string values\n\n## Common Pitfalls\n\n- **Problem:** Schema passes validation but rich result doesn't appear in search\n  **Solution:** Rich results can take weeks to appear after deployment. Request re-indexing in Google Search Console immediately after adding schema.\n\n- **Problem:** Product schema missing star rating display\n  **Solution:** Add AggregateRating object with ratingValue, reviewCount, bestRating, and worstRating — all four fields required.\n\n## Related Skills\n\n- `@seo-aeo-landing-page-writer` — provides the FAQ and product data for schema population\n- `@seo-aeo-content-quality-auditor` — flags schema gaps during the audit\n\n## Additional Resources\n\n- [SEO-AEO Engine Repository](https:\u002F\u002Fgithub.com\u002Fmrprewsh\u002Fseo-aeo-engine)\n- [Full Schema Generator SKILL.md](https:\u002F\u002Fgithub.com\u002Fmrprewsh\u002Fseo-aeo-engine\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fschema-generator\u002FSKILL.md)\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","# SEO-AEO Schema Generator\n\n## Overview\n\nGenerates implementation-ready JSON-LD schema markup for 10 schema types including FAQPage, Article, Product, HowTo, and BreadcrumbList. Validates all required fields against Google rich result eligibility rules, flags missing fields with exact fix instructions, and outputs one clean `\u003Cscript>` block per schema type ready to paste into the page `\u003Chead>`.\n\nPart of the [SEO-AEO Engine](https:\u002F\u002Fgithub.com\u002Fmrprewsh\u002Fseo-aeo-engine).\n\n## When to Use This Skill\n\n- Use when adding structured data to a new landing page or blog post\n- Use when a page needs FAQ rich results or product star ratings in search\n- Use when validating existing schema for Google rich result eligibility\n- Use after the content-quality-auditor flags missing schema\n\n## Supported Schema Types\n\n| Type | Rich Result Unlocked |\n|------|---------------------|\n| FAQPage | FAQ accordion in SERP — AEO critical |\n| Article | Article rich result, Top Stories |\n| Product | Price, availability, rating in SERP |\n| HowTo | Step-by-step rich result |\n| Review | Star rating in SERP |\n| AggregateRating | Star rating with review count |\n| BreadcrumbList | Breadcrumb path in SERP URL |\n| Organization | Brand knowledge panel signals |\n| WebPage | Enhanced page understanding |\n| WebSite | Sitelinks Searchbox |\n\n## How It Works\n\n### Step 1: Recommend Schema Types\nIf schema types are not specified, recommend the appropriate types based on the page type. Landing pages get FAQPage + Product + BreadcrumbList. Blog posts get Article + FAQPage + BreadcrumbList.\n\n### Step 2: Use Built-In Schema Templates\nUsing your knowledge of schema.org and Google's rich result requirements, construct the JSON-LD template for each requested schema type. Use the required and recommended fields listed in the Google Rich Results documentation for that type.\n\n### Step 3: Populate Fields\nMap all page data to template placeholders. Check every required field against the rich result eligibility rules.\n\n### Step 4: Validate\nFlag any missing required field as a Critical issue. Flag missing recommended fields as warnings. Do not output schema with missing required fields.\n\n### Step 5: Output Script Blocks\nWrite one `\u003Cscript type=\"application\u002Fld+json\">` block per schema type. Include implementation instructions and testing tool links.\n\n## Examples\n\n### Example: FAQPage Schema Output\n```html\n\u003Cscript type=\"application\u002Fld+json\">\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What is Syncro?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Syncro is a remote-first project management platform for distributed engineering teams. It centralises task tracking, async communication, and sprint planning in one tool.\"\n      }\n    }\n  ]\n}\n\u003C\u002Fscript>\n```\n\n## Best Practices\n\n- ✅ **Do:** Always include FAQPage schema on any page with a FAQ section — it is the strongest AEO signal\n- ✅ **Do:** Use one `\u003Cscript>` block per schema type — never combine multiple types\n- ✅ **Do:** Test every output in Google's Rich Results Test before deploying\n- ❌ **Don't:** Use relative URLs anywhere in schema — all URLs must start with `https:\u002F\u002F`\n- ❌ **Don't:** Leave placeholder text in any field before deploying\n- ❌ **Don't:** Use HTML tags inside JSON-LD string values\n\n## Common Pitfalls\n\n- **Problem:** Schema passes validation but rich result doesn't appear in search\n  **Solution:** Rich results can take weeks to appear after deployment. Request re-indexing in Google Search Console immediately after adding schema.\n\n- **Problem:** Product schema missing star rating display\n  **Solution:** Add AggregateRating object with ratingValue, reviewCount, bestRating, and worstRating — all four fields required.\n\n## Related Skills\n\n- `@seo-aeo-landing-page-writer` — provides the FAQ and product data for schema population\n- `@seo-aeo-content-quality-auditor` — flags schema gaps during the audit\n\n## Additional Resources\n\n- [SEO-AEO Engine Repository](https:\u002F\u002Fgithub.com\u002Fmrprewsh\u002Fseo-aeo-engine)\n- [Full Schema Generator SKILL.md](https:\u002F\u002Fgithub.com\u002Fmrprewsh\u002Fseo-aeo-engine\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fschema-generator\u002FSKILL.md)\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":7},"safe","community","2026-04-01","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fseo-aeo-schema-generator",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":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill seo-aeo-schema-generator",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill seo-aeo-schema-generator",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill seo-aeo-schema-generator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fseo-aeo-schema-generator\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"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":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"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":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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",[],[]]