[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75M9R7CSN91GTGYGD03D12B":3,"skill-same:01M75M9R7CSN91GTGYGD03D12B":75},{"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":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M75M9R7CSN91GTGYGD03D12B","technical-seo-schema-engineer",null,"Design deterministic technical SEO and schema.org guidance for crawlable public pages. Use this skill when the user asks for title and meta description rules, canonical and hreflang tags, JSON-LD schema, NewsArticle, Article, TechArticle, BreadcrumbList, WebSite, Organization, Person, OpenGraph, Twitter cards, sitemap, news-sitemap, RSS, robots.txt, llms.txt, publisher logo, ImageObject, or metadata templates that must match visible content.","sergekostenchuk\u002Fseo-llm-skill-cluster","sergekostenchuk","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F65920873?v=4","01M75M7XRSVA03QA5MRRV3SB2G","mlllm.io","01M75M7XSTVXJCC0CCF1AVTER9",40,"MIT","https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-seo-schema-engineer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: technical-seo-schema-engineer\ndescription: Design deterministic technical SEO and schema.org guidance for crawlable public pages. Use this skill when the user asks for title and meta description rules, canonical and hreflang tags, JSON-LD schema, NewsArticle, Article, TechArticle, BreadcrumbList, WebSite, Organization, Person, OpenGraph, Twitter cards, sitemap, news-sitemap, RSS, robots.txt, llms.txt, publisher logo, ImageObject, or metadata templates that must match visible content.\n---\n\n# Technical SEO Schema Engineer\n\nUse this skill after `information-architecture-seo` has defined page roles and before live regression validation.\n\nRead [references\u002Fschema-patterns.md](references\u002Fschema-patterns.md) before designing full metadata or JSON-LD templates.\n\n## Owns\n\n- title and meta description rules;\n- canonical and hreflang tag templates;\n- JSON-LD schema patterns;\n- OpenGraph and Twitter card metadata;\n- sitemap, news-sitemap, RSS, robots.txt, and llms.txt output policy;\n- publisher logo and ImageObject fallback policy;\n- page-type metadata checklist.\n\n## Does Not Own\n\n- semantic core;\n- final URL architecture;\n- internal link graph;\n- live audit execution;\n- hidden content;\n- visual page layout.\n\n## Workflow\n\n1. Read `url-map.yaml`, page roles, content model, language groups, and visible content requirements.\n2. Select metadata and schema by page role.\n3. Define title\u002Fmeta fallbacks and length guidance.\n4. Define canonical and hreflang tags from URL map.\n5. Define JSON-LD nodes that match visible page content.\n6. Define OG\u002FTwitter image policy: media, video poster, publisher card, or fallback OG card.\n7. Define sitemap\u002FRSS\u002Frobots\u002Fllms.txt inclusion rules.\n8. Produce schema\u002Fhead guidance using [assets\u002Fjsonld-templates.md](assets\u002Fjsonld-templates.md) and [assets\u002Fhead-metadata.template.html](assets\u002Fhead-metadata.template.html).\n9. Hand off validation to `seo-regression-validator`.\n\n## Non-Negotiables\n\n- Schema must match visible content.\n- Do not add FAQPage unless the FAQ block is visible to users.\n- Do not add review, rating, price, author, publisher, date, image, or source claims that are absent or unsupported.\n- Do not use JSON-LD to hide extra keywords, extra entities, or alternate facts.\n- NewsArticle.image must resolve to media, poster, or a stable fallback ImageObject.\n- Canonical and hreflang must follow URL architecture.\n- Current Google\u002Fschema.org\u002Fcrawler rules require primary-source verification before production changes.\n\n## Safety And Privacy Boundaries\n\n- Do not expose admin, API, private dashboards, raw analytics, raw IP logs, secret files, tokens, unpublished drafts, or staging URLs in metadata, schema, sitemaps, RSS, robots, or llms.txt.\n- Do not weaken authentication, access control, CSP, CORS, cookies, rate limits, or private-content boundaries for crawlability.\n- Do not place private instructions or internal planning notes in public LLM-facing files.\n- Do not treat robots.txt as a secrecy mechanism for sensitive content.\n- Security, privacy, legal accuracy, accessibility, and visible user comprehension override SEO or LLM visibility tactics.\n\n## Validation\n\nBefore marking work complete:\n\n- every page type has title, description, canonical, OG, Twitter, and schema guidance;\n- every schema type has required visible-content fields;\n- every news\u002Farticle page has image fallback policy;\n- every hreflang group is based on URL map equivalents;\n- sitemap and news-sitemap rules include only intended public canonical URLs;\n- robots and llms.txt rules avoid private\u002Fadmin\u002FAPI surfaces;\n- hidden schema and duplicate canonical patterns are rejected.\n\nValidate skill edits with:\n\n```bash\npython3 \u003Ccodex-skills-dir>\u002Fsenior-skill-architect\u002Fscripts\u002Flint_production_skill.py .\u002Fskills\u002Ftechnical-seo-schema-engineer\npython3 .\u002Fplans\u002Fseo-llm-skill-cluster\u002Fscripts\u002Flint_skill_cluster.py .\n```\n\nForward tests live in [evals.json](evals.json).\n\n## Output Shape\n\nReturn:\n\n1. Page-type metadata matrix.\n2. Schema nodes and required visible fields.\n3. Canonical\u002Fhreflang rules.\n4. Sitemap\u002FRSS\u002Frobots\u002Fllms.txt inclusion policy.\n5. Validation checklist and handoff to regression validator.\n","# Technical SEO Schema Engineer\n\nUse this skill after `information-architecture-seo` has defined page roles and before live regression validation.\n\nRead [references\u002Fschema-patterns.md](references\u002Fschema-patterns.md) before designing full metadata or JSON-LD templates.\n\n## Owns\n\n- title and meta description rules;\n- canonical and hreflang tag templates;\n- JSON-LD schema patterns;\n- OpenGraph and Twitter card metadata;\n- sitemap, news-sitemap, RSS, robots.txt, and llms.txt output policy;\n- publisher logo and ImageObject fallback policy;\n- page-type metadata checklist.\n\n## Does Not Own\n\n- semantic core;\n- final URL architecture;\n- internal link graph;\n- live audit execution;\n- hidden content;\n- visual page layout.\n\n## Workflow\n\n1. Read `url-map.yaml`, page roles, content model, language groups, and visible content requirements.\n2. Select metadata and schema by page role.\n3. Define title\u002Fmeta fallbacks and length guidance.\n4. Define canonical and hreflang tags from URL map.\n5. Define JSON-LD nodes that match visible page content.\n6. Define OG\u002FTwitter image policy: media, video poster, publisher card, or fallback OG card.\n7. Define sitemap\u002FRSS\u002Frobots\u002Fllms.txt inclusion rules.\n8. Produce schema\u002Fhead guidance using [assets\u002Fjsonld-templates.md](assets\u002Fjsonld-templates.md) and [assets\u002Fhead-metadata.template.html](assets\u002Fhead-metadata.template.html).\n9. Hand off validation to `seo-regression-validator`.\n\n## Non-Negotiables\n\n- Schema must match visible content.\n- Do not add FAQPage unless the FAQ block is visible to users.\n- Do not add review, rating, price, author, publisher, date, image, or source claims that are absent or unsupported.\n- Do not use JSON-LD to hide extra keywords, extra entities, or alternate facts.\n- NewsArticle.image must resolve to media, poster, or a stable fallback ImageObject.\n- Canonical and hreflang must follow URL architecture.\n- Current Google\u002Fschema.org\u002Fcrawler rules require primary-source verification before production changes.\n\n## Safety And Privacy Boundaries\n\n- Do not expose admin, API, private dashboards, raw analytics, raw IP logs, secret files, tokens, unpublished drafts, or staging URLs in metadata, schema, sitemaps, RSS, robots, or llms.txt.\n- Do not weaken authentication, access control, CSP, CORS, cookies, rate limits, or private-content boundaries for crawlability.\n- Do not place private instructions or internal planning notes in public LLM-facing files.\n- Do not treat robots.txt as a secrecy mechanism for sensitive content.\n- Security, privacy, legal accuracy, accessibility, and visible user comprehension override SEO or LLM visibility tactics.\n\n## Validation\n\nBefore marking work complete:\n\n- every page type has title, description, canonical, OG, Twitter, and schema guidance;\n- every schema type has required visible-content fields;\n- every news\u002Farticle page has image fallback policy;\n- every hreflang group is based on URL map equivalents;\n- sitemap and news-sitemap rules include only intended public canonical URLs;\n- robots and llms.txt rules avoid private\u002Fadmin\u002FAPI surfaces;\n- hidden schema and duplicate canonical patterns are rejected.\n\nValidate skill edits with:\n\n```bash\npython3 \u003Ccodex-skills-dir>\u002Fsenior-skill-architect\u002Fscripts\u002Flint_production_skill.py .\u002Fskills\u002Ftechnical-seo-schema-engineer\npython3 .\u002Fplans\u002Fseo-llm-skill-cluster\u002Fscripts\u002Flint_skill_cluster.py .\n```\n\nForward tests live in [evals.json](evals.json).\n\n## Output Shape\n\nReturn:\n\n1. Page-type metadata matrix.\n2. Schema nodes and required visible fields.\n3. Canonical\u002Fhreflang rules.\n4. Sitemap\u002FRSS\u002Frobots\u002Fllms.txt inclusion policy.\n5. Validation checklist and handoff to regression validator.\n",{"name":5,"description":7},"main","5873665900e03e9422ee9accc16671b7477294ed","skills\u002Ftechnical-seo-schema-engineer",4,"https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster","https:\u002F\u002Fgithub.com\u002Fsergekostenchuk","https:\u002F\u002Fmlllm.io\u002F","I build AI news infrastructure, Telegram automation, local knowledge workflows, and agentic developer tools","2026-06-12 04:14:05",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add sergekostenchuk\u002Fseo-llm-skill-cluster --skill technical-seo-schema-engineer",{"tool":39,"command":40},"bunx","bunx skills add sergekostenchuk\u002Fseo-llm-skill-cluster --skill technical-seo-schema-engineer",{"tool":42,"command":43},"pnpm","pnpm dlx skills add sergekostenchuk\u002Fseo-llm-skill-cluster --skill technical-seo-schema-engineer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-seo-schema-engineer\u002FSKILL.md",true,[47,53,59,63,67,71],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",419,"https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-seo-schema-engineer\u002Fagents\u002Fopenai.yaml",{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"assets\u002Fhead-metadata.template.html","ASSET","资产文件",1556,"https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-seo-schema-engineer\u002Fassets\u002Fhead-metadata.template.html",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"assets\u002Fjsonld-templates.md",2968,"https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-seo-schema-engineer\u002Fassets\u002Fjsonld-templates.md",{"path":64,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":65,"sourceHtmlUrl":66},"evals.json",1968,"https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-seo-schema-engineer\u002Fevals.json",{"path":68,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fschema-patterns.md",3193,"https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-seo-schema-engineer\u002Freferences\u002Fschema-patterns.md",{"path":72,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":73,"sourceHtmlUrl":74},"validation-report.md",1383,"https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-seo-schema-engineer\u002Fvalidation-report.md",[76,83,90,97,104,111],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M75M9X9H71PWGC23BT617VC6","ux-journey-architect","Map user journeys, onboarding paths, entry points, first actions, trust points, accessibility risks, and SEO\u002FLLM handoffs for public websites without redesigning the visual system. Use this skill when the user asks how new readers, returning users, project reviewers, community members, buyers, or AI agents should move through a site and what each page must make clear before layout implementation.","https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Fux-journey-architect\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M75M9JJK6G0NSQJ6R8AP1RBE","site-growth-orchestrator","Coordinate SEO, LLM-readable site architecture, UX, content, monitoring, security, and external authority work as a task-plan-driven sequence. Use this skill when the user asks to plan, execute, validate, or route multi-skill website growth work; asks what to do next across semantic core, URL structure, internal linking, schema, llms.txt, UX journeys, analytics, citation monitoring, or white-hat link placement; or wants a central architect that preserves evidence, alarms, handoffs, and tests.","https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Fsite-growth-orchestrator\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M75M9DPZC07XSKYHJHT2STYR","server-log-crawler-analyst","Analyze credential-free public website monitoring evidence from server access logs, HTTP fetches, robots\u002Fllms\u002Fsitemap checks, and exported summaries while protecting raw IP and private query data. Use this skill when the user asks whether crawlers or AI bots reached a site, whether public SEO\u002FLLM discovery files respond, or how to separate observed facts from unknown Search Console, rank, analytics, or citation claims.","https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Fserver-log-crawler-analyst\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M75M99BEBPDRHRT7QD489W7R","seo-regression-validator","Validate SEO and LLM-readability claims against live HTML, local fixtures, and generated artifacts. Use this skill when the user asks to prove whether title, meta description, canonical, hreflang, JSON-LD, NewsArticle.image, OpenGraph, Twitter cards, RSS autodiscovery, robots.txt, llms.txt, sitemap, news-sitemap, crawler access, or performance evidence is actually present, and when subjective audits must become timestamped pass\u002Ffail reports.","https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Fseo-regression-validator\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M75M941RZED3RG5154ZSNZYN","semantic-core-architect","Build evidence-labeled semantic cores for SEO, LLM-readable architecture, and site information design. Use this skill when the user asks for semantic core, query clusters, search intents, audience segments, entity\u002Ftopic maps, language or locale priorities, competitor\u002Fsource evidence, pillar-topic planning, or a structured handoff before URL architecture and internal linking. It must mark unknown search volume, difficulty, and ranking data as unknown instead of inventing metrics.","https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Fsemantic-core-architect\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M75M8YMSHVKX5KSSSJ29M0TT","llm-friendly-site-architect","Design human-visible, machine-readable website layers for AI assistants, RAG, and agentic search. Use this skill when the user asks for llms.txt, LLM discovery plans, visible TLDR or direct-answer blocks, source trails, entity pages, markdown alternates, AI crawler policy, topic-to-URL maps, assistant-readable public content, or LLM-friendly architecture that must preserve canonical SEO strategy without hidden bot-only facts or duplicate story bodies.","https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Fllm-friendly-site-architect\u002FSKILL.md",[],[]]