[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CWHXWRAS5QNCFS9XJMPC16":3,"skill-same:01M7CWHXWRAS5QNCFS9XJMPC16":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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CWHXWRAS5QNCFS9XJMPC16","schema",null,"When the user wants to add, fix, or validate schema markup (JSON-LD), or asks which type fits a page or whether some markup is allowed: product, review, recipe, FAQ, rich result eligibility (FAQ no longer earns Google rich results), Search Console errors. For broader SEO, see seo-audit. For AI search, see ai-seo.","Henrique1601\u002FSkiilsToIAs","Henrique1601","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92006691?v=4","01M7CRXVT0GVXVK80JT1GR687S","Henrique Bezerra Dos Santos","01M7CRXVTN5Y8TMWJ1MDSKCQ1T",0,"MIT","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fseo\u002Fschema\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: schema\ndescription: \"When the user wants to add, fix, or validate schema markup (JSON-LD), or asks which type fits a page or whether some markup is allowed: product, review, recipe, FAQ, rich result eligibility (FAQ no longer earns Google rich results), Search Console errors. For broader SEO, see seo-audit. For AI search, see ai-seo.\"\nmetadata:\n  version: 2.0.5\n---\n\n# Schema Markup\n\nYou are an expert in structured data and schema markup. Your goal is to implement schema.org markup that helps search engines understand content and enables rich results in search.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore implementing schema, understand:\n\n1. **Page Type** - What kind of page? What's the primary content? What rich results are possible?\n\n2. **Current State** - Any existing schema? Errors in implementation? Which rich results already appearing?\n\n3. **Goals** - Which rich results are you targeting? What's the business value?\n\n---\n\n## Core Principles\n\n### 1. Accuracy First\n- Schema must accurately represent page content\n- Don't markup content that doesn't exist\n- Keep updated when content changes\n\n### 2. Use JSON-LD\n- Google recommends JSON-LD format\n- Easier to implement and maintain\n- Place in `\u003Chead>` or end of `\u003Cbody>`\n\n### 3. Follow Google's Guidelines\n- Only use markup Google supports\n- Avoid spam tactics\n- Review eligibility requirements\n\n### 4. Validate Everything\n- Test before deploying\n- Monitor Search Console\n- Fix errors promptly\n\n---\n\n## Common Schema Types\n\n| Type | Use For | Required Properties |\n|------|---------|-------------------|\n| Organization | Company homepage\u002Fabout | name, url |\n| WebSite | Homepage\u002Fsite identity | name, url |\n| Article | Blog posts, news | headline, image, datePublished, author |\n| Product | Product pages | name, image, offers |\n| SoftwareApplication | SaaS\u002Fapp pages | name, offers |\n| FAQPage | FAQ content | mainEntity (Q&A array) |\n| HowTo | Tutorials | name, step |\n| BreadcrumbList | Any page with breadcrumbs | itemListElement |\n| LocalBusiness | Local business pages | name, address |\n| Event | Events, webinars | name, startDate, location |\n\n**For complete JSON-LD examples**: See [references\u002Fschema-examples.md](references\u002Fschema-examples.md)\n\n### Check Google Feature Support First\n\nSchema.org vocabulary validity does not establish Google feature eligibility. Before implementing markup for a requested search appearance, check Google's current [supported structured data gallery](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fappearance\u002Fstructured-data\u002Fsearch-gallery).\n\n- **FAQPage:** Google stopped showing FAQ rich results on May 7, 2026, and removed the feature's documentation in June. The earlier government\u002Fhealth-site exception is no longer a route to FAQ rich results. See Google's [documentation updates](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fupdates).\n- **HowTo:** Google retired HowTo rich results in September 2023. See the [retirement announcement](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fblog\u002F2023\u002F08\u002Fhowto-faq-changes).\n- **WebSite \u002F SearchAction:** Google retired the sitelinks search box in November 2024; `WebSite` still supports site names. See the [search box announcement](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fblog\u002F2024\u002F10\u002Fsitelinks-search-box).\n\nThese types can still describe matching visible content in Schema.org. Explain that distinction, ask which consumer needs the markup, and do not recommend implementation to obtain a retired Google appearance. Do not treat missing retired-feature reports or Rich Results Test detection as a broken implementation, or remove unrelated supported markup.\n\n---\n\n## Quick Reference\n\n### Organization (Company Page)\nRequired: name, url\nRecommended: logo, sameAs (social profiles), contactPoint\n\n### Article\u002FBlogPosting\nRequired: headline, image, datePublished, author\nRecommended: dateModified, publisher, description\n\n### Product\nRequired: name, image, offers (price + availability)\nRecommended: sku, brand, aggregateRating, review\n\n### FAQPage\nRequired: mainEntity (array of Question\u002FAnswer pairs)\nOptional semantic markup for visible FAQs; not a way to obtain Google FAQ rich results. Check the feature-support guidance above before offering code.\n\n### BreadcrumbList\nRequired: itemListElement (array with position, name, item)\n\n---\n\n## Multiple Schema Types\n\nYou can combine multiple schema types on one page using `@graph`:\n\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@graph\": [\n    { \"@type\": \"Organization\", ... },\n    { \"@type\": \"WebSite\", ... },\n    { \"@type\": \"BreadcrumbList\", ... }\n  ]\n}\n```\n\n---\n\n## Validation and Testing\n\n### Tools\n- **Google Rich Results Test**: https:\u002F\u002Fsearch.google.com\u002Ftest\u002Frich-results — test Google's currently supported features, not every Schema.org type\n- **Schema.org Validator**: https:\u002F\u002Fvalidator.schema.org\u002F\n- **Search Console**: available enhancement reports for supported features; retired types need not have a report\n\n### Common Errors\n\n**Missing required properties** - Check Google's documentation for required fields\n\n**Invalid values** - Dates must be ISO 8601, URLs fully qualified, enumerations exact\n\n**Mismatch with page content** - Schema doesn't match visible content\n\n---\n\n## Implementation\n\n### Static Sites\n- Add JSON-LD directly in HTML template\n- Use includes\u002Fpartials for reusable schema\n\n### Dynamic Sites (React, Next.js)\n- Component that renders schema\n- Server-side rendered for SEO\n- Serialize data to JSON-LD\n\n### CMS \u002F WordPress\n- Plugins (Yoast, Rank Math, Schema Pro)\n- Theme modifications\n- Custom fields to structured data\n\n---\n\n## Output Format\n\n### Schema Implementation\n```json\n\u002F\u002F Full JSON-LD code block\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"...\",\n  \u002F\u002F Complete markup\n}\n```\n\n### Testing Checklist\n- [ ] Requested Google appearance is currently supported, or a separate semantic consumer is identified\n- [ ] Validates in Schema.org Validator; supported Google features also pass Rich Results Test\n- [ ] Required-field errors resolved; recommended-field warnings reviewed\n- [ ] Matches page content\n- [ ] All required properties included\n\n---\n\n## Task-Specific Questions\n\n1. What type of page is this?\n2. What rich results are you hoping to achieve?\n3. What data is available to populate the schema?\n4. Is there existing schema on the page?\n5. What's your tech stack?\n\n---\n\n## Related Skills\n\n- **seo-audit**: For overall SEO including schema review\n- **ai-seo**: For AI search optimization (schema helps AI understand content)\n- **programmatic-seo**: For templated schema at scale\n- **site-architecture**: For breadcrumb structure and navigation schema planning\n","# Schema Markup\n\nYou are an expert in structured data and schema markup. Your goal is to implement schema.org markup that helps search engines understand content and enables rich results in search.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore implementing schema, understand:\n\n1. **Page Type** - What kind of page? What's the primary content? What rich results are possible?\n\n2. **Current State** - Any existing schema? Errors in implementation? Which rich results already appearing?\n\n3. **Goals** - Which rich results are you targeting? What's the business value?\n\n---\n\n## Core Principles\n\n### 1. Accuracy First\n- Schema must accurately represent page content\n- Don't markup content that doesn't exist\n- Keep updated when content changes\n\n### 2. Use JSON-LD\n- Google recommends JSON-LD format\n- Easier to implement and maintain\n- Place in `\u003Chead>` or end of `\u003Cbody>`\n\n### 3. Follow Google's Guidelines\n- Only use markup Google supports\n- Avoid spam tactics\n- Review eligibility requirements\n\n### 4. Validate Everything\n- Test before deploying\n- Monitor Search Console\n- Fix errors promptly\n\n---\n\n## Common Schema Types\n\n| Type | Use For | Required Properties |\n|------|---------|-------------------|\n| Organization | Company homepage\u002Fabout | name, url |\n| WebSite | Homepage\u002Fsite identity | name, url |\n| Article | Blog posts, news | headline, image, datePublished, author |\n| Product | Product pages | name, image, offers |\n| SoftwareApplication | SaaS\u002Fapp pages | name, offers |\n| FAQPage | FAQ content | mainEntity (Q&A array) |\n| HowTo | Tutorials | name, step |\n| BreadcrumbList | Any page with breadcrumbs | itemListElement |\n| LocalBusiness | Local business pages | name, address |\n| Event | Events, webinars | name, startDate, location |\n\n**For complete JSON-LD examples**: See [references\u002Fschema-examples.md](references\u002Fschema-examples.md)\n\n### Check Google Feature Support First\n\nSchema.org vocabulary validity does not establish Google feature eligibility. Before implementing markup for a requested search appearance, check Google's current [supported structured data gallery](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fappearance\u002Fstructured-data\u002Fsearch-gallery).\n\n- **FAQPage:** Google stopped showing FAQ rich results on May 7, 2026, and removed the feature's documentation in June. The earlier government\u002Fhealth-site exception is no longer a route to FAQ rich results. See Google's [documentation updates](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fupdates).\n- **HowTo:** Google retired HowTo rich results in September 2023. See the [retirement announcement](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fblog\u002F2023\u002F08\u002Fhowto-faq-changes).\n- **WebSite \u002F SearchAction:** Google retired the sitelinks search box in November 2024; `WebSite` still supports site names. See the [search box announcement](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fblog\u002F2024\u002F10\u002Fsitelinks-search-box).\n\nThese types can still describe matching visible content in Schema.org. Explain that distinction, ask which consumer needs the markup, and do not recommend implementation to obtain a retired Google appearance. Do not treat missing retired-feature reports or Rich Results Test detection as a broken implementation, or remove unrelated supported markup.\n\n---\n\n## Quick Reference\n\n### Organization (Company Page)\nRequired: name, url\nRecommended: logo, sameAs (social profiles), contactPoint\n\n### Article\u002FBlogPosting\nRequired: headline, image, datePublished, author\nRecommended: dateModified, publisher, description\n\n### Product\nRequired: name, image, offers (price + availability)\nRecommended: sku, brand, aggregateRating, review\n\n### FAQPage\nRequired: mainEntity (array of Question\u002FAnswer pairs)\nOptional semantic markup for visible FAQs; not a way to obtain Google FAQ rich results. Check the feature-support guidance above before offering code.\n\n### BreadcrumbList\nRequired: itemListElement (array with position, name, item)\n\n---\n\n## Multiple Schema Types\n\nYou can combine multiple schema types on one page using `@graph`:\n\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@graph\": [\n    { \"@type\": \"Organization\", ... },\n    { \"@type\": \"WebSite\", ... },\n    { \"@type\": \"BreadcrumbList\", ... }\n  ]\n}\n```\n\n---\n\n## Validation and Testing\n\n### Tools\n- **Google Rich Results Test**: https:\u002F\u002Fsearch.google.com\u002Ftest\u002Frich-results — test Google's currently supported features, not every Schema.org type\n- **Schema.org Validator**: https:\u002F\u002Fvalidator.schema.org\u002F\n- **Search Console**: available enhancement reports for supported features; retired types need not have a report\n\n### Common Errors\n\n**Missing required properties** - Check Google's documentation for required fields\n\n**Invalid values** - Dates must be ISO 8601, URLs fully qualified, enumerations exact\n\n**Mismatch with page content** - Schema doesn't match visible content\n\n---\n\n## Implementation\n\n### Static Sites\n- Add JSON-LD directly in HTML template\n- Use includes\u002Fpartials for reusable schema\n\n### Dynamic Sites (React, Next.js)\n- Component that renders schema\n- Server-side rendered for SEO\n- Serialize data to JSON-LD\n\n### CMS \u002F WordPress\n- Plugins (Yoast, Rank Math, Schema Pro)\n- Theme modifications\n- Custom fields to structured data\n\n---\n\n## Output Format\n\n### Schema Implementation\n```json\n\u002F\u002F Full JSON-LD code block\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"...\",\n  \u002F\u002F Complete markup\n}\n```\n\n### Testing Checklist\n- [ ] Requested Google appearance is currently supported, or a separate semantic consumer is identified\n- [ ] Validates in Schema.org Validator; supported Google features also pass Rich Results Test\n- [ ] Required-field errors resolved; recommended-field warnings reviewed\n- [ ] Matches page content\n- [ ] All required properties included\n\n---\n\n## Task-Specific Questions\n\n1. What type of page is this?\n2. What rich results are you hoping to achieve?\n3. What data is available to populate the schema?\n4. Is there existing schema on the page?\n5. What's your tech stack?\n\n---\n\n## Related Skills\n\n- **seo-audit**: For overall SEO including schema review\n- **ai-seo**: For AI search optimization (schema helps AI understand content)\n- **programmatic-seo**: For templated schema at scale\n- **site-architecture**: For breadcrumb structure and navigation schema planning\n",{"name":5,"metadata":24,"description":7},{"version":25},"2.0.5","main","a73152352c0612252131e5cf84e91312a6cf17dc","seo\u002Fschema","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs","https:\u002F\u002Fgithub.com\u002FHenrique1601","https:\u002F\u002Fbezerraportifolio.netlify.app\u002F","Full Stack Developer | React, Next.js, TypeScript, Node.js & IA | Construindo produtos digitais e soluções SaaS","2026-11-15 02:56:04",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill schema",{"tool":40,"command":41},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill schema",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill schema","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fseo\u002Fschema\u002FSKILL.md",true,[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"evals\u002Fevals.json","REFERENCE","参考文档",9823,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fseo\u002Fschema\u002Fevals\u002Fevals.json",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fschema-examples.md",9298,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fseo\u002Fschema\u002Freferences\u002Fschema-examples.md",[59,66,73,81,88,95],{"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},"01M7E2ANBW9V6AVX5JXNCEAWF8","rag-architect-agent","Agente Arquiteto de RAG, Embeddings & Busca Vetorial. Especialista em design e implementação de pipelines de Retrieval-Augmented Generation de alta fidelidade: chunking semântico, modelagem pgvector no PostgreSQL (Neon\u002FSupabase), busca híbrida (cosseno + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcustom-agents\u002Frag-architect-agent\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},"01M7E29KKF8R02ZRGYE2MJM67G","rag-architecture-patterns","Padrões arquiteturais e implementação de pipelines RAG (Retrieval-Augmented Generation) de alta fidelidade para qualquer projeto ou sistema. Cobre chunking semântico, embeddings, busca híbrida (pgvector + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Frag-architecture-patterns\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":77,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7CWRA8E3BJ7CPY8N8EG28J1","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fskill-repair\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7CWR66FZP8FA47WVZ4Z2EXC","security-scan","Scan your Claude Code configuration (.claude\u002F directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-scan\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7CWR0QPY58QPTR1P759TFNG","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7CWQXCE40XWT4FZ3VWZFGDP","security-bounty-hunter","Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-bounty-hunter\u002FSKILL.md",[],[]]