Token导航 LogoToken导航

Agent Skill · 研究检索

seo-local(SEO 本地)

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

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

总安装 275周安装 11GitHub Stars 28下载 89核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/mangollc/claude-seo-skill --skill seo-local

这个 Skill 是做什么的

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

用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于需要根据关键词或任务场景进行信息检索的场景,如本地 SEO 查询。通过 npx skills add 命令从指定 GitHub 仓库安装,需确认权限范围和是否触发联网操作。

建议结合原始 README 核验具体用法,注意检查维护状态和潜在的文件读写行为。安装前应评估是否需要执行外部命令或访问敏感数据,避免误改生产环境。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

seo-local 怎么安装?

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

seo-local 支持哪些 AI 工具?

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

seo-local 需要什么权限?

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

seo-local 是免费的吗?

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

seo-local 用的人多吗?

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

seo-local 安全吗?

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

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

值得选的地方

  • 同时适配 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调用外部服务未明确有提醒
seo-local

SEO 本地 · 本页

27528需要联网未明确有提醒

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

SKILL.md 原文

Local SEO & Google Business Profile

Load client context first. Requires gbp section in client config. See seo-keywords rules/client-setup.md.

File Organization

local/
├── gbp-posts/
│   ├── calendar-{month}-{year}.json     # Monthly posting calendar
│   └── posts/
│       └── post-{date}-{slug}.md        # Individual posts
├── nap-audit.json                        # NAP consistency results
├── citations.json                        # Citation audit
├── competitor-gbp-analysis.json          # Competitor GBP research
└── review-templates.md                   # Review response templates

Competitor GBP Research

Before generating posts, research what competitors are doing:

# Search for competitor businesses in local SERPs
firecrawl search "{service} {city}" --limit 20 -o .seo/clients/{slug}/local/.firecrawl/local-serps.json --json &
firecrawl search "{business_name} {city} reviews" --limit 10 -o .seo/clients/{slug}/local/.firecrawl/reviews-search.json --json &
wait

Analyze competitor patterns:

  • What types of posts are they publishing? (Offers, updates, events, tips)
  • How frequently are they posting?
  • What CTAs are they using? (Call now, Book online, Learn more, Get offer)
  • What photos are they sharing? (Team, work-in-progress, before/after, office)
  • What keywords do they use naturally in posts?

GBP Post Types

1. What's New (Updates)

  • Business updates, new services, team news
  • 100-300 words
  • Include a relevant photo suggestion
  • Example: "We've expanded our service area to include {neighborhood}..."

2. Offer Posts

  • Seasonal promotions, discounts, limited-time offers
  • Include: offer details, terms, expiration date
  • CTA: "Redeem offer" or "Call now"
  • Example: "$50 off your first {service} — mention this post when you call..."

3. Event Posts

  • Community events, workshops, open houses
  • Include: date, time, location, what to expect
  • CTA: "Sign up" or "Learn more"

4. Product/Service Highlights

  • Showcase a specific service or product
  • Include benefits, what makes it different
  • CTA: "Book now" or "Get a quote"
  • Example: "Did you know we offer 24/7 emergency {service}?..."

5. Educational/Tips

  • Share expertise, position as authority
  • Quick tips related to the industry
  • CTA: "Learn more" with link to blog post
  • Example: "3 signs your {item} needs {service}..."

30-Day Posting Calendar Generation

Generate 12-16 posts per month (3-4 per week).

Calendar Rules

  • Monday/Wednesday/Friday posting schedule (or Tue/Thu/Sat for variety)
  • Rotate post types: never post the same type back-to-back
  • Rotate services: cover all services from client config over the month
  • Rotate service areas: if multiple areas, mention different ones
  • Seasonal relevance: tie posts to current season, holidays, weather
  • Local keywords: naturally include {service} {city} and variants in posts
  • Photos: suggest a specific photo type for each post

Calendar Output Format

{
  "month": "March 2026",
  "client": "client-slug",
  "posts": [
    {
      "date": "2026-03-02",
      "day": "Monday",
      "post_type": "educational",
      "title": "3 Signs Your Water Heater Needs Service",
      "body": "Post body text here (150-250 words)...",
      "cta_text": "Book an inspection",
      "cta_url": "https://example.com/water-heater",
      "photo_suggestion": "Photo of technician inspecting a water heater",
      "target_keyword": "water heater repair austin",
      "service": "Water Heater Repair",
      "service_area": "Austin, TX"
    }
  ]
}

Post Writing Guidelines

  • Write in the brand's voice (professional but approachable)
  • Include the business name naturally
  • Mention the city/service area in each post
  • Use local landmarks or references when appropriate
  • End with a clear CTA
  • Keep under 300 words (GBP truncates long posts)
  • No hashtags (GBP isn't social media)

NAP Consistency Audit

Check Name, Address, Phone across major directories:

# Search for business across platforms
firecrawl search "{business_name} {city}" --limit 20 -o .seo/clients/{slug}/local/.firecrawl/nap-search.json --json
firecrawl search "{business_name} {phone}" --limit 10 -o .seo/clients/{slug}/local/.firecrawl/nap-phone.json --json

Check these directories:

  • Google Business Profile
  • Yelp
  • Facebook Business
  • Apple Maps / Apple Business Connect
  • Bing Places
  • BBB (Better Business Bureau)
  • Yellow Pages / YP.com
  • Angi (formerly Angie's List)
  • Thumbtack
  • HomeAdvisor (for home services)
  • Nextdoor
  • Industry-specific directories

For each listing check:

  • Business name matches exactly (no abbreviations, no extra words)
  • Address matches exactly (same format, suite number, etc.)
  • Phone number matches (same format, no tracking numbers)
  • Website URL is correct
  • Hours are accurate
  • Categories are appropriate

Flag inconsistencies with specific corrections needed.

Local Citation Audit

Priority Citation Sources by Industry

Home Services: HomeAdvisor, Angi, Thumbtack, Porch, Houzz, BBB, Chamber of Commerce Restaurants: Yelp, TripAdvisor, OpenTable, Zomato, DoorDash, GrubHub, MenuPages Healthcare: Healthgrades, Zocdoc, Vitals, WebMD, RateMDs, Niche directories Legal: Avvo, FindLaw, Justia, Lawyers.com, Martindale-Hubbell Real Estate: Zillow, Realtor.com, Redfin, Homes.com, local MLS Automotive: CarFax, AutoTrader, Cars.com, DealerRater, Edmunds General: Google, Bing, Apple Maps, Yelp, Facebook, BBB, Chamber of Commerce, YP, Foursquare, Superpages, CitySearch, MerchantCircle, Manta, MapQuest

For each citation source:

  • Listed? (yes/no)
  • NAP accurate? (yes/inconsistent/not listed)
  • Profile complete? (basic/moderate/comprehensive)
  • Reviews present? (count if available)

Review Response Templates

Positive Review Responses (vary between these)

Template 1 — Personal: "Thank you so much, {name}! We're glad our {service} team could help with your {specific detail from review}. It's customers like you that make what we do worthwhile. We look forward to serving you again!"

Template 2 — Service-focused: "We appreciate the kind words, {name}! Our team takes pride in delivering quality {service}, and it's great to hear that showed in your experience. Don't hesitate to reach out if you need anything in the future."

Template 3 — Brief: "Thanks for the wonderful review, {name}! We're so happy you had a great experience. See you next time!"

Template 4 — Referral-oriented: "Thank you for the 5-star review, {name}! We're thrilled you're happy with our {service}. If you know anyone who needs {service category}, we'd love to help them too!"

Template 5 — Detailed: "What a great review, {name}! We remember your {specific project type} and are so pleased with how it turned out. Your satisfaction is our top priority. Thank you for choosing {business_name}!"

Negative Review Responses (vary between these)

Template 1 — Empathetic: "We're sorry to hear about your experience, {name}. This isn't the level of service we aim to provide. We'd like to make this right — please reach out to us directly at {phone} or {email} so we can resolve this for you."

Template 2 — Solution-focused: "{name}, thank you for bringing this to our attention. We take all feedback seriously and want to address your concerns. Please contact our team at {phone} so we can discuss how to resolve this."

Template 3 — Ownership: "We apologize for falling short, {name}. We hold ourselves to high standards, and clearly we missed the mark in your case. Please call us at {phone} — we want to understand what happened and make it right."

Template 4 — Factual: "{name}, we appreciate your feedback. We'd like to look into the specifics of your experience. Could you please contact us at {email}? We want to ensure we address your concerns thoroughly."

Template 5 — Gracious: "Thank you for your honest feedback, {name}. We're sorry your experience didn't meet expectations. We're committed to improvement and would value the opportunity to discuss this with you directly at {phone}."

Response rules:

  • Respond within 24 hours
  • Always use the reviewer's name
  • Reference specific details from their review
  • Never argue or get defensive
  • Take the conversation offline for negative reviews
  • Keep it professional but warm

Local Keyword Optimization

For each service in client config, generate geo-modified keyword variants:

PatternExampleIntent
{service} {city}"plumber austin"Primary local
{service} {city} {state}"plumber austin tx"Long-tail
{service} near {neighborhood}"plumber near downtown austin"Hyperlocal
best {service} in {city}"best plumber in austin"Commercial
{service} cost {city}"plumber cost austin"Transactional
emergency {service} {city}"emergency plumber austin"Urgent
{service} near me"plumber near me"Mobile
{service} reviews {city}"plumber reviews austin"Social proof
affordable {service} {city}"affordable plumber austin"Price-sensitive
{service} open now"plumber open now"Urgent/hours

Map each variant to:

  • Recommended landing page (existing or new)
  • GBP post usage (which posts should target this keyword)
  • Priority (based on revenue potential)

平台分布

Codex

36.46%
按下载量换算32

Claude

31.72%
按下载量换算28

Cursor

17.48%
按下载量换算16

Gemini CLI

10.03%
按下载量换算9

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills