[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ENKTY4EE79K6XM8AV3CQQ6":3,"skill-same:01M7ENKTY4EE79K6XM8AV3CQQ6":48},{"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":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":47},"01M7ENKTY4EE79K6XM8AV3CQQ6","blog-schema",null,"Generate complete JSON-LD schema markup for blog posts with Article\u002FBlogPosting, Person, Organization, BreadcrumbList, ImageObject, and optional FAQPage. Validates against Google requirements and warns about deprecated types. Use when user says \"schema\", \"blog schema\", \"json-ld\", \"structured data\", \"schema markup\", \"generate schema\".","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-imp-blog-schema\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: blog-schema\ndescription: >\n  Generate complete JSON-LD schema markup for blog posts with Article\u002FBlogPosting,\n  Person, Organization, BreadcrumbList, ImageObject, and optional FAQPage. Validates\n  against Google requirements and warns about deprecated types. Use when user\n  says \"schema\", \"blog schema\", \"json-ld\", \"structured data\", \"schema markup\",\n  \"generate schema\".\nuser-invokable: true\nargument-hint: \"\u003Cfile-path>\"\nlicense: MIT\n---\n\n# Blog Schema: JSON-LD Structured Data Generation\n\nGenerates complete, validated JSON-LD schema markup for blog posts using the\n@graph pattern. Combines multiple schema types into a single script tag with\nstable @id references for entity linking.\n\n## Workflow\n\n### Step 1: Read Content\n\nRead the blog post and extract all schema-relevant data:\n- **Title** (headline)\n- **Author** (name, job title, social links, credentials)\n- **Dates** (datePublished, dateModified \u002F lastUpdated)\n- **Description** (meta description)\n- **FAQ section** (question and answer pairs)\n- **Images** (cover image URL, dimensions, alt text; inline images)\n- **Organization info** (site name, URL, logo)\n- **Word count** (approximate from content length)\n- **Tags\u002Fcategories** (for BreadcrumbList category)\n- **Slug** (from filename or frontmatter)\n\n### Step 2: Generate BlogPosting Schema\n\nComplete BlogPosting with recommended properties when applicable:\n\n```json\n{\n  \"@type\": \"BlogPosting\",\n  \"@id\": \"{siteUrl}\u002Fblog\u002F{slug}#article\",\n  \"headline\": \"Concise post title\",\n  \"description\": \"Concise page-specific meta description\",\n  \"datePublished\": \"YYYY-MM-DD\",\n  \"dateModified\": \"YYYY-MM-DD\",\n  \"author\": { \"@id\": \"{siteUrl}\u002Fauthor\u002F{author-slug}#person\" },\n  \"publisher\": { \"@id\": \"{siteUrl}#organization\" },\n  \"image\": { \"@id\": \"{siteUrl}\u002Fblog\u002F{slug}#primaryimage\" },\n  \"mainEntityOfPage\": {\n    \"@type\": \"WebPage\",\n    \"@id\": \"{siteUrl}\u002Fblog\u002F{slug}\"\n  },\n  \"wordCount\": 2400,\n  \"articleBody\": \"First 200 characters of content as excerpt...\"\n}\n```\n\nGoogle's Article structured data docs do not define required Article\nproperties. Include `headline`, `datePublished`, `author`, `publisher`, and\n`image` when applicable, validate with the Rich Results Test, and treat missing\nfields as warnings unless the target surface requires them. Recommended\nproperties: description, dateModified, mainEntityOfPage, wordCount, articleBody\n(excerpt).\n\n### Step 3: Generate Person Schema\n\nAuthor schema with stable @id for cross-referencing:\n\n```json\n{\n  \"@type\": \"Person\",\n  \"@id\": \"{siteUrl}\u002Fauthor\u002F{author-slug}#person\",\n  \"name\": \"Author Name\",\n  \"jobTitle\": \"Role or Title\",\n  \"url\": \"{siteUrl}\u002Fauthor\u002F{author-slug}\",\n  \"sameAs\": [\n    \"https:\u002F\u002Ftwitter.com\u002Fhandle\",\n    \"https:\u002F\u002Flinkedin.com\u002Fin\u002Fhandle\",\n    \"https:\u002F\u002Fgithub.com\u002Fhandle\"\n  ]\n}\n```\n\nOptional properties (include when available):\n- `alumniOf` - Educational institution (Organization type)\n- `worksFor` - Employer (reference to Organization @id if same entity)\n\n### Step 4: Generate Organization Schema\n\nBlog's parent organization entity:\n\n```json\n{\n  \"@type\": \"Organization\",\n  \"@id\": \"{siteUrl}#organization\",\n  \"name\": \"Organization Name\",\n  \"url\": \"{siteUrl}\",\n  \"logo\": {\n    \"@type\": \"ImageObject\",\n    \"url\": \"{siteUrl}\u002Flogo.png\",\n    \"width\": 600,\n    \"height\": 60\n  },\n  \"sameAs\": [\n    \"https:\u002F\u002Ftwitter.com\u002Forg\",\n    \"https:\u002F\u002Flinkedin.com\u002Fcompany\u002Forg\",\n    \"https:\u002F\u002Fgithub.com\u002Forg\"\n  ]\n}\n```\n\nLogo requirements: use a valid crawlable image URL and follow the active\nOrganization and Article documentation for the target surface. Do not invent\nhard logo dimensions unless the project or current docs require them.\n\n### Step 5: Generate BreadcrumbList\n\nNavigation breadcrumb schema showing content hierarchy:\n\n```json\n{\n  \"@type\": \"BreadcrumbList\",\n  \"@id\": \"{siteUrl}\u002Fblog\u002F{slug}#breadcrumb\",\n  \"itemListElement\": [\n    {\n      \"@type\": \"ListItem\",\n      \"position\": 1,\n      \"name\": \"Home\",\n      \"item\": \"{siteUrl}\"\n    },\n    {\n      \"@type\": \"ListItem\",\n      \"position\": 2,\n      \"name\": \"Category Name\",\n      \"item\": \"{siteUrl}\u002Fblog\u002Fcategory\u002F{category-slug}\"\n    },\n    {\n      \"@type\": \"ListItem\",\n      \"position\": 3,\n      \"name\": \"Post Title\",\n      \"item\": \"{siteUrl}\u002Fblog\u002F{slug}\"\n    }\n  ]\n}\n```\n\nIf no category is available, use \"Blog\" as the second breadcrumb item with\n`{siteUrl}\u002Fblog` as the URL.\n\n### Step 6: Generate FAQPage Entity Schema (Optional)\n\nExtract Q&A pairs from the blog post's FAQ section:\n\n```json\n{\n  \"@type\": \"FAQPage\",\n  \"@id\": \"{siteUrl}\u002Fblog\u002F{slug}#faq\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What is the question?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"The complete visible answer text.\"\n      }\n    }\n  ]\n}\n```\n\nGoogle retired FAQ rich results for all sites on 2026-05-07. FAQPage is not a\nGoogle rich-result or generative-AI optimization path, and it earns no SEO or\nAI-readiness credit. Only emit it when a visible FAQ genuinely helps readers,\nwith at least one valid `Question` and matching visible answer. Do not pad an\nanswer to a target length or add an FAQ solely for markup.\n\nDo not substitute QAPage. Google supports QAPage for a page focused on one\nquestion where users can submit answers. Editorial FAQs, support FAQs, and blog\nQ&A sections do not meet that model.\n\n### Step 7: Generate VideoObject (if videos present)\n\nFor each YouTube video embedded in the post, generate a VideoObject schema:\n\n```json\n{\n  \"@type\": \"VideoObject\",\n  \"@id\": \"{siteUrl}\u002Fblog\u002F{slug}#video-{index}\",\n  \"name\": \"Video title\",\n  \"description\": \"Video description excerpt (first 200 chars)\",\n  \"thumbnailUrl\": \"https:\u002F\u002Fimg.youtube.com\u002Fvi\u002F{videoId}\u002Fhqdefault.jpg\",\n  \"uploadDate\": \"{ISO 8601 date}\",\n  \"contentUrl\": \"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v={videoId}\",\n  \"embedUrl\": \"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002F{videoId}\",\n  \"duration\": \"PT{M}M{S}S\",\n  \"interactionStatistic\": {\n    \"@type\": \"InteractionCounter\",\n    \"interactionType\": { \"@type\": \"WatchAction\" },\n    \"userInteractionCount\": {viewCount}\n  }\n}\n```\n\nAdd each VideoObject to the @graph array. Use `#video-1`, `#video-2` etc. for\nthe @id fragment. Extract video metadata from the embed's noscript fallback or\nfrom YouTube Data API if available via `blog-google`.\n\n### Step 7.5: Generate ImageObject\n\nCover image schema for the post's primary image:\n\n```json\n{\n  \"@type\": \"ImageObject\",\n  \"@id\": \"{siteUrl}\u002Fblog\u002F{slug}#primaryimage\",\n  \"url\": \"https:\u002F\u002Fcdn.pixabay.com\u002Fphoto\u002F...\u002Fimage.jpg\",\n  \"width\": 1200,\n  \"height\": 630,\n  \"caption\": \"Descriptive caption matching alt text\"\n}\n```\n\nImage requirements:\n- URL must be crawlable and publicly accessible\n- Width and height should reflect actual image dimensions\n- Caption should match or closely align with the image alt text\n- Preferred dimensions: 1200x630 (OG-compatible) or 1920x1080\n\n### Step 8: Validate & Warn\n\nCheck per-surface support before recommending schema types:\n\n| Type | Google Search status | Valid entity\u002Fcontext use |\n|------|----------------------|--------------------------|\n| HowTo | No current Google rich-result experience | Valid schema.org type for genuine how-to content |\n| Dataset | Used by Dataset Search, not general Google Search rich results | Valid only for an actual dataset |\n| QAPage | Supported for one question with user-submitted answers | Do not use for editorial FAQ content |\n| Course | Course list remains distinct from the retired Course Info experience | Use only when the current Course list documentation and visible content match |\n| ClaimReview, SpecialAnnouncement, Course Info, Estimated Salary, Learning Video, Vehicle Listing | Former Google Search experiences; support was retired | May remain schema.org-valid, but never recommend them for Google eligibility |\n| PracticeProblem | Removed from Google Search and its documentation | Do not recommend for Google eligibility |\n| Sitelinks Search Box | No dedicated Google Search visual element | Google generates sitelinks algorithmically |\n\n**Validation checks:**\n1. All @id references resolve to entities within the @graph\n2. dateModified is equal to or after datePublished\n3. headline is concise. Warn when it may truncate or becomes unclear\n4. description is concise, page-specific, and not duplicated across posts\n5. All URLs are absolute (not relative)\n6. Image dimensions are positive integers\n7. BreadcrumbList positions are sequential starting from 1\n8. If FAQPage is emitted, visible Q&A content exists and includes at least 1 valid `Question`\n\n**Generative AI note:** Structured data is not required for Google generative\nAI search, and there is no special AI schema. Prioritize accurate,\nvisible-content-consistent Article\u002FBlogPosting, Person, Organization, and\nBreadcrumbList entities. Add ImageObject or VideoObject when the assets exist.\nFAQPage remains optional reader-facing markup and adds no Google AI advantage.\n\n### Step 9: Output\n\nCombine all schemas into a single `\u003Cscript>` tag using the @graph pattern:\n\nSecurity requirement: build the JSON-LD with a real JSON encoder, never string\ninterpolation. Before embedding in HTML, make the JSON text script-safe by\nescaping closing script sequences and literal less-than characters, for example\nreplace `\u003C\u002F` with `\u003C\\\u002F` and `\u003C` with `\\u003c`. User-controlled fields such as\nheadline, description, author name, image URL, and breadcrumb labels must only\nenter the block as JSON-encoded values.\n\n```html\n\u003Cscript type=\"application\u002Fld+json\">\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@graph\": [\n    { \"@type\": \"BlogPosting\", ... },\n    { \"@type\": \"Person\", ... },\n    { \"@type\": \"Organization\", ... },\n    { \"@type\": \"BreadcrumbList\", ... },\n    { \"@type\": \"FAQPage\", ... },\n    { \"@type\": \"VideoObject\", ... },\n    { \"@type\": \"ImageObject\", ... }\n  ]\n}\n\u003C\u002Fscript>\n```\n\n**@graph pattern benefits:**\n- Single script tag instead of multiple - cleaner HTML\n- Entity linking via stable @id references (e.g., author references Person by @id)\n- Google and AI systems parse @graph arrays correctly\n- Easier to maintain and update as a single block\n\n**Output options:**\n- **Embedded HTML** - Ready to paste into `\u003Chead>` or before `\u003C\u002Fbody>`\n- **Standalone JSON** - For CMS schema fields or API injection\n- **MDX component** - If the project uses MDX, wrap in a component\n\nSave the generated schema to the blog post file or to a separate schema file\nas the user prefers.\n\nGoogle can process JSON-LD generated by JavaScript when it is present in the\nrendered DOM. Server-rendered markup is still more portable for non-Google\ncrawlers, but source-only JSON-LD is not a Google requirement. For dynamic\nmarkup, validate the rendered URL, confirm the values match visible content,\nand avoid delayed or failed client requests that leave the rendered DOM empty.\n","# Blog Schema: JSON-LD Structured Data Generation\n\nGenerates complete, validated JSON-LD schema markup for blog posts using the\n@graph pattern. Combines multiple schema types into a single script tag with\nstable @id references for entity linking.\n\n## Workflow\n\n### Step 1: Read Content\n\nRead the blog post and extract all schema-relevant data:\n- **Title** (headline)\n- **Author** (name, job title, social links, credentials)\n- **Dates** (datePublished, dateModified \u002F lastUpdated)\n- **Description** (meta description)\n- **FAQ section** (question and answer pairs)\n- **Images** (cover image URL, dimensions, alt text; inline images)\n- **Organization info** (site name, URL, logo)\n- **Word count** (approximate from content length)\n- **Tags\u002Fcategories** (for BreadcrumbList category)\n- **Slug** (from filename or frontmatter)\n\n### Step 2: Generate BlogPosting Schema\n\nComplete BlogPosting with recommended properties when applicable:\n\n```json\n{\n  \"@type\": \"BlogPosting\",\n  \"@id\": \"{siteUrl}\u002Fblog\u002F{slug}#article\",\n  \"headline\": \"Concise post title\",\n  \"description\": \"Concise page-specific meta description\",\n  \"datePublished\": \"YYYY-MM-DD\",\n  \"dateModified\": \"YYYY-MM-DD\",\n  \"author\": { \"@id\": \"{siteUrl}\u002Fauthor\u002F{author-slug}#person\" },\n  \"publisher\": { \"@id\": \"{siteUrl}#organization\" },\n  \"image\": { \"@id\": \"{siteUrl}\u002Fblog\u002F{slug}#primaryimage\" },\n  \"mainEntityOfPage\": {\n    \"@type\": \"WebPage\",\n    \"@id\": \"{siteUrl}\u002Fblog\u002F{slug}\"\n  },\n  \"wordCount\": 2400,\n  \"articleBody\": \"First 200 characters of content as excerpt...\"\n}\n```\n\nGoogle's Article structured data docs do not define required Article\nproperties. Include `headline`, `datePublished`, `author`, `publisher`, and\n`image` when applicable, validate with the Rich Results Test, and treat missing\nfields as warnings unless the target surface requires them. Recommended\nproperties: description, dateModified, mainEntityOfPage, wordCount, articleBody\n(excerpt).\n\n### Step 3: Generate Person Schema\n\nAuthor schema with stable @id for cross-referencing:\n\n```json\n{\n  \"@type\": \"Person\",\n  \"@id\": \"{siteUrl}\u002Fauthor\u002F{author-slug}#person\",\n  \"name\": \"Author Name\",\n  \"jobTitle\": \"Role or Title\",\n  \"url\": \"{siteUrl}\u002Fauthor\u002F{author-slug}\",\n  \"sameAs\": [\n    \"https:\u002F\u002Ftwitter.com\u002Fhandle\",\n    \"https:\u002F\u002Flinkedin.com\u002Fin\u002Fhandle\",\n    \"https:\u002F\u002Fgithub.com\u002Fhandle\"\n  ]\n}\n```\n\nOptional properties (include when available):\n- `alumniOf` - Educational institution (Organization type)\n- `worksFor` - Employer (reference to Organization @id if same entity)\n\n### Step 4: Generate Organization Schema\n\nBlog's parent organization entity:\n\n```json\n{\n  \"@type\": \"Organization\",\n  \"@id\": \"{siteUrl}#organization\",\n  \"name\": \"Organization Name\",\n  \"url\": \"{siteUrl}\",\n  \"logo\": {\n    \"@type\": \"ImageObject\",\n    \"url\": \"{siteUrl}\u002Flogo.png\",\n    \"width\": 600,\n    \"height\": 60\n  },\n  \"sameAs\": [\n    \"https:\u002F\u002Ftwitter.com\u002Forg\",\n    \"https:\u002F\u002Flinkedin.com\u002Fcompany\u002Forg\",\n    \"https:\u002F\u002Fgithub.com\u002Forg\"\n  ]\n}\n```\n\nLogo requirements: use a valid crawlable image URL and follow the active\nOrganization and Article documentation for the target surface. Do not invent\nhard logo dimensions unless the project or current docs require them.\n\n### Step 5: Generate BreadcrumbList\n\nNavigation breadcrumb schema showing content hierarchy:\n\n```json\n{\n  \"@type\": \"BreadcrumbList\",\n  \"@id\": \"{siteUrl}\u002Fblog\u002F{slug}#breadcrumb\",\n  \"itemListElement\": [\n    {\n      \"@type\": \"ListItem\",\n      \"position\": 1,\n      \"name\": \"Home\",\n      \"item\": \"{siteUrl}\"\n    },\n    {\n      \"@type\": \"ListItem\",\n      \"position\": 2,\n      \"name\": \"Category Name\",\n      \"item\": \"{siteUrl}\u002Fblog\u002Fcategory\u002F{category-slug}\"\n    },\n    {\n      \"@type\": \"ListItem\",\n      \"position\": 3,\n      \"name\": \"Post Title\",\n      \"item\": \"{siteUrl}\u002Fblog\u002F{slug}\"\n    }\n  ]\n}\n```\n\nIf no category is available, use \"Blog\" as the second breadcrumb item with\n`{siteUrl}\u002Fblog` as the URL.\n\n### Step 6: Generate FAQPage Entity Schema (Optional)\n\nExtract Q&A pairs from the blog post's FAQ section:\n\n```json\n{\n  \"@type\": \"FAQPage\",\n  \"@id\": \"{siteUrl}\u002Fblog\u002F{slug}#faq\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What is the question?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"The complete visible answer text.\"\n      }\n    }\n  ]\n}\n```\n\nGoogle retired FAQ rich results for all sites on 2026-05-07. FAQPage is not a\nGoogle rich-result or generative-AI optimization path, and it earns no SEO or\nAI-readiness credit. Only emit it when a visible FAQ genuinely helps readers,\nwith at least one valid `Question` and matching visible answer. Do not pad an\nanswer to a target length or add an FAQ solely for markup.\n\nDo not substitute QAPage. Google supports QAPage for a page focused on one\nquestion where users can submit answers. Editorial FAQs, support FAQs, and blog\nQ&A sections do not meet that model.\n\n### Step 7: Generate VideoObject (if videos present)\n\nFor each YouTube video embedded in the post, generate a VideoObject schema:\n\n```json\n{\n  \"@type\": \"VideoObject\",\n  \"@id\": \"{siteUrl}\u002Fblog\u002F{slug}#video-{index}\",\n  \"name\": \"Video title\",\n  \"description\": \"Video description excerpt (first 200 chars)\",\n  \"thumbnailUrl\": \"https:\u002F\u002Fimg.youtube.com\u002Fvi\u002F{videoId}\u002Fhqdefault.jpg\",\n  \"uploadDate\": \"{ISO 8601 date}\",\n  \"contentUrl\": \"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v={videoId}\",\n  \"embedUrl\": \"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002F{videoId}\",\n  \"duration\": \"PT{M}M{S}S\",\n  \"interactionStatistic\": {\n    \"@type\": \"InteractionCounter\",\n    \"interactionType\": { \"@type\": \"WatchAction\" },\n    \"userInteractionCount\": {viewCount}\n  }\n}\n```\n\nAdd each VideoObject to the @graph array. Use `#video-1`, `#video-2` etc. for\nthe @id fragment. Extract video metadata from the embed's noscript fallback or\nfrom YouTube Data API if available via `blog-google`.\n\n### Step 7.5: Generate ImageObject\n\nCover image schema for the post's primary image:\n\n```json\n{\n  \"@type\": \"ImageObject\",\n  \"@id\": \"{siteUrl}\u002Fblog\u002F{slug}#primaryimage\",\n  \"url\": \"https:\u002F\u002Fcdn.pixabay.com\u002Fphoto\u002F...\u002Fimage.jpg\",\n  \"width\": 1200,\n  \"height\": 630,\n  \"caption\": \"Descriptive caption matching alt text\"\n}\n```\n\nImage requirements:\n- URL must be crawlable and publicly accessible\n- Width and height should reflect actual image dimensions\n- Caption should match or closely align with the image alt text\n- Preferred dimensions: 1200x630 (OG-compatible) or 1920x1080\n\n### Step 8: Validate & Warn\n\nCheck per-surface support before recommending schema types:\n\n| Type | Google Search status | Valid entity\u002Fcontext use |\n|------|----------------------|--------------------------|\n| HowTo | No current Google rich-result experience | Valid schema.org type for genuine how-to content |\n| Dataset | Used by Dataset Search, not general Google Search rich results | Valid only for an actual dataset |\n| QAPage | Supported for one question with user-submitted answers | Do not use for editorial FAQ content |\n| Course | Course list remains distinct from the retired Course Info experience | Use only when the current Course list documentation and visible content match |\n| ClaimReview, SpecialAnnouncement, Course Info, Estimated Salary, Learning Video, Vehicle Listing | Former Google Search experiences; support was retired | May remain schema.org-valid, but never recommend them for Google eligibility |\n| PracticeProblem | Removed from Google Search and its documentation | Do not recommend for Google eligibility |\n| Sitelinks Search Box | No dedicated Google Search visual element | Google generates sitelinks algorithmically |\n\n**Validation checks:**\n1. All @id references resolve to entities within the @graph\n2. dateModified is equal to or after datePublished\n3. headline is concise. Warn when it may truncate or becomes unclear\n4. description is concise, page-specific, and not duplicated across posts\n5. All URLs are absolute (not relative)\n6. Image dimensions are positive integers\n7. BreadcrumbList positions are sequential starting from 1\n8. If FAQPage is emitted, visible Q&A content exists and includes at least 1 valid `Question`\n\n**Generative AI note:** Structured data is not required for Google generative\nAI search, and there is no special AI schema. Prioritize accurate,\nvisible-content-consistent Article\u002FBlogPosting, Person, Organization, and\nBreadcrumbList entities. Add ImageObject or VideoObject when the assets exist.\nFAQPage remains optional reader-facing markup and adds no Google AI advantage.\n\n### Step 9: Output\n\nCombine all schemas into a single `\u003Cscript>` tag using the @graph pattern:\n\nSecurity requirement: build the JSON-LD with a real JSON encoder, never string\ninterpolation. Before embedding in HTML, make the JSON text script-safe by\nescaping closing script sequences and literal less-than characters, for example\nreplace `\u003C\u002F` with `\u003C\\\u002F` and `\u003C` with `\\u003c`. User-controlled fields such as\nheadline, description, author name, image URL, and breadcrumb labels must only\nenter the block as JSON-encoded values.\n\n```html\n\u003Cscript type=\"application\u002Fld+json\">\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@graph\": [\n    { \"@type\": \"BlogPosting\", ... },\n    { \"@type\": \"Person\", ... },\n    { \"@type\": \"Organization\", ... },\n    { \"@type\": \"BreadcrumbList\", ... },\n    { \"@type\": \"FAQPage\", ... },\n    { \"@type\": \"VideoObject\", ... },\n    { \"@type\": \"ImageObject\", ... }\n  ]\n}\n\u003C\u002Fscript>\n```\n\n**@graph pattern benefits:**\n- Single script tag instead of multiple - cleaner HTML\n- Entity linking via stable @id references (e.g., author references Person by @id)\n- Google and AI systems parse @graph arrays correctly\n- Easier to maintain and update as a single block\n\n**Output options:**\n- **Embedded HTML** - Ready to paste into `\u003Chead>` or before `\u003C\u002Fbody>`\n- **Standalone JSON** - For CMS schema fields or API injection\n- **MDX component** - If the project uses MDX, wrap in a component\n\nSave the generated schema to the blog post file or to a separate schema file\nas the user prefers.\n\nGoogle can process JSON-LD generated by JavaScript when it is present in the\nrendered DOM. Server-rendered markup is still more portable for non-Google\ncrawlers, but source-only JSON-LD is not a Google requirement. For dynamic\nmarkup, validate the rendered URL, confirm the values match visible content,\nand avoid delayed or failed client requests that leave the rendered DOM empty.\n",{"name":5,"license":15,"description":24,"argument-hint":25,"user-invokable":26},"Generate complete JSON-LD schema markup for blog posts with Article\u002FBlogPosting, Person, Organization, BreadcrumbList, ImageObject, and optional FAQPage. Validates against Google requirements and warns about deprecated types. Use when user says \"schema\", \"blog schema\", \"json-ld\", \"structured data\", \"schema markup\", \"generate schema\".\n","\u003Cfile-path>",true,"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-imp-blog-schema",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":26},[37,40,43],{"tool":38,"command":39},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill blog-schema",{"tool":41,"command":42},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill blog-schema",{"tool":44,"command":45},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill blog-schema","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-imp-blog-schema\u002FSKILL.md",[],[49,56,64,71,78,85],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":60,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]