Content Semantics Stinger
You are equipping content-semantics-wasp-drone, part of the Website
Auditor by Legion Code Inc. plugin. Full scope and acceptance criteria:
prd-010-content-semantics.
Purpose
Produce the run's 03-seo/content-semantics.md sub-audit: a quantified,
formula-shown reading-level estimate for every crawled page, and a
separately-labeled [subjective] ICP-relevancy score per page against the
ICP icp-positioning-stinger already determined. These are two
independent findings about the same page and must never be merged into one
number or one section; a page can be effortlessly readable and completely
off-ICP, or dense and jargon-heavy yet exactly on-ICP for a technical
buyer persona.
When to use
- Wave W5 of every audit run, reading
site-data/ and 02-positioning/
(both read-only)
- Distinguishing a genuinely low-reading-level page from one that is
merely off-ICP; the two are commonly conflated and this Stinger exists
specifically to keep them apart
- Judging whether a page clears Google's stated "non-commodity content"
bar as one input to the ICP-relevancy score
When not to use
- Technical structure, metadata, indexation, or internal-link-graph
analysis of the same pages. That is
technical-seo-stinger's and
internal-linking-stinger's scope respectively.
- Determining the site's niche, ICP, or conversion-action taxonomy from
scratch. That is
icp-positioning-stinger's scope; this Stinger applies
its output, never re-derives it.
- Crawling or fetching a page not already in
site-data/. This Stinger
never crawls; that is site-crawler-wasp-drone's job.
Procedure
- Run
references/scripts/reading-level.py against site-data/*.md to
produce the quantified reading-level estimate (word/sentence/syllable
counts, Flesch Reading Ease, Flesch-Kincaid Grade) per page, stating the
formula-choice grounding caveat explicitly. See
guides/01-reading-level-scoring.md.
- Read
02-positioning/'s ICP and conversion-action taxonomy (do not
re-derive it) and apply references/templates/icp-relevancy-scoring- rubric-template.md to score every page's [subjective] ICP-relevancy,
including the non-commodity-content check. See
guides/02-icp-relevancy-scoring.md.
- Observe and report the supporting content-structure signals (lead-
paragraph length against both cited ranges, heading structure, schema
presence) that inform the ICP-relevancy judgment, each with its
sourcing caveat. See
guides/03-content-structure-signals.md.
- Assemble
03-seo/content-semantics.md from
references/templates/content-semantics-report-template.md, keeping
the quantified and subjective sections clearly separate, fill the
findings-register rows, and log any rejected/reframed candidate. See
guides/04-report-assembly.md.
References map
references/research/distilled-content-semantics.md, load when a claim
needs verification, or to check section 8's gap list before assuming
this archive covers something it does not (readability formulas,
ICP-scoring methodology).
- Source research archive (not shipped with the plugin): the shipped distillation summarizes it; do not require it.
its primary source.
references/scripts/reading-level.py, run once per audit against
site-data/*.md; do not hand-count words, sentences, or syllables. Its
docstring carries the formula-grounding caveat in full.
references/templates/content-semantics-report-template.md, load when
assembling 03-seo/content-semantics.md.
references/templates/icp-relevancy-scoring-rubric-template.md, load
when scoring the [subjective] ICP-relevancy checkpoint; bridges the
build plan's universal zero-to-six scale to this specific checkpoint.
guides/01-reading-level-scoring.md through
guides/04-report-assembly.md, load in order for a full pass; each maps
to one section of the report template.
Related drones and stingers
- icp-positioning-stinger - owns the ICP,
niche, and conversion-action taxonomy this Stinger applies to score
page-level relevancy. Read its output, never duplicate its taxonomy.
- internal-linking-stinger - sibling
wave-W5 Stinger over the same
site-data/, link-structure analysis
rather than copy quality; runs concurrently, no write contention.
- technical-seo-stinger - owns the technical
structure, metadata, and indexation sub-audit for the same page set;
content quality (this Stinger) and technical structure are scored
separately per the build plan's weight table.
- content-semantics-wasp-drone -
this Stinger's paired Drone.
Critical Directive
- You must read all files and context contained within your skill.
- In the event your core knowledge does not provide sufficient guidance you must make every attempt to search the internet, related knowledge base documentation files, and other available resources to supplement your knowledge prior to proceeding with your task.
- Additional related skills can be found here:
Ship Gate
Ship Gate removed: research-only stinger, produces no committable code.
This Stinger's output is a findings report (03-seo/content-semantics.md)
written to the target audit workspace outside this repository; it never
proposes a diff or a commit to this plugin's own tracked source, so the
security-stinger / quality-stinger / github-repo-health-stinger close-out
sequence does not apply.
1---2name: content-semantics-stinger-23description: "Quantified reading-level estimate (Flesch Reading Ease/Grade Level) plus a subjective ICP-relevancy score per crawled page, kept in separate sections. Wave W5."4license: AGPL-3.0-or-later5compatibility: "Claude Code, Cursor, ChatGPT Codex, Claude Cowork."6metadata:7 source: https://skillmd.com/skills/legioncodeinc/content-semantics-stinger-28 hive-tier: stinger9 hive-drone: content-semantics-wasp-drone10 research-window: "2026-08-18 (single sweep, two clusters: seo-standards, aeo-and-answer-engines)"11 primary-surface: external-website-audit12---1314# Content Semantics Stinger1516You are equipping **content-semantics-wasp-drone**, part of the Website17Auditor by Legion Code Inc. plugin. Full scope and acceptance criteria:18[prd-010-content-semantics](../../library/requirements/backlog/prd-010-content-semantics/prd-010-content-semantics-index.md).1920## Purpose2122Produce the run's `03-seo/content-semantics.md` sub-audit: a quantified,23formula-shown reading-level estimate for every crawled page, and a24separately-labeled `[subjective]` ICP-relevancy score per page against the25ICP `icp-positioning-stinger` already determined. These are two26independent findings about the same page and must never be merged into one27number or one section; a page can be effortlessly readable and completely28off-ICP, or dense and jargon-heavy yet exactly on-ICP for a technical29buyer persona.3031## When to use3233- Wave W5 of every audit run, reading `site-data/` and `02-positioning/`34 (both read-only)35- Distinguishing a genuinely low-reading-level page from one that is36 merely off-ICP; the two are commonly conflated and this Stinger exists37 specifically to keep them apart38- Judging whether a page clears Google's stated "non-commodity content"39 bar as one input to the ICP-relevancy score4041## When not to use4243- Technical structure, metadata, indexation, or internal-link-graph44 analysis of the same pages. That is `technical-seo-stinger`'s and45 `internal-linking-stinger`'s scope respectively.46- Determining the site's niche, ICP, or conversion-action taxonomy from47 scratch. That is `icp-positioning-stinger`'s scope; this Stinger applies48 its output, never re-derives it.49- Crawling or fetching a page not already in `site-data/`. This Stinger50 never crawls; that is `site-crawler-wasp-drone`'s job.5152## Procedure53541. Run `references/scripts/reading-level.py` against `site-data/*.md` to55 produce the quantified reading-level estimate (word/sentence/syllable56 counts, Flesch Reading Ease, Flesch-Kincaid Grade) per page, stating the57 formula-choice grounding caveat explicitly. See58 `guides/01-reading-level-scoring.md`.592. Read `02-positioning/`'s ICP and conversion-action taxonomy (do not60 re-derive it) and apply `references/templates/icp-relevancy-scoring-61 rubric-template.md` to score every page's `[subjective]` ICP-relevancy,62 including the non-commodity-content check. See63 `guides/02-icp-relevancy-scoring.md`.643. Observe and report the supporting content-structure signals (lead-65 paragraph length against both cited ranges, heading structure, schema66 presence) that inform the ICP-relevancy judgment, each with its67 sourcing caveat. See `guides/03-content-structure-signals.md`.684. Assemble `03-seo/content-semantics.md` from69 `references/templates/content-semantics-report-template.md`, keeping70 the quantified and subjective sections clearly separate, fill the71 findings-register rows, and log any rejected/reframed candidate. See72 `guides/04-report-assembly.md`.7374## References map7576- `references/research/distilled-content-semantics.md`, load when a claim77 needs verification, or to check section 8's gap list before assuming78 this archive covers something it does not (readability formulas,79 ICP-scoring methodology).80- Source research archive (not shipped with the plugin): the shipped distillation summarizes it; do not require it.81 its primary source.82- `references/scripts/reading-level.py`, run once per audit against83 `site-data/*.md`; do not hand-count words, sentences, or syllables. Its84 docstring carries the formula-grounding caveat in full.85- `references/templates/content-semantics-report-template.md`, load when86 assembling `03-seo/content-semantics.md`.87- `references/templates/icp-relevancy-scoring-rubric-template.md`, load88 when scoring the `[subjective]` ICP-relevancy checkpoint; bridges the89 build plan's universal zero-to-six scale to this specific checkpoint.90- `guides/01-reading-level-scoring.md` through91 `guides/04-report-assembly.md`, load in order for a full pass; each maps92 to one section of the report template.9394## Related drones and stingers9596- [icp-positioning-stinger](../icp-positioning-stinger) - owns the ICP,97 niche, and conversion-action taxonomy this Stinger applies to score98 page-level relevancy. Read its output, never duplicate its taxonomy.99- [internal-linking-stinger](../internal-linking-stinger) - sibling100 wave-W5 Stinger over the same `site-data/`, link-structure analysis101 rather than copy quality; runs concurrently, no write contention.102- [technical-seo-stinger](../technical-seo-stinger) - owns the technical103 structure, metadata, and indexation sub-audit for the same page set;104 content quality (this Stinger) and technical structure are scored105 separately per the build plan's weight table.106- [content-semantics-wasp-drone](../../agents/content-semantics-wasp-drone.md) -107 this Stinger's paired Drone.108109## Critical Directive110111- You must read all files and context contained within your skill.112- In the event your core knowledge does not provide sufficient guidance you must make every attempt to search the internet, related knowledge base documentation files, and other available resources to supplement your knowledge prior to proceeding with your task.113- Additional related skills can be found here:114 - [icp-positioning-stinger](../icp-positioning-stinger) - ICP and conversion-action taxonomy this Stinger applies but does not own.115 - [internal-linking-stinger](../internal-linking-stinger) - sibling wave-W5 Stinger, link structure rather than copy quality.116 - [technical-seo-stinger](../technical-seo-stinger) - technical structure/metadata sub-audit over the same page set.117118## Ship Gate119120Ship Gate removed: research-only stinger, produces no committable code.121This Stinger's output is a findings report (`03-seo/content-semantics.md`)122written to the target audit workspace outside this repository; it never123proposes a diff or a commit to this plugin's own tracked source, so the124security-stinger / quality-stinger / github-repo-health-stinger close-out125sequence does not apply.