Token导航 LogoToken导航

Agent Skill · 研究检索

seo-optimizer(SEO 优化器)

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

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

总安装 759周安装 31GitHub Stars 1下载 243核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/pixel-process-ug/superkit-agents --skill seo-optimizer

这个 Skill 是做什么的

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

seo-optimizer 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。适用于 SEO 优化相关的信息搜集与筛选,可结合来源仓库和原始 README 核验具体用法。

通过 npx skills add 命令从指定 GitHub 仓库安装,需确认权限范围和维护状态。安装前建议确认是否会触发联网、命令执行或文件读写等操作边界。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

seo-optimizer 怎么安装?

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

seo-optimizer 支持哪些 AI 工具?

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

seo-optimizer 需要什么权限?

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

seo-optimizer 是免费的吗?

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

seo-optimizer 用的人多吗?

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

seo-optimizer 安全吗?

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

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

值得选的地方

  • 同时适配 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-optimizer

SEO 优化器 · 本页

7591需要联网未明确有提醒

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

SKILL.md 原文

SEO Optimizer

Overview

Optimize websites for search engine visibility through technical SEO, on-page optimization, structured data implementation, and Core Web Vitals performance tuning. This skill covers crawlability, indexability, meta tag strategy, Schema.org markup, sitemap generation, canonical URL management, internationalization (hreflang), and performance optimization for Google's ranking signals.

Apply this skill whenever a site needs better organic search performance, whether for a single page audit or a full-site overhaul.

Multi-Phase Process

Phase 1: Technical Audit

  1. Crawl the site (Screaming Frog, Sitebulb, or custom script)
  2. Check robots.txt and XML sitemap validity
  3. Identify crawl errors, redirect chains, and broken links
  4. Verify canonical URLs and duplicate content handling
  5. Assess mobile-friendliness and responsive design
  6. Check HTTPS implementation and mixed content
  7. Evaluate page load performance (Core Web Vitals)
STOP — Do NOT proceed to Phase 2 until audit findings are documented and prioritized.

Phase 2: On-Page Optimization

  1. Audit title tags (unique, 50-60 chars, keyword placement)
  2. Review meta descriptions (unique, 150-160 chars, compelling CTAs)
  3. Analyze heading hierarchy (single H1, logical H2-H6 structure)
  4. Optimize image alt text and file names
  5. Review internal linking structure and anchor text
  6. Check URL structure (short, descriptive, hyphenated)
  7. Validate Open Graph and Twitter Card tags
STOP — Do NOT proceed to Phase 3 until on-page changes are implemented and verified.

Phase 3: Structured Data Implementation

  1. Identify applicable Schema.org types for content
  2. Implement JSON-LD structured data
  3. Validate with Google Rich Results Test
  4. Test for rich snippet eligibility
  5. Monitor Search Console for structured data errors
STOP — Do NOT proceed to Phase 4 until structured data passes validation.

Phase 4: Monitoring and Iteration

  1. Set up Google Search Console monitoring
  2. Track Core Web Vitals over time
  3. Monitor indexation status and coverage
  4. Review search performance (clicks, impressions, CTR, position)
  5. Set up alerts for crawl errors and ranking drops

Audit Priority Decision Table

FindingSeverityFix PriorityImpact
No HTTPS / mixed contentCriticalImmediateRanking penalty, trust signals
Missing canonical URLsCriticalImmediateDuplicate content dilution
Broken redirect chains (3+ hops)HighThis sprintCrawl budget waste, link equity loss
Missing or duplicate title tagsHighThis sprintCTR drop, ranking confusion
No structured dataMediumNext sprintMissing rich snippets
Missing alt text on imagesMediumNext sprintAccessibility and image search loss
Suboptimal Core Web VitalsMediumNext sprintRanking signal, user experience
Missing hreflang tags (multi-language)LowBacklogGeo-targeting issues
Non-descriptive URL slugsLowBacklogMinor ranking and CTR effect

Meta Tag Reference

Essential Meta Tags

<head>
  <!-- Primary -->
  <title>Primary Keyword - Secondary Keyword | Brand Name</title>
  <meta name="description" content="Compelling 150-160 char description with target keyword and clear value proposition.">
  <link rel="canonical" href="https://example.com/page">

  <!-- Robots -->
  <meta name="robots" content="index, follow">
  <!-- or noindex, nofollow for pages that shouldn't be indexed -->

  <!-- Viewport (mobile) -->
  <meta name="viewport" content="width=device-width, initial-scale=1">

  <!-- Open Graph -->
  <meta property="og:type" content="website">
  <meta property="og:title" content="Page Title for Social Sharing">
  <meta property="og:description" content="Description optimized for social sharing.">
  <meta property="og:image" content="https://example.com/og-image.jpg">
  <meta property="og:url" content="https://example.com/page">
  <meta property="og:site_name" content="Brand Name">

  <!-- Twitter Card -->
  <meta name="twitter:card" content="summary_large_image">
  <meta name="twitter:title" content="Page Title">
  <meta name="twitter:description" content="Twitter-optimized description.">
  <meta name="twitter:image" content="https://example.com/twitter-image.jpg">

  <!-- Internationalization -->
  <link rel="alternate" hreflang="en" href="https://example.com/en/page">
  <link rel="alternate" hreflang="de" href="https://example.com/de/page">
  <link rel="alternate" hreflang="x-default" href="https://example.com/page">
</head>

Meta Tag Optimization Matrix

ElementMax LengthPriority KeywordsCommon Mistakes
Title tag50-60 charsFront-load primary keywordToo long, keyword stuffing, duplicate
Meta description150-160 charsInclude CTA and keywordMissing, duplicate, no CTA
H1N/A (single per page)Primary keyword variationMultiple H1s, missing H1
URL slug3-5 wordsTarget keywordToo long, parameters, underscores
Image alt125 charsDescriptive, keyword if naturalEmpty, "image of...", keyword stuffing
OG title60-90 charsEngaging, shareableSame as title tag (missed opportunity)

Structured Data (JSON-LD)

Article

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to Optimize Core Web Vitals",
  "author": {
    "@type": "Person",
    "name": "Jane Smith",
    "url": "https://example.com/authors/jane-smith"
  },
  "datePublished": "2026-03-01",
  "dateModified": "2026-03-15",
  "image": "https://example.com/images/article-hero.jpg",
  "publisher": {
    "@type": "Organization",
    "name": "Example Blog",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.png"
    }
  },
  "description": "A comprehensive guide to improving LCP, FID, and CLS scores."
}
</script>

Product

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Widget Pro",
  "description": "Professional-grade widget for enterprise use.",
  "image": "https://example.com/widget-pro.jpg",
  "brand": { "@type": "Brand", "name": "WidgetCo" },
  "offers": {
    "@type": "Offer",
    "price": "49.99",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://example.com/widget-pro"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.7",
    "reviewCount": "312"
  }
}
</script>

FAQ Page

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is Core Web Vitals?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Core Web Vitals are a set of metrics that measure real-world user experience for loading, interactivity, and visual stability."
      }
    }
  ]
}
</script>

Schema Type Decision Guide

Content TypeSchema TypeRich Result
Blog postArticleArticle snippet
Product pageProductPrice, rating, availability
FAQ sectionFAQPageExpandable Q&A
How-to guideHowToStep-by-step snippet
RecipeRecipeImage, time, rating
EventEventDate, location, price
Local businessLocalBusinessMap pack, hours
SoftwareSoftwareApplicationRating, price
BreadcrumbsBreadcrumbListBreadcrumb trail
VideoVideoObjectThumbnail, duration

Core Web Vitals

Metrics and Thresholds

MetricGoodNeeds ImprovementPoorMeasures
LCP (Largest Contentful Paint)<= 2.5s<= 4.0s> 4.0sLoading performance
INP (Interaction to Next Paint)<= 200ms<= 500ms> 500msInteractivity
CLS (Cumulative Layout Shift)<= 0.1<= 0.25> 0.25Visual stability

LCP Optimization

<!-- Preload hero image -->
<link rel="preload" as="image" href="/hero.webp" fetchpriority="high">

<!-- Use modern image formats -->
<picture>
  <source srcset="/hero.avif" type="image/avif">
  <source srcset="/hero.webp" type="image/webp">
  <img src="/hero.jpg" alt="Hero description" width="1200" height="600"
       fetchpriority="high" decoding="async">
</picture>

CLS Prevention

/* Always set dimensions on images and video */
img, video {
  width: 100%;
  height: auto;
  aspect-ratio: 16 / 9;
}

/* Reserve space for dynamic content */
.ad-slot {
  min-height: 250px;
}

/* Avoid inserting content above existing content */
.notification-bar {
  position: fixed; /* doesn't shift layout */
}

INP Optimization

// Break long tasks with yield
async function processLargeDataset(data) {
  for (let i = 0; i < data.length; i++) {
    processItem(data[i]);
    if (i % 100 === 0) {
      await new Promise(resolve => setTimeout(resolve, 0)); // yield to main thread
    }
  }
}

// Use requestIdleCallback for non-critical work
requestIdleCallback(() => {
  loadAnalytics();
  initNonCriticalFeatures();
});

XML Sitemap

Generation Pattern

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://example.com/</loc>
    <lastmod>2026-03-15</lastmod>
    <changefreq>daily</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://example.com/products</loc>
    <lastmod>2026-03-14</lastmod>
    <changefreq>weekly</changefreq>
    <priority>0.8</priority>
  </url>
</urlset>

Sitemap Best Practices

  • Maximum 50,000 URLs per sitemap file
  • Use sitemap index for larger sites
  • Include only canonical, indexable URLs
  • Update lastmod only when content genuinely changes
  • Submit via Google Search Console and robots.txt

robots.txt Template

User-agent: *
Allow: /
Disallow: /admin/
Disallow: /api/
Disallow: /search?
Disallow: /*?sort=
Disallow: /*?filter=

Sitemap: https://example.com/sitemap.xml

Next.js / React SEO Patterns

Next.js Metadata API (App Router)

import type { Metadata } from 'next';

export const metadata: Metadata = {
  title: {
    template: '%s | Brand Name',
    default: 'Brand Name - Tagline',
  },
  description: 'Site-wide default description.',
  openGraph: {
    type: 'website',
    locale: 'en_US',
    url: 'https://example.com',
    siteName: 'Brand Name',
  },
  twitter: {
    card: 'summary_large_image',
  },
  robots: {
    index: true,
    follow: true,
  },
  alternates: {
    canonical: 'https://example.com',
  },
};

Dynamic Metadata per Page

export async function generateMetadata({ params }): Promise<Metadata> {
  const product = await getProduct(params.slug);

  return {
    title: product.name,
    description: product.description.slice(0, 160),
    openGraph: {
      title: product.name,
      description: product.description.slice(0, 200),
      images: [{ url: product.image, width: 1200, height: 630 }],
    },
  };
}

Anti-Patterns / Common Mistakes

Anti-PatternWhy It FailsWhat To Do Instead
Keyword stuffing in titles/contentTriggers spam filters, reduces CTRUse primary keyword once naturally, add variations
Same title/description across pagesDuplicate content signals, wasted opportunityUnique, page-specific meta for every indexable URL
Blocking CSS/JS in robots.txtGooglebot cannot render pagesAllow all rendering resources
Structured data mismatching page contentGoogle penalties, rich snippet removalSchema must reflect visible content exactly
Redirect chains > 2 hopsCrawl budget waste, link equity lossRedirect directly to final destination
JS-only navigation without SSR linksCrawler cannot discover pagesServer-render navigation links
Ignoring Core Web VitalsRanking signal degradationProfile and optimize LCP, INP, CLS
Missing canonical URLsDuplicate content penaltiesSet canonical on every indexable page
Over-optimized anchor textUnnatural link patterns trigger penaltiesUse descriptive, varied anchor text
Hiding content with CSS for SEOCloaking violationAll SEO content must be visible to users

Anti-Rationalization Guards

  • Do NOT skip the technical audit because "the site looks fine" -- crawl it.
  • Do NOT add structured data without validating it passes the Rich Results Test.
  • Do NOT assume meta tags are correct without checking every page type.
  • Do NOT deploy SEO changes without before/after measurement.
  • Do NOT optimize for search engines at the expense of user experience.

Integration Points

SkillHow It Connects
content-creatorSEO informs keyword targeting and headline strategy for marketing content
content-research-writerResearch-backed content needs SEO-optimized structure and meta tags
senior-frontendCore Web Vitals optimization requires frontend performance tuning
performance-optimizationPage speed directly affects LCP and INP scores
deploymentSEO changes need proper cache invalidation and redirect configuration
tech-docs-generatorDocumentation sites need sitemap, canonical, and structured data setup

Skill Type

FLEXIBLE — Adapt the optimization strategy to the site's technology stack, content type, and competitive landscape. Technical SEO fundamentals and structured data best practices are strongly recommended; specific implementation patterns vary by framework.

平台分布

Codex

32.11%
按下载量换算78

Claude

31.48%
按下载量换算76

Cursor

20.17%
按下载量换算49

Gemini CLI

8.33%
按下载量换算20

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills