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/topic maps, language or locale priorities, competitor/source 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.
- License 许可
- MIT
- 最近更新
- 2026-06-12
- Stars
- ★ 40
- Forks
- 4
01 前言 Front Matter
- name
- semantic-core-architect
- description
- 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/topic maps, language or locale priorities, competitor/source 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.
02 资源文件 6
- 参考文档agents/openai.yaml410 B
- 资产文件assets/entity-topic-map.template.yaml839 B
- 资产文件assets/semantic-core.template.yaml1.3 KB
- 参考文档evals.json2.1 KB
- 参考文档references/semantic-core-rubric.md3.3 KB
- 参考文档validation-report.md1.3 KB
03 SKILL.md 正文
Semantic Core Architect
Use this skill before URL architecture, internal linking, schema, content planning, or LLM-friendly page design. It turns a site goal into reusable semantic artifacts.
Read references/semantic-core-rubric.md before producing a full semantic core.
Owns
- query clusters;
- user/search intents;
- audience and job-to-be-done mapping;
- entity and topic mapping;
- language and locale priority;
- evidence labels and data gaps;
- handoff to information architecture.
Does Not Own
- final URL/canonical policy;
- internal link graph;
- schema implementation;
- page copywriting;
- rank guarantees;
- external link placement.
Workflow
- Capture the goal, audience, markets, languages, content model, constraints, and forbidden areas.
- Separate observed facts, user-provided facts, inferred assumptions, and unknowns.
- Build query clusters by intent, not by keyword volume alone.
- Map entities and topics to likely canonical page candidates without deciding final URLs.
- Assign priority from strategic value, page feasibility, audience fit, and evidence strength.
- Mark volume, difficulty, competitive strength, and rank opportunity as
unknownunless verified from an approved source. - Produce
semantic-core.yamlandentity-topic-map.yamlusing the templates in assets/. - Hand off to
information-architecture-seowith gaps and assumptions explicit.
Evidence Rules
- Search volume, difficulty, traffic, ranking, and assistant citation claims require current evidence.
- If keyword tools, Search Console, rank trackers, logs, or assistant-monitoring data are unavailable, use
unknown. - Current facts about search engines, AI crawlers, rich results, or platforms must follow the cluster freshness policy.
- Do not use competitor pages as proof of volume unless they come with a measured source.
Priority Model
Use 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.
Priority is not ranking probability.
Required Outputs
Create or update:
semantic-core.yaml, based on assets/semantic-core.template.yaml;entity-topic-map.yaml, based on assets/entity-topic-map.template.yaml;- a gap list for unverified data and needed research.
Each cluster must include intent, audience, languages, entities, queries, evidence, assumptions, unknown metrics, and downstream notes.
Validation
Before marking work complete:
- check every cluster has intent, audience, language, priority, and at least one query or topic seed;
- check every metric field is either evidence-backed or
unknown; - check entity names have stable ids;
- check no URL/canonical decision is made as final;
- run the cluster linter after skill edits.
Validate skill edits with:
python3 <codex-skills-dir>/senior-skill-architect/scripts/lint_production_skill.py ./skills/semantic-core-architect
python3 ./plans/seo-llm-skill-cluster/scripts/lint_skill_cluster.py .
Forward tests for this skill live in evals.json.
Output Shape
Return:
- Semantic core summary.
- Top clusters by priority.
- Entity/topic map summary.
- Unknown metrics and evidence gaps.
- Handoff notes for information architecture.
04 同仓库更多 Skills
ux-journey-architect
Map user journeys, onboarding paths, entry points, first actions, trust points, accessibility risks, and SEO/LLM 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.
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.
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.
server-log-crawler-analyst
Analyze credential-free public website monitoring evidence from server access logs, HTTP fetches, robots/llms/sitemap 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/LLM discovery files respond, or how to separate observed facts from unknown Search Console, rank, analytics, or citation claims.
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/fail reports.
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.