sergekostenchuk/ui-ux-agent-skill-system

serp-keyword-harvester

Collect and normalize search-demand inputs for public site projects before semantic-core work.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill serp-keyword-harvester

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

SERP Keyword Harvester

This skill prepares raw search-demand evidence for the pre-design pipeline. It does not decide final site architecture or source/proxy policy; serp-source-configurator owns setup gates and this skill hands structured inputs to semantic-core-builder.

Operating Modes

  • plan: define seed keywords, locales, sources, approvals, and fallback.
  • harvest-local: normalize user-provided keywords, exported CSVs, existing site text, or local reports.
  • harvest-external: use approved SERP/autocomplete APIs or tools; approval required before network calls.
  • audit: review an existing reports/keyword-harvest.json.

Required Workflow

  1. Read references/keyword-harvest-contract.md.
  2. If OpenSERP, AKE, proxy, API keys, engine checkboxes, source settings, or paid-proxy limits are mentioned, route setup to serp-source-configurator first and consume its redacted reports/serp-source-config.json handoff.
  3. If OpenSERP is already approved/configured, read references/openserp-setup.md and use assets/openserp-settings.example.json only as a redacted contract, not as a credential store.
  4. Confirm privacy and approval mode:
  • local inputs and user-provided public facts: allowed;
  • external SERP/API/crawling: explicit approval required;
  • private/authenticated sources: explicit approval plus data-handling note.
  1. Collect or normalize seed keywords, market/locale, project type, and source provenance.
  2. Write or update reports/keyword-harvest.json using assets/keyword-harvest.schema.json as the field contract.
  3. Label every data group as Ran, Skipped, Planned, or Manual.
  4. Hand off to semantic-core-builder; do not invent missing SERP evidence.

Safety Rules

  • Do not scrape or call external services without approval.
  • Do not store API keys, cookies, private URLs, recovery codes, or .env values in reports.
  • Treat OpenSERP as optional-cloud / external-network: no call without explicit approval, configured credentials, query scope, source config, and a data-transfer note.
  • Do not decide proxy provider, paid budget, or engine selection inside this skill when it is not already explicit; use serp-source-configurator.
  • If search APIs return 429/503 or are unavailable, mark the source Skipped and continue with local/user-provided inputs.

Handoff Shape

text
Mode:
Locale/market:
Seed keywords:
Sources used:
Sources skipped:
Source config:
Output path:
Privacy/approval note:
Next skill: semantic-core-builder

Validation

When editing this skill, run:

bash
python3 $CODEX_HOME/skills/.system/skill-creator/scripts/quick_validate.py $CODEX_HOME/skills/serp-keyword-harvester
python3 $CODEX_HOME/skills/senior-skill-architect/scripts/lint_production_skill.py $CODEX_HOME/skills/serp-keyword-harvester

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
sergekostenchuk
コミュニティ

admin-ui-builder

Use when admin/CMS/back-office screens need to be built or specified after admin-ui-orchestrator defines roles, permissions, workflows, and safety gates. Covers tables, forms, editors, moderation queues, dashboards, CRUD surfaces, and state coverage without production destructive actions.

1時間の導入数
1
GitHub Stars
35
更新日
9月13日
sergekostenchuk
コミュニティ

admin-ui-orchestrator

Use when a project needs admin/CMS/back-office UI architecture: roles, permissions, content workflows, AI assistant boundaries, audit logs, destructive-action confirmations, and builder handoff. Planning only; do not perform production admin actions or expose secrets.

1時間の導入数
1
GitHub Stars
35
更新日
9月13日
sergekostenchuk
コミュニティ

analytics-setup-architect

Use when a website or web app needs privacy-aware analytics architecture: GA4, Yandex Metrica, self-hosted analytics, consent, UTM, event taxonomy, funnels, dashboards, and launch verification. Do not mutate real analytics accounts or store credentials without explicit approval.

1時間の導入数
1
GitHub Stars
35
更新日
9月13日
sergekostenchuk
コミュニティ

editorial-quality-gate

Review public site content for editorial quality, source support, prompt residue, duplicate blocks, translation drift, hidden filler, and human usefulness before SEO or LLM-friendly publication. Use this skill when the user asks to quality-gate news briefs, longform explainers, blog posts, topic pages, project pages, translated content, or generated article drafts without changing the live publishing pipeline.

1時間の導入数
1
GitHub Stars
35
更新日
9月13日