AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Serp Keyword Harvester

skill-sergekostenchuk-ui-ux-agent-skill-system-serp-keyword-harvester · by sergekostenchuk

Collect and normalize search-demand inputs for public site projects before semantic-core work. Use when a UI/UX or SEO project needs seed keywords, SERP snapshots, autocomplete ideas, People Also Ask, related searches, or a dry-run keyword harvest with approval-gated external search APIs.

No reviews yet
0 installs
10 views
0.0% view→install

Install

$ agentstack add skill-sergekostenchuk-ui-ux-agent-skill-system-serp-keyword-harvester

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets Used
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-sergekostenchuk-ui-ux-agent-skill-system-serp-keyword-harvester)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Serp Keyword Harvester? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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](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](references/openserp-setup.md) and use [assets/openserp-settings.example.json](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](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

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:

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

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.