Index of every page on this site: llms.txt
All skills
ryze-ai-adgent avatar

/competitor-gap

@f587b0a
Run it yourself

Find keywords a competitor ranks for that the user's site doesn't — the content gap, prioritized by volume and winnability. Use when asked "what does competitor.com rank for", "keyword gap vs X", "steal competitor keywords", or "why do they outrank us".

  • 1 file
  • 2.3 KB
  • Updated 4 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/ryze-ai-adgent/open-seo-mcp-skills/competitor-gap

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈68 tokens for metadata: the name and description. ≈503 when used: this file.

Description uses 3.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈270 characters, or 3.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Competitor Gap

Requires

The free Ryze MCP connector (https://connector.get-ryze.ai/mcp). Claude Code: claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp. claude.ai / Desktop / Cursor: add it as a custom connector with the same URL. Setup: https://www.get-ryze.ai/how-to-connect-claude-to-google-meta-ads-mcp?utm_source=github&utm_content=open-seo-mcp-skills

Their rankings are estimates (DataForSEO), yours are real (GSC). Diff them.

Workflow

  1. Competitor's keywords. Via the workspace's DataForSEO tools — Labs ranked_keywords for the competitor domain (request shape: native__get_provider_docs, provider dataforseo). Pull top ~500 by volume. If DataForSEO isn't exposed in this workspace, check for connected ahrefs/semrush providers and use their organic-keywords endpoint instead; if none, stop and say which connection is missing.
  2. Competitor overview. Labs domain_rank_overview — their estimated organic traffic and keyword count, for context.
  3. Your keywords. google_search_console__runRawSearchAnalytics, dimension ["query"], last 90 days, high rowLimit — the full set of queries the user's site gets impressions for.
  4. Diff into three buckets:
    • Gap — competitor ranks top 20, you have zero impressions → new content needed
    • Behind — you both rank but they're ≥ 5 spots ahead → improve existing page
    • Ahead — you outrank them (report briefly; it's the moat)
  5. Prioritize the Gap and Behind buckets by volume × relevance to the user's product. Drop branded competitor terms unless the user wants comparison pages — then list them separately as "vs / alternative" page candidates.

Output

Verdict (how big the gap is, in keywords and estimated traffic), then: Gap table (keyword, their position, volume, suggested page), Behind table (keyword, their pos, your pos, your page, fix), and a top-10 action list. Note explicitly which numbers are estimates (theirs) vs real (yours).

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at f587b0a. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 4 weeks ago

README badge

README badge for ryze-ai-adgent/open-seo-mcp-skills/competitor-gap