← ClaudeAtlas

hoo-keyword-intellisted

Use for keyword research, competitor keyword gaps, "what should we rank for", "keyword ideas for X", or the /organic-os:keywords command. Detects the user's Google Ads access tier and degrades honestly.
shalintripathi/organic-os · ★ 5 · AI & Automation · score 70
Install: claude install-skill shalintripathi/organic-os
# Keyword intelligence (tiered) 0. Read site-profile.yaml (google_ads.status, keywords.targets, competitors, geos, languages). Source env from `~/.config/organic-os/<site-slug>.env` if present. ## Tier detection (once per session) Run: `PYTHONPATH="$CLAUDE_PLUGIN_ROOT/lib" python3 -c "..."` snippet importing `hoo.google_ads.tier`: if env vars missing -> tier "none". Else build real_client() and `tier.detect()` -> basic|explorer. Tell the user which tier is active and what that enables. In the same pass, check whether a search-data adapter's tools are present in this session (the search-data capability slot, ADR-0009 in the repo; the known adapter is OpenSEO - tool surface listed in `$CLAUDE_PLUGIN_ROOT/docs/connectors.md`, OpenSEO section; verify against the tools actually present, never pin the list). Present: the search-data adapter section below applies on top of whatever tier is active. Absent: every tier behaves exactly as it does today, and nothing is fabricated in its place. ## basic (or standard) 1. Ideas: `keyword_ideas.run` with profile target keywords as seeds AND, per competitor, `site_seed=<competitor domain>`. Cache dir: `<brain>/keywords/cache/`. 2. Gap: ideas(own site_seed) vs ideas(competitor site_seed) - keywords in their set, absent from ours, volume >= 100. Rank by volume x profile fit. 3. Metrics for the shortlist: `historical.run` (batches of 200 handled inside). 4. Write `runs/YYYYMMDD-keywords/` (01-ideas.json, 02-gaps.json, REPORT.md)