[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75M941RZED3RG5154ZSNZYN":3,"skill-same:01M75M941RZED3RG5154ZSNZYN":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},"01M75M941RZED3RG5154ZSNZYN","semantic-core-architect",null,"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.","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\u002Fsemantic-core-architect\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: semantic-core-architect\ndescription: 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.\n---\n\n# Semantic Core Architect\n\nUse this skill before URL architecture, internal linking, schema, content planning, or LLM-friendly page design. It turns a site goal into reusable semantic artifacts.\n\nRead [references\u002Fsemantic-core-rubric.md](references\u002Fsemantic-core-rubric.md) before producing a full semantic core.\n\n## Owns\n\n- query clusters;\n- user\u002Fsearch intents;\n- audience and job-to-be-done mapping;\n- entity and topic mapping;\n- language and locale priority;\n- evidence labels and data gaps;\n- handoff to information architecture.\n\n## Does Not Own\n\n- final URL\u002Fcanonical policy;\n- internal link graph;\n- schema implementation;\n- page copywriting;\n- rank guarantees;\n- external link placement.\n\n## Workflow\n\n1. Capture the goal, audience, markets, languages, content model, constraints, and forbidden areas.\n2. Separate observed facts, user-provided facts, inferred assumptions, and unknowns.\n3. Build query clusters by intent, not by keyword volume alone.\n4. Map entities and topics to likely canonical page candidates without deciding final URLs.\n5. Assign priority from strategic value, page feasibility, audience fit, and evidence strength.\n6. Mark volume, difficulty, competitive strength, and rank opportunity as `unknown` unless verified from an approved source.\n7. Produce `semantic-core.yaml` and `entity-topic-map.yaml` using the templates in [assets\u002F](assets\u002F).\n8. Hand off to `information-architecture-seo` with gaps and assumptions explicit.\n\n## Evidence Rules\n\n- Search volume, difficulty, traffic, ranking, and assistant citation claims require current evidence.\n- If keyword tools, Search Console, rank trackers, logs, or assistant-monitoring data are unavailable, use `unknown`.\n- Current facts about search engines, AI crawlers, rich results, or platforms must follow the cluster freshness policy.\n- Do not use competitor pages as proof of volume unless they come with a measured source.\n\n## Priority Model\n\nUse `P0` only when a cluster is both central to the site's identity and needed by downstream architecture. Use `P1` for important supporting clusters. Use `P2` for useful expansion. Use `P3` for backlog or speculative ideas.\n\nPriority is not ranking probability.\n\n## Required Outputs\n\nCreate or update:\n\n- `semantic-core.yaml`, based on [assets\u002Fsemantic-core.template.yaml](assets\u002Fsemantic-core.template.yaml);\n- `entity-topic-map.yaml`, based on [assets\u002Fentity-topic-map.template.yaml](assets\u002Fentity-topic-map.template.yaml);\n- a gap list for unverified data and needed research.\n\nEach cluster must include intent, audience, languages, entities, queries, evidence, assumptions, unknown metrics, and downstream notes.\n\n## Validation\n\nBefore marking work complete:\n\n- check every cluster has intent, audience, language, priority, and at least one query or topic seed;\n- check every metric field is either evidence-backed or `unknown`;\n- check entity names have stable ids;\n- check no URL\u002Fcanonical decision is made as final;\n- run the cluster linter after skill edits.\n\nValidate skill edits with:\n\n```bash\npython3 \u003Ccodex-skills-dir>\u002Fsenior-skill-architect\u002Fscripts\u002Flint_production_skill.py .\u002Fskills\u002Fsemantic-core-architect\npython3 .\u002Fplans\u002Fseo-llm-skill-cluster\u002Fscripts\u002Flint_skill_cluster.py .\n```\n\nForward tests for this skill live in [evals.json](evals.json).\n\n## Output Shape\n\nReturn:\n\n1. Semantic core summary.\n2. Top clusters by priority.\n3. Entity\u002Ftopic map summary.\n4. Unknown metrics and evidence gaps.\n5. Handoff notes for information architecture.\n","# Semantic Core Architect\n\nUse this skill before URL architecture, internal linking, schema, content planning, or LLM-friendly page design. It turns a site goal into reusable semantic artifacts.\n\nRead [references\u002Fsemantic-core-rubric.md](references\u002Fsemantic-core-rubric.md) before producing a full semantic core.\n\n## Owns\n\n- query clusters;\n- user\u002Fsearch intents;\n- audience and job-to-be-done mapping;\n- entity and topic mapping;\n- language and locale priority;\n- evidence labels and data gaps;\n- handoff to information architecture.\n\n## Does Not Own\n\n- final URL\u002Fcanonical policy;\n- internal link graph;\n- schema implementation;\n- page copywriting;\n- rank guarantees;\n- external link placement.\n\n## Workflow\n\n1. Capture the goal, audience, markets, languages, content model, constraints, and forbidden areas.\n2. Separate observed facts, user-provided facts, inferred assumptions, and unknowns.\n3. Build query clusters by intent, not by keyword volume alone.\n4. Map entities and topics to likely canonical page candidates without deciding final URLs.\n5. Assign priority from strategic value, page feasibility, audience fit, and evidence strength.\n6. Mark volume, difficulty, competitive strength, and rank opportunity as `unknown` unless verified from an approved source.\n7. Produce `semantic-core.yaml` and `entity-topic-map.yaml` using the templates in [assets\u002F](assets\u002F).\n8. Hand off to `information-architecture-seo` with gaps and assumptions explicit.\n\n## Evidence Rules\n\n- Search volume, difficulty, traffic, ranking, and assistant citation claims require current evidence.\n- If keyword tools, Search Console, rank trackers, logs, or assistant-monitoring data are unavailable, use `unknown`.\n- Current facts about search engines, AI crawlers, rich results, or platforms must follow the cluster freshness policy.\n- Do not use competitor pages as proof of volume unless they come with a measured source.\n\n## Priority Model\n\nUse `P0` only when a cluster is both central to the site's identity and needed by downstream architecture. Use `P1` for important supporting clusters. Use `P2` for useful expansion. Use `P3` for backlog or speculative ideas.\n\nPriority is not ranking probability.\n\n## Required Outputs\n\nCreate or update:\n\n- `semantic-core.yaml`, based on [assets\u002Fsemantic-core.template.yaml](assets\u002Fsemantic-core.template.yaml);\n- `entity-topic-map.yaml`, based on [assets\u002Fentity-topic-map.template.yaml](assets\u002Fentity-topic-map.template.yaml);\n- a gap list for unverified data and needed research.\n\nEach cluster must include intent, audience, languages, entities, queries, evidence, assumptions, unknown metrics, and downstream notes.\n\n## Validation\n\nBefore marking work complete:\n\n- check every cluster has intent, audience, language, priority, and at least one query or topic seed;\n- check every metric field is either evidence-backed or `unknown`;\n- check entity names have stable ids;\n- check no URL\u002Fcanonical decision is made as final;\n- run the cluster linter after skill edits.\n\nValidate skill edits with:\n\n```bash\npython3 \u003Ccodex-skills-dir>\u002Fsenior-skill-architect\u002Fscripts\u002Flint_production_skill.py .\u002Fskills\u002Fsemantic-core-architect\npython3 .\u002Fplans\u002Fseo-llm-skill-cluster\u002Fscripts\u002Flint_skill_cluster.py .\n```\n\nForward tests for this skill live in [evals.json](evals.json).\n\n## Output Shape\n\nReturn:\n\n1. Semantic core summary.\n2. Top clusters by priority.\n3. Entity\u002Ftopic map summary.\n4. Unknown metrics and evidence gaps.\n5. Handoff notes for information architecture.\n",{"name":5,"description":7},"main","5873665900e03e9422ee9accc16671b7477294ed","skills\u002Fsemantic-core-architect",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 semantic-core-architect",{"tool":39,"command":40},"bunx","bunx skills add sergekostenchuk\u002Fseo-llm-skill-cluster --skill semantic-core-architect",{"tool":42,"command":43},"pnpm","pnpm dlx skills add sergekostenchuk\u002Fseo-llm-skill-cluster --skill semantic-core-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Fsemantic-core-architect\u002FSKILL.md",true,[47,53,59,63,67,71],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",410,"https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Fsemantic-core-architect\u002Fagents\u002Fopenai.yaml",{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"assets\u002Fentity-topic-map.template.yaml","ASSET","资产文件",839,"https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Fsemantic-core-architect\u002Fassets\u002Fentity-topic-map.template.yaml",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"assets\u002Fsemantic-core.template.yaml",1320,"https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Fsemantic-core-architect\u002Fassets\u002Fsemantic-core.template.yaml",{"path":64,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":65,"sourceHtmlUrl":66},"evals.json",2146,"https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Fsemantic-core-architect\u002Fevals.json",{"path":68,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fsemantic-core-rubric.md",3389,"https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Fsemantic-core-architect\u002Freferences\u002Fsemantic-core-rubric.md",{"path":72,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":73,"sourceHtmlUrl":74},"validation-report.md",1360,"https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Fsemantic-core-architect\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},"01M75M9R7CSN91GTGYGD03D12B","technical-seo-schema-engineer","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.","https:\u002F\u002Fgithub.com\u002Fsergekostenchuk\u002Fseo-llm-skill-cluster\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-seo-schema-engineer\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},"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":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},"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":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},"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":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",[],[]]