keyword-research — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited keyword-research (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Produce a keyword map: a scored, clustered list of search terms worth targeting, each tied to the content that should win it. Governing principle: a keyword is only worth targeting if it survives all six circles — aligned with the positioning, phrased in the customer's language, under-served by competitors, actually searched, winnable with the user's real expertise, and connected to revenue. Traffic that fails circle 6 is vanity.
skills/marketing/positioning-angles first (or infer a provisional one and label it) — circle 1 is unworkable without it.skills/marketing/seo-strategy; this skill is the keyword-selection layer only.skills/marketing/seo-content.One batch; reuse anything already produced by skills/marketing/orchestrator or skills/marketing/positioning-angles:
Don't stall: with a positioning statement and a recognizable market you can draft the full map from knowledge and web research — label all volumes and difficulty as estimates and list them for the user to verify in a tool.
Run the circles as sequential filters: generate wide in circles 1–2, then cut in 3–6.
Expand the positioning statement into 20–40 seed keywords. Take each element of the claim (audience, problem, mechanism, outcome) and list the searches that element implies. Rule: seeds come from the angle, not the category. "Project management tool for remote teams" seeds remote-team keywords (async standups, distributed team communication), not generic project management keywords the incumbents own.
Rewrite every seed in the words customers actually type, harvested from the intake sources. Kill jargon: if customers say "remote work tools", drop "distributed workforce management solutions". Add the question-form variants ("how do I…", "best X for Y", "X vs Y") — those carry the clearest intent.
Check each surviving keyword against the competitors' content (crawl their blog/sitemap or search site:competitor.com <keyword>).
Screen for workable volume. Heuristic (label it as such): target roughly 100–10,000 searches/month — below ~100 rarely repays an article; above ~10,000 is usually incumbent territory for a young domain. Decision rules: established domain with authority (from intake Q4) → the upper bound relaxes; brand-new domain → stay in the low hundreds-to-low-thousands band. If no tool access, estimate from autocomplete breadth, "People also ask" density, and ad presence — and flag every estimate.
Keep only keywords where the user can honestly out-write the current top results — first-hand experience, proprietary data, a named mechanism, or a sharper niche take. If the user can't add anything the top 3 results lack, cut the keyword regardless of volume.
Score what remains by distance to revenue:
Group survivors into topic clusters (one head keyword + 3–8 supporting keywords that one strong article or hub can cover). Priority order: high intent + competitor blind spot first, then high intent + contested, then medium intent gaps. Propose the top 3–5 clusters and have the user confirm the order before content production starts.
# Keyword Map — [Brand]
**Positioning it serves:** "[claim from skills/marketing/positioning-angles]"
**Volume/difficulty source:** [tool name | estimates — user to verify]
## Priority clusters
### Cluster 1: [name] — Priority: HIGH
Target article: "[working title]" — intent: [high/med] — feeds: [lead magnet / product page]
| Keyword | Role | Est. volume | Competition note | Intent |
|---|---|---|---|---|
| [head keyword] | Head | ~N/mo | [gap / thin / contested] | High |
| [supporting] | Support | ... | ... | ... |
### Cluster 2: ...
(3–5 clusters total)
## Cut list (why keywords were rejected)
- "[keyword]" — failed circle [n]: [one-line reason]
(representative sample, not exhaustive)
## Assumptions & verification queue
- [every estimated volume or inferred competitor read, listed for tool verification]
**Next step:** write Cluster 1's target article via skills/marketing/seo-content.skills/marketing/positioning-angles supplies the claim that seeds circle 1; skills/marketing/orchestrator routes here on awareness and scale paths.skills/marketing/seo-content consumes the cluster map one cluster at a time (head keyword + supports + working title cross the boundary); skills/marketing/seo-strategy consumes it as the keyword layer of a full program; skills/marketing/content-atomizer uses cluster themes to steer repurposing.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.