Token导航 LogoToken导航

Agent Skill · 研究检索

seo-team-the-doctor(SEO team THE doctor 搜索)

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

seo-team-the-doctor 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为接触敏感数据;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 72,323。

总安装 188周安装 8GitHub Stars 公开资料未说明下载 66核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/skillatlas/skills --skill seo-team-the-doctor

这个 Skill 是做什么的

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

用于查找和筛选与 SEO 问题诊断与修复相关的信息。适合在技术缺陷排查、性能瓶颈识别等场景中使用。通过 npx 命令从 GitHub 仓库安装并集成。使用前应确认权限范围、维护状态及是否触发网络访问或系统操作。seo-team-the-doctor 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/seo-team-the-doctor

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/skillatlas/skills --skill seo-team-the-doctor;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

seo-team-the-doctor 怎么安装?

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

seo-team-the-doctor 支持哪些 AI 工具?

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

seo-team-the-doctor 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

seo-team-the-doctor 是免费的吗?

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

seo-team-the-doctor 用的人多吗?

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

seo-team-the-doctor 安全吗?

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

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

值得选的地方

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

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

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

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 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调用外部服务未明确有提醒
seo-team-the-doctor

SEO team THE doctor 搜索 · 本页

188—接触敏感数据未明确有提醒

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

SKILL.md 原文

SEO Doctor — Site & Page Diagnostician

The Doctor audits sites and pages, scores SEO health across five dimensions, and produces a prioritised fix list.

Prerequisites

  • DataForSEO API key — This skill uses seocli, which sources all its data from the DataForSEO API. You need a DataForSEO account and API key before using any SEO team skill.

Two Operating Modes

Infer mode from the user's request:

ModeTriggerAPI Cost
Site-Wide Audit"audit my site," "health check," domain reference without specific page+keyword25–35 calls
Single-Page AuditSpecific URL + keyword, "why isn't this ranking," page vs competitor comparison9–12 calls
IF user mentions a specific URL + keyword pair → Single-Page Audit
ELSE IF user mentions a domain, "my site", "health check", or "audit" → Site-Wide Audit
ELSE → Ask: "Would you like me to audit your entire site, or diagnose a specific page?"

Pre-Flight (Both Modes)

Before any API calls:

  1. Check audit history — Look in workspace/seo/audit-history/ for recent audits. If one ran within 7 days, offer to reuse crawl data.
  2. Load config — Read workspace/seo/config.yaml for domain, competitors, location.
  3. Load keyword context — Read workspace/seo/keyword-map.json for target keywords to spot-check.
  4. Confirm scope (site-wide only) — Ask site size (small <50, medium 50–500, large >500) and type (blog, catalog, SaaS, mixed).

Cost Estimation & Confirmation

Before executing, estimate API calls and confirm with the user:

Site-Wide: ~25–35 calls (1 crawl + 6 result retrievals + 3–5 Lighthouse + 5 backlink + 3 ranking + 1 LLM mentions + 5–10 AI Overview checks + 1 llms.txt check).

Single-Page: ~9–12 calls (1 on-page live + 1 SERP organic + 1 SERP AI mode + 3 competitor on-page + 3 competitor backlinks).


Mode 1: Site-Wide Audit

PRE-FLIGHT → CRAWL → LIGHTHOUSE → BACKLINKS → RANKINGS → AI VISIBILITY → ON-PAGE SPOT-CHECKS → SCORE → PRIORITISE → REPORT

Step 1 — Technical Crawl

Start an async crawl with content parsing, micromarkup validation, spell checking, resource loading, and keyword density enabled:

seocli on-page create \
  --target "example.com" \
  --max-crawl-pages 500 \
  --enable-content-parsing \
  --validate-micromarkup \
  --check-spell \
  --load-resources \
  --calculate-keyword-density

Adapt crawl config by site signals: small site → --max-crawl-pages 100; large/e-commerce → --max-crawl-pages 500 --crawl-delay 1; international → --allow-subdomains; pre-launch → --enable-www-redirect-check.

Poll for completion, then retrieve results:

seocli on-page summary --id <task-id>
seocli on-page pages --id <task-id> --limit 500
seocli on-page duplicate-content --id <task-id>
seocli on-page duplicate-tags --id <task-id> --type duplicate_title
seocli on-page duplicate-tags --id <task-id> --type duplicate_description
seocli on-page redirect-chains --id <task-id>
seocli on-page resources --id <task-id>

Extract from crawl: Total pages and error pages (4xx, 5xx); pages blocked by robots.txt (check Googlebot, OAI-SearchBot, PerplexityBot); orphan pages; missing title/meta/H1; duplicate titles/descriptions; redirect chains >2 hops; mixed HTTP/HTTPS; broken links; missing canonicals; thin content (<300 words); keyword density outliers (>3% or <0.5%); invalid schema; spelling errors; image alt text coverage.

Step 2 — Performance / Lighthouse

Run Lighthouse on homepage + 3–5 key pages (highest internal link count from crawl, or user-specified):

seocli on-page lighthouse --url "https://example.com/"

Extract: Performance, Accessibility, Best Practices, SEO scores (flag <80). Core Web Vitals: LCP (<2.5s), CLS (<0.1), INP (<200ms). Top performance opportunities.

Step 3 — Backlink Health

seocli backlinks summary --target "example.com"
seocli backlinks bulk-spam-score --targets "example.com"
seocli backlinks referring-domains --target "example.com" --limit 100
seocli backlinks anchors --target "example.com" --limit 50
seocli backlinks bulk-ranks --targets "example.com"

Extract and flag: Total backlinks and referring domains; domain rank; spam score (>30 concerning, >60 toxic); referring domain diversity ratio; anchor text distribution (>30% exact-match = over-optimisation); top referring domains by authority.

Step 4 — Keyword Position Snapshot

Use Labs estimates for directional ranking intelligence:

seocli labs bulk-ranking-keywords --targets "example.com"
seocli labs domain-rank-overview --target "example.com"
seocli labs bulk-traffic-estimation --targets "example.com"

Spot-check 5–10 top keywords against live SERPs:

seocli serp google organic live --keyword "target keyword" --depth 10

Extract: Estimated organic keywords, traffic, domain rank trend, top keywords by traffic, spot-check calibration.

Step 5 — AI Visibility Check

seocli ai-optimization llm-mentions --target "example.com"

# For top 5–10 keywords:
seocli serp google ai-mode live --keyword "target keyword"

# Check llms.txt:
seocli on-page live --url "https://example.com/llms.txt"

Extract and flag: LLM platform mention count and sentiment; AI Overview presence per keyword; missing llms.txt (easy win).

Step 6 — On-Page Spot Checks

Analyse the top 20 pages (by internal link count or estimated traffic) from crawl data against the 8-factor on-page rubric. See reference/scoring.md for the full rubric.

Also assess Content Freshness (flag pages >12 months without updates) and E-E-A-T signals (author credentials, expert quotes, original data, authoritative sources — flag pages where ≥2 of 4 are present).

Step 7 — Scoring

Score across 5 dimensions (0–100 each), weighted:

DimensionWeightKey Data Sources
Technical Health30%Crawl errors, redirects, page speed, CWV, mobile
Content Quality25%Thin/duplicate content, spelling, keyword density, E-E-A-T, freshness
On-Page Optimisation20%Titles, metas, headings, schema, internal links, alt text
Backlink Profile15%Domain rank, referring domains, spam score, anchor distribution
AI Visibility10%LLM mentions, AI Overview citations, llms.txt
Overall SEO Score = Σ (dimension_score × dimension_weight)

Grade thresholds: A+ (90–100), A (80–89), B (70–79), C (60–69), D (40–59), F (0–39). See reference/scoring.md for detailed scoring methodology.

Step 8 — Issue Prioritisation

Categorise every issue into four severity tiers:

Critical — Blocking indexing/rendering: noindex on important pages, broken redirects to key pages, 5xx errors, missing sitemap, Googlebot blocked, rendering failures.

Important — Directly hurting rankings: duplicate content, missing titles on high-traffic pages, thin content on key pages, toxic backlinks (spam >60), slow speed (LCP >4s, CLS >0.25), 3+ hop redirects.

Opportunity — Quick wins: missing meta descriptions, missing schema, no llms.txt, orphan pages, missing alt text, no LLM mentions, content needing refresh (>12 months).

Nice-to-Have — Marginal gains: spelling errors, suboptimal title length, minor heading hierarchy issues, anchor diversity improvements.

Step 9 — Report Generation

Generate a Markdown report saved to workspace with:

  1. SEO Health Score (0–100) with dimensional breakdown
  2. Executive Summary — 3-sentence diagnosis
  3. Prioritised Issue List — Critical → Important → Opportunity → Nice-to-Have, each with: issue, affected URLs, severity, fix instructions
  4. Quick Wins — Top 5–10 highest-impact, lowest-effort fixes
  5. Technical Issues Table
  6. Backlink Health Summary
  7. AI Visibility Report
  8. Performance Summary — Lighthouse scores and CWV

File naming: {domain}-audit-{date}.md

Forced Reasoning Phase

Before scoring, explicitly document: (1) what's present and healthy, (2) what's missing or broken, (3) what's critical vs cosmetic. This prevents recency bias in scoring. Include as a "Findings Summary" section in the report.


Mode 2: Single-Page Audit

FETCH PAGE → PULL SERP → SCORE PAGE → FETCH COMPETITORS → COMPARE → GAP ANALYSIS → REPORT

Step 1 — Instant Page Analysis

seocli on-page live \
  --url "https://example.com/target-page" \
  --load-resources \
  --validate-micromarkup \
  --check-spell \
  --enable-content-parsing

Extract: Title, meta description, H1, heading hierarchy, word count, keyword density, schema, canonical, link counts, alt text coverage, speed indicators, mobile rendering.

Step 2 — SERP Analysis

seocli serp google organic live --keyword "target keyword" --depth 20
seocli serp google ai-mode live --keyword "target keyword"

Extract: Top 20 results with URLs/titles/descriptions, SERP features (snippet, PAA, video, images, knowledge panel, AI Overview).

Step 3 — Score the Target Page

Apply the 8-factor weighted single-page rubric. See reference/scoring.md for full rubric details. Factors: Title Tag (15%), Headers (10%), Content (25%), Keywords (15%), Internal Links (10%), Images (10%), Technical (10%), Meta (5%).

Step 4 — Competitor Comparison

For the top 3 ranking pages from Step 2:

seocli on-page live --url "https://competitor.com/page" --enable-content-parsing
seocli backlinks summary --target "https://competitor.com/page"

Build a comparison matrix: word count, H2 sections, internal links, backlinks, schema types, page speed.

Step 5 — Gap Analysis

From the comparison, identify specific gaps with prescriptions:

Gap TypeDetectionExample Prescription
Content DepthWord count <50% of avg top 3"Expand from 600 to ~2,500 words. Add sections on [topics]."
Topic CoverageH2 topics in top 3 you're missing"Add sections: Pricing, Pros & Cons, Alternatives."
SchemaCompetitors have structured data, you don't"Add FAQ + Article schema."
Internal LinksCount <50% of avg top 3"Add 8–10 internal links from high-authority pages."
BacklinksReferring domains far below competitors"Content-level gap. Pursue link-worthy assets."
Intent/Format Mismatch4+ of top 5 are a different content type"Reformat to match SERP expectation. This is a format problem, not depth."
FreshnessOlder than competitors"Update with current data and statistics."
AI OptimisationCompetitors cited in AI Overview, you aren't"Add definitions, statistics, numbered lists."

Intent/Format Mismatch Detection: Classify top 5 SERP results by content type. If 4+ share a type and your page is different, flag as intent mismatch and elevate priority — this requires reframing, not just expansion.

Step 6 — Report Generation

  1. Page Audit Score (0–100) with per-factor breakdown
  2. Competitor Comparison Card — side-by-side metrics
  3. Gap Analysis — prioritised fixes with estimated effort
  4. Prescription — the single most impactful action
  5. Quick Wins — fixes achievable in under 30 minutes

File naming: {slug}-page-audit-{date}.md


Shared Data & Handoff Protocol

Reads From

  • workspace/seo/config.yaml — domain, competitors, location
  • workspace/seo/keyword-map.json — target keywords for spot-checking
  • workspace/seo/audit-history/ — previous audits (reuse/compare)

Writes To

  • workspace/seo/audit-history/{domain}-{date}.json — timestamped audit (overall score, dimensional scores, issue counts, top keywords, top quick wins, timestamp)

Handoff

Receives from seo-team-the-researcher: keyword-map.json for spot-check targeting. Receives from seo-team-the-general: Priority pages/keywords from strategy plan's next_actions. Sends to seo-team-the-writer: Pages needing refresh, optimisation, or schema — with specific prescriptions. Sends to seo-team-the-general: Audit scores and issue counts for tracking improvement over time. Sends to seo-team-the-researcher: Keywords discovered during audit not in the keyword map.


Cost Guardrails

GuardrailImplementation
Pre-flight estimateCalculate expected calls, present to user before starting
Reuse recent crawlsOffer to reuse crawl data <7 days old
Batch endpointsUse bulk-spam-score, bulk-ranks, bulk-traffic-estimation, bulk-ranking-keywords
Progressive depthStart with summaries; drill into per-page detail only for flagged issues
Lighthouse samplingTest 3–5 pages, not all — homepage + highest internal link count
AI check samplingCheck 5–10 keywords for AI Overview, not the full universe

Reference Files

平台分布

Codex

38.46%
按下载量换算25

Claude

30.3%
按下载量换算20

Cursor

19.23%
按下载量换算13

Gemini CLI

8.74%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

可疑

Snyk

可疑

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

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

继续浏览同类 Skills