Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

programmatic-seo-spyprogrammatic SEO SPY 搜索

Agent Skill

programmatic-seo-spy 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

235

周安装

10

GitHub Stars

607

下载量

82
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:programmatic-seo-spy(programmatic SEO SPY 搜索)
来源仓库:https://github.com/athina-ai/goose-skills
仓库路径:skills/programmatic-seo-spy
安装命令:
npx skills add https://github.com/athina-ai/goose-skills --skill programmatic-seo-spy
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/athina-ai/goose-skills --skill programmatic-seo-spy

简介

用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。

  • 支持基于关键词、任务场景或来源线索进行信息筛选与整理。
  • 通过 npx 命令从指定 GitHub 仓库安装,需结合原始 README 确认具体用法。
  • 安装前建议核实权限范围、维护状态及是否涉及联网、命令执行或文件读写操作。
  • programmatic-seo-spy 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Programmatic SEO Competitor Spy

Before building your own programmatic SEO pages, know what your competitors are already doing. This skill crawls competitor sitemaps, detects which URL patterns are programmatic, estimates which ones actually drive traffic, assesses template quality, and finds the gaps they're missing.

Core principle: The best pSEO strategy starts with competitive intelligence. If 3 competitors have /vs/ pages and none have /for-{industry}/ pages, that's a signal. This skill turns competitor site structures into strategic intelligence.

When to Use

  • "What programmatic SEO are competitors doing?"
  • "Reverse-engineer competitor SEO pages"
  • "Which pSEO patterns actually work in our space?"
  • "Find pSEO gaps our competitors are missing"
  • "Analyze competitor URL structure for SEO patterns"

Tool Enhancement (Optional)

This skill works with existing capabilities but is dramatically better with domain analytics data that shows actual traffic per URL pattern.

Agent Prompt to User

"I can analyze competitor site structures with our existing crawling tools. For the most accurate results — especially knowing which patterns actually drive traffic vs. just existing — I'd recommend connecting a domain analytics API." Recommended: DataForSEO (pay-per-use, ~$0.02-0.05 per domain analysis) - Sign up at dataforseo.com → get API login + password - Set DATAFORSEO_LOGIN and DATAFORSEO_PASSWORD env vars Alternatives that also work: - SEMrush API (if you have a subscription) → set SEMRUSH_API_KEY - Ahrefs API (if you have a subscription) → set AHREFS_API_TOKEN - SimilarWeb API (if you have access) → set SIMILARWEB_API_KEY "Want to use one of these, or should I proceed with baseline mode? Baseline will detect patterns and assess template quality, but traffic estimates will be inferred rather than measured."

Mode Selection

  • Enhanced mode — Domain analytics API provides organic keywords and estimated traffic per URL. Enables confident "this pattern drives X traffic" conclusions. Can show which specific pages within a pattern rank well.
  • Baseline mode — Uses site-content-catalog for URL crawling, seo-domain-analyzer for domain-level metrics, web_search for spot-checking rankings. Pattern detection is equally good. Traffic attribution is directional, based on page count × domain authority × keyword indicators.

Phase 0: Intake

  1. Competitors — 1-5 competitor URLs to analyze
  2. Your product URL — So we can compare coverage
  3. Category — What market/category are these competitors in?
  4. Specific interest? — Looking for anything specific (vs/ pages, integrations, etc.) or full analysis?
  5. Tool preference — Enhanced mode with domain analytics API, or baseline? (see Tool Enhancement above)

Phase 1: Sitemap Crawl

For each competitor, run site-content-catalog:

python3 skills/site-content-catalog/scripts/catalog_content.py \
  --url "<competitor_url>" \
  --output json

Collect:

  • All URLs from sitemap and internal crawl
  • Page titles
  • URL structure/hierarchy
  • Last modified dates (if available)

Phase 2: Pattern Detection

2A: URL Clustering

Group URLs by structural patterns using regex matching:

Pattern RegexExample URLsCategory
/vs/.* or /compare/.*/vs/competitor-a, /vs/competitor-bComparison
/integrations?/.*/integrations/slack, /integrations/hubspotIntegration
/for-.* or /solutions/.*/for-startups, /for-enterpriseVertical
/use-cases?/.*/use-cases/project-managementUse case
/alternatives?(-to)?/.*/alternatives/competitor-aAlternatives
/templates?/.* or /examples?/.*/templates/invoice, /templates/proposalTemplates
/glossary/.* or /what-is/.*/glossary/term-a, /what-is/crmGlossary
/tools?/.* or `/calculat(ore)/.*`/tools/roi-calculator
/blog/.* (exclude from pSEO)/blog/how-to-xEditorial (not pSEO)

For each detected pattern:

  • Page count — How many pages follow this pattern?
  • Data axis — What varies per page? (competitor name, tool name, industry, etc.)
  • URL consistency — Are URLs cleanly structured or messy?
  • Coverage completeness — Have they covered the obvious variations?

2B: Programmatic vs. Editorial Classification

Not every URL pattern is programmatic. Classify each cluster:

  • Programmatic — Clearly templated: consistent URL structure, similar page titles following a pattern, high page count, structured content
  • Semi-programmatic — Template with heavy manual customization
  • Editorial — Individually written, no template pattern
  • Auto-generated — Thin/low-quality programmatic (tag pages, archive pages)

Focus analysis on Programmatic and Semi-programmatic clusters only.

Phase 3: Traffic & Performance Analysis

Enhanced Mode (DataForSEO / SEMrush / Ahrefs)

For each competitor domain, pull organic keywords data:

# DataForSEO example
POST /v3/dataforseo_labs/google/ranked_keywords/live
{
  "target": "competitor.com",
  "filters": [
    ["ranked_serp_element.serp_item.url", "contains", "/vs/"]
  ]
}

Per pattern cluster:

  • Total ranking keywords across all pages in the pattern
  • Estimated monthly organic traffic to the pattern
  • Average ranking position for pages in this pattern
  • Top-performing pages within the pattern (which variations rank best?)
  • Keyword difficulty distribution (are they targeting easy or hard keywords?)

Baseline Mode

Estimate traffic indicators:

  • Run seo-domain-analyzer for overall domain metrics
  • Spot-check 3-5 pages per pattern via web_search — do they appear in top 10?
  • Check if pages are indexed (site:competitor.com/vs/)
  • Infer relative traffic: pattern page count × indexation rate × domain authority proxy
  • Note: these are directional estimates, not exact numbers

Phase 4: Template Quality Assessment

For each programmatic pattern, fetch 3-5 sample pages via fetch_webpage:

# Pick pages from the pattern — one high-variation, one low-variation, one middle

Evaluate template quality on:

DimensionScore 1-5What to Look For
Content depthWord count, sections, detail level
Unique value per pageDoes each page offer something you can't get from the template alone?
Data richnessTables, comparisons, stats, screenshots
Freshness signalsUpdated dates, current pricing, recent reviews
Internal linkingLinks to related pages, hub structure
CTA integrationContextual CTAs vs. generic banners
Schema markupStructured data, FAQ schema, review schema

Quality tiers:

  • 4-5 avg: Well-executed pSEO — hard to beat without significant differentiation
  • 3-4 avg: Decent but improvable — opportunity to out-template them
  • 1-3 avg: Thin/low-quality — easy to dominate with better content

Phase 5: Gap Analysis

5A: Pattern Coverage Matrix

Pattern TypeCompetitor ACompetitor BCompetitor CYouGap?
vs/ comparisons25 pages ★★★★10 pages ★★★00✓ A leads
integrations/40 pages ★★★60 pages ★★★★20 pages ★★0✓ B leads
for-{industry}/008 pages ★★0✓ Wide open
alternatives/5 pages ★★★000✓ Lightly competed
glossary/100 pages ★★050 pages ★★★0⚠️ Volume play

5B: Variation Gaps

Within each pattern competitors use, find missing variations:

  • Competitors they haven't written vs/ pages for
  • Integrations they support but haven't built pages for
  • Industries they serve but haven't targeted
  • These are your quick-win entries

5C: Pattern White Space

Entire pattern types no competitor has built:

  • Highest opportunity — no one to outrank, first-mover advantage
  • Validate search demand exists (Phase 1D of programmatic-seo-planner)

5D: Quality Gaps

Patterns where competitors have pages but they're low quality:

  • Thin content (< 500 words, no unique data)
  • Outdated (old screenshots, wrong pricing)
  • Missing schema markup
  • No visual differentiation between pages
  • These are "out-template" opportunities

Phase 6: Output

# Programmatic SEO Competitive Landscape — [Category] — [DATE]

## Competitors Analyzed
- [Competitor A] — [domain metrics, total pages crawled]
- [Competitor B] — [domain metrics, total pages crawled]
- [Competitor C] — [domain metrics, total pages crawled]

## Executive Summary
- [N] programmatic patterns detected across [M] competitors
- Strongest competitor pSEO: [Competitor X] with [pattern] ([N] pages, [quality])
- Biggest opportunity: [pattern type] — [reasoning]
- Quick wins: [N] variation gaps in existing competitor patterns

---

## Pattern-by-Pattern Analysis

### Pattern: [vs/ Comparisons]
**Who's doing it:** [Competitor A (25 pages, ★★★★), Competitor B (10 pages, ★★★)]
**Traffic estimate:** [X monthly visits across pattern] (enhanced) / [directional estimate] (baseline)
**Template quality:** [summary of strengths/weaknesses]
**Top-performing pages:** [specific pages that rank well]
**Variation gaps:** [competitors/variations they're missing]
**Your opportunity:** [specific recommendation]

### Pattern: [integrations/]
...

---

## Opportunity Ranking

| Priority | Pattern | Opportunity Type | Effort | Expected Impact |
|----------|---------|-----------------|--------|----------------|
| P0 | [pattern] | White space — no competitors | Medium | High |
| P0 | [pattern] | Quality gap — beat weak templates | Low | Medium |
| P1 | [pattern] | Variation gap — fill missing pages | Low | Medium |
| P2 | [pattern] | Head-to-head — outrank strong competitor | High | High |

---

## Recommended Action Plan

1. **Immediate (Week 1-2):** Build [pattern] — [rationale]
2. **Short-term (Month 1):** Build [pattern] — [rationale]
3. **Medium-term (Month 2-3):** Build [pattern] — [rationale]

---

## Raw Data
[Link to crawl data, pattern clusters, sample pages analyzed]

Save to the current working directory or wherever the user prefers.

Cost

ComponentCost
Site catalog per competitor (Apify)~$0.05-0.10
SEO domain analyzer per competitor~$0.10-0.20
Page fetches (3-5 per pattern × N patterns)~$0.01-0.05
DataForSEO domain analytics (enhanced)~$0.10-0.50 per competitor
AnalysisFree (LLM reasoning)
Total (baseline, 3 competitors)~$0.50-1.00
Total (enhanced, 3 competitors)~$0.80-2.00

Tools Required

  • Apify API tokenAPIFY_API_TOKEN env var
  • Upstream skills: site-content-catalog, seo-domain-analyzer, fetch_webpage
  • Optional (enhanced): DataForSEO (DATAFORSEO_LOGIN + DATAFORSEO_PASSWORD), SEMrush (SEMRUSH_API_KEY), Ahrefs (AHREFS_API_TOKEN), or SimilarWeb (SIMILARWEB_API_KEY)

Trigger Phrases

  • "What pSEO are competitors doing?"
  • "Reverse-engineer competitor programmatic pages"
  • "Analyze competitor URL structure"
  • "Find pSEO gaps in our space"
  • "What comparison pages do competitors have?"

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.62%
按下载量换算28

Claude

32.11%
按下载量换算26

Cursor

18.52%
按下载量换算15

Gemini CLI

9.18%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills