Token导航 LogoToken导航

Agent Skill · 研究检索

programmatic-seo-spy(programmatic SEO SPY 搜索)

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

programmatic-seo-spy 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 68,166。

总安装 235周安装 10GitHub Stars 607下载 82核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。支持基于关键词、任务场景或来源线索进行信息筛选与整理。通过 npx 命令从指定 GitHub 仓库安装,需结合原始 README 确认具体用法。

安装前建议核实权限范围、维护状态及是否涉及联网、命令执行或文件读写操作。programmatic-seo-spy 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/programmatic-seo-spy

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/athina-ai/goose-skills --skill programmatic-se…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

programmatic-seo-spy 怎么安装?

在终端执行 npx skills add https://github.com/athina-ai/goose-skills --skill programmatic-seo-spy。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

programmatic-seo-spy 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

programmatic-seo-spy 需要什么权限?

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

programmatic-seo-spy 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

programmatic-seo-spy 用的人多吗?

公开数据是累计安装 235 次,近一周安装 10 次,下载 82 次,GitHub 607 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

programmatic-seo-spy 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
programmatic-seo-spy

programmatic SEO SPY 搜索 · 本页

235607需要联网未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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 token — APIFY_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?"

平台分布

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 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills