[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DYGPQWZP04V525TK90G4MD":3,"skill-same:01M7DYGPQWZP04V525TK90G4MD":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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7DYGPQWZP04V525TK90G4MD","schema",null,"Use when adding, fixing, or reviewing structured data: JSON-LD for articles, products, FAQs, breadcrumbs, organizations, and local businesses, and what to do when markup doesn't earn a rich result.","vercel\u002Feve","vercel","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F14985020?v=4","01M75TEEHHNJR9E6CG84ENB3MS","Vercel","01M75TEEJ5BJVTCPRH9YAWSMW4",5902,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fmarketing-team-eve-template\u002Fagent\u002Fsubagents\u002Fseo\u002Fskills\u002Fschema\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Use when adding, fixing, or reviewing structured data: JSON-LD for articles, products, FAQs, breadcrumbs, organizations, and local businesses, and what to do when markup doesn't earn a rich result.\"\n---\n\n# Schema markup\n\nStructured data tells a search engine what a page is rather than making it rank. Done right it earns a richer result and makes the page easier for an engine to summarize. Done wrong it earns a manual action.\n\nFour rules govern everything below:\n\n- Mark up only what the page visibly shows. Schema describing content a reader can't see is a spam signal, and it's the single most common reason markup gets penalized rather than ignored.\n- Use JSON-LD, in a `\u003Cscript type=\"application\u002Fld+json\">` in the head or at the end of the body. Google recommends it, and it's the only format you can add without touching the page's markup.\n- Only claim types and properties the engine actually supports for a rich result. Valid schema.org markup with no supported result does nothing for search, which is fine, but don't promise a rich result it can't produce.\n- Validate before it ships, then watch Search Console. Markup that validates can still be wrong about the page.\n\n## Choosing the type\n\n| Type                 | Use on                                 | Required                                       |\n| -------------------- | -------------------------------------- | ---------------------------------------------- |\n| Organization         | Homepage, about page                   | `name`, `url`                                  |\n| WebSite              | Homepage, to declare a site search     | `name`, `url`                                  |\n| Article, BlogPosting | Posts and news                         | `headline`, `image`, `datePublished`, `author` |\n| Product              | Product pages                          | `name`, `image`, `offers`                      |\n| SoftwareApplication  | App and SaaS pages                     | `name`, `offers`                               |\n| FAQPage              | A page with real questions and answers | `mainEntity`                                   |\n| HowTo                | Step-by-step instructions              | `name`, `step`                                 |\n| BreadcrumbList       | Any page with breadcrumbs              | `itemListElement`                              |\n| LocalBusiness        | A location page                        | `name`, `address`                              |\n| Event                | Events and webinars                    | `name`, `startDate`, `location`                |\n\n`references\u002Fschema-examples.md` has a complete, valid block for each of these plus a combined `@graph` and a Next.js pattern. `references\u002Frequired-properties.json` is the same table in the form `validate_schema` reads, so adding a type means editing both.\n\nWhen a page needs several types, prefer one `@graph` array over several separate script tags: entities can then reference each other by `@id` instead of repeating themselves.\n\n## Reviewing existing markup\n\nA fetch of the page shows only server-rendered JSON-LD. CMS SEO plugins commonly inject it client side, so absence in fetched HTML is not absence on the page. Report what the server HTML contained, then send them to the Rich Results Test, which renders JavaScript.\n\nWhen markup exists but earns nothing, check in this order: a required property missing, a value in the wrong shape (dates must be ISO 8601, URLs absolute, enumerations exact), the type having no rich result to earn, or the markup describing something the page doesn't show.\n\nRun `validate_schema` on any block before you hand it over. It parses the JSON, checks each type against the required properties in `references\u002Frequired-properties.json`, and catches the two value shapes that fail most often: a date that isn't ISO 8601 and a relative URL. It's mechanical, so a clean result means the syntax is right and nothing more.\n\nThen point the user at the Rich Results Test at https:\u002F\u002Fsearch.google.com\u002Ftest\u002Frich-results for eligibility, and the schema.org validator at https:\u002F\u002Fvalidator.schema.org\u002F for correctness against the vocabulary. Those answer different questions from each other and from the tool, so a block can pass one and fail another. None of the three can tell you whether the markup describes what the page actually shows, which is the accuracy rule above and still yours to check.\n\n## Handing it over\n\nGive the complete block, ready to paste, with the page's real values filled in rather than placeholders. Say where it goes, name any property you had to leave out and why, and note which rich result it makes the page eligible for, with eligible being the honest word. Google decides whether to show one.\n\n## Sources\n\n- Google Search Central, Intro to how structured data works: https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fappearance\u002Fstructured-data\u002Fintro-structured-data\n- Google Search Central, Structured data general guidelines: https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fappearance\u002Fstructured-data\u002Fsd-policies\n- Google Search Central, Search gallery of supported result types: https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fappearance\u002Fstructured-data\u002Fsearch-gallery\n- schema.org: https:\u002F\u002Fschema.org\u002F\n","# Schema markup\n\nStructured data tells a search engine what a page is rather than making it rank. Done right it earns a richer result and makes the page easier for an engine to summarize. Done wrong it earns a manual action.\n\nFour rules govern everything below:\n\n- Mark up only what the page visibly shows. Schema describing content a reader can't see is a spam signal, and it's the single most common reason markup gets penalized rather than ignored.\n- Use JSON-LD, in a `\u003Cscript type=\"application\u002Fld+json\">` in the head or at the end of the body. Google recommends it, and it's the only format you can add without touching the page's markup.\n- Only claim types and properties the engine actually supports for a rich result. Valid schema.org markup with no supported result does nothing for search, which is fine, but don't promise a rich result it can't produce.\n- Validate before it ships, then watch Search Console. Markup that validates can still be wrong about the page.\n\n## Choosing the type\n\n| Type                 | Use on                                 | Required                                       |\n| -------------------- | -------------------------------------- | ---------------------------------------------- |\n| Organization         | Homepage, about page                   | `name`, `url`                                  |\n| WebSite              | Homepage, to declare a site search     | `name`, `url`                                  |\n| Article, BlogPosting | Posts and news                         | `headline`, `image`, `datePublished`, `author` |\n| Product              | Product pages                          | `name`, `image`, `offers`                      |\n| SoftwareApplication  | App and SaaS pages                     | `name`, `offers`                               |\n| FAQPage              | A page with real questions and answers | `mainEntity`                                   |\n| HowTo                | Step-by-step instructions              | `name`, `step`                                 |\n| BreadcrumbList       | Any page with breadcrumbs              | `itemListElement`                              |\n| LocalBusiness        | A location page                        | `name`, `address`                              |\n| Event                | Events and webinars                    | `name`, `startDate`, `location`                |\n\n`references\u002Fschema-examples.md` has a complete, valid block for each of these plus a combined `@graph` and a Next.js pattern. `references\u002Frequired-properties.json` is the same table in the form `validate_schema` reads, so adding a type means editing both.\n\nWhen a page needs several types, prefer one `@graph` array over several separate script tags: entities can then reference each other by `@id` instead of repeating themselves.\n\n## Reviewing existing markup\n\nA fetch of the page shows only server-rendered JSON-LD. CMS SEO plugins commonly inject it client side, so absence in fetched HTML is not absence on the page. Report what the server HTML contained, then send them to the Rich Results Test, which renders JavaScript.\n\nWhen markup exists but earns nothing, check in this order: a required property missing, a value in the wrong shape (dates must be ISO 8601, URLs absolute, enumerations exact), the type having no rich result to earn, or the markup describing something the page doesn't show.\n\nRun `validate_schema` on any block before you hand it over. It parses the JSON, checks each type against the required properties in `references\u002Frequired-properties.json`, and catches the two value shapes that fail most often: a date that isn't ISO 8601 and a relative URL. It's mechanical, so a clean result means the syntax is right and nothing more.\n\nThen point the user at the Rich Results Test at https:\u002F\u002Fsearch.google.com\u002Ftest\u002Frich-results for eligibility, and the schema.org validator at https:\u002F\u002Fvalidator.schema.org\u002F for correctness against the vocabulary. Those answer different questions from each other and from the tool, so a block can pass one and fail another. None of the three can tell you whether the markup describes what the page actually shows, which is the accuracy rule above and still yours to check.\n\n## Handing it over\n\nGive the complete block, ready to paste, with the page's real values filled in rather than placeholders. Say where it goes, name any property you had to leave out and why, and note which rich result it makes the page eligible for, with eligible being the honest word. Google decides whether to show one.\n\n## Sources\n\n- Google Search Central, Intro to how structured data works: https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fappearance\u002Fstructured-data\u002Fintro-structured-data\n- Google Search Central, Structured data general guidelines: https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fappearance\u002Fstructured-data\u002Fsd-policies\n- Google Search Central, Search gallery of supported result types: https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fappearance\u002Fstructured-data\u002Fsearch-gallery\n- schema.org: https:\u002F\u002Fschema.org\u002F\n",{"description":7},"main","2e99dc3564dd243224e74b970a3c990b625cc8c0","apps\u002Ftemplates\u002Fmarketing-team-eve-template\u002Fagent\u002Fsubagents\u002Fseo\u002Fskills\u002Fschema",656,"https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve","https:\u002F\u002Feve.dev","https:\u002F\u002Fgithub.com\u002Fvercel","https:\u002F\u002Fvercel.com","Agentic infrastructure for every app and agent.","2026-11-15 05:08:34",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add vercel\u002Feve --skill schema",{"tool":40,"command":41},"bunx","bunx skills add vercel\u002Feve --skill schema",{"tool":43,"command":44},"pnpm","pnpm dlx skills add vercel\u002Feve --skill schema","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fmarketing-team-eve-template\u002Fagent\u002Fsubagents\u002Fseo\u002Fskills\u002Fschema\u002FSKILL.md",true,[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Frequired-properties.json","REFERENCE","参考文档",470,"https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fmarketing-team-eve-template\u002Fagent\u002Fsubagents\u002Fseo\u002Fskills\u002Fschema\u002Freferences\u002Frequired-properties.json",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fschema-examples.md",8411,"https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fmarketing-team-eve-template\u002Fagent\u002Fsubagents\u002Fseo\u002Fskills\u002Fschema\u002Freferences\u002Fschema-examples.md",[59,66,72,79,86,93],{"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},"01M7DYJETPKENT6T9THCB7WKFD","writing-quality","The review rubric: writing-quality rules and reference lists for judging a content draft, covering AI-sounding phrasing, bloated wording, structure, and web-content specs. Load at the start of every review.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fsubagents\u002Freviewer\u002Fskills\u002Fwriting-quality\u002FSKILL.md",[],[],{"skillNo":67,"name":61,"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},"01M7DYJAZM6Y5VNF2PCM01N145","Writing-quality guardrails for any prose the agent drafts or edits: blog posts, page copy, Notion drafts, release notes, marketing text. Use this skill whenever writing or revising content meant for humans to read, to keep the prose natural, plain, and free of AI-sounding phrasing. Not needed for code, queries, or structural CMS work.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fwriting-quality\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},"01M7DYJ40G4YADA5P8YAEQ7W7F","seo-aeo-best-practices","SEO and AEO best practices for metadata, Open Graph, sitemaps, robots.txt, hreflang, JSON-LD structured data, EEAT, and content optimized for search engines and AI answer surfaces. Use this skill when implementing page SEO, technical SEO, schema markup, international SEO, AI-overview readiness, or improving content for Google, ChatGPT, Perplexity, and similar assistants.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fseo-aeo-best-practices\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},"01M7DYHX5JXJFHF2DZV64VFC13","sanity-best-practices","Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this skill whenever working with Sanity schemas, defineType or defineField, GROQ or defineQuery, content modeling, Presentation or preview setups, Sanity-powered frontend integrations, Sanity Functions, documentEventHandler, defineDocumentFunction, defineMediaLibraryAssetFunction, @sanity\u002Ffunctions, @sanity\u002Fblueprints, sanity.blueprint.ts, event-driven content automation, or when reviewing and fixing a Sanity codebase.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fsanity-best-practices\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},"01M7DYHQG96APC7EV3FANC90WX","portable-text-serialization","Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fportable-text-serialization\u002FSKILL.md",[],[],{"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":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7DYHJJ89WGRXXVWJAQNQW9M","portable-text-conversion","Convert HTML and Markdown content into Portable Text blocks for Sanity. Use when migrating content from legacy CMSs, importing HTML or Markdown into Sanity, building content pipelines that ingest external content, converting rich text between formats, or programmatically creating Portable Text documents. Covers @portabletext\u002Fmarkdown (markdownToPortableText), @portabletext\u002Fblock-tools (htmlToBlocks), custom deserializers, and the Portable Text specification for manual block construction.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fportable-text-conversion\u002FSKILL.md",[],[]]