Token导航 LogoToken导航

Agent Skill · 研究检索

seo-meta-tags(SEO meta tags 搜索)

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

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

总安装 238周安装 10GitHub Stars 12下载 83核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/jeremy0x/meta-tag-boilerplate --skill seo-meta-tags

这个 Skill 是做什么的

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

用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词快速定位候选结果。适用于 meta tags 相关研究、SEO 策略制定、信息收集和线索筛选等场景。通过关键词、任务场景或来源线索快速定位候选结果,可结合来源仓库继续核验具体用法。

安装命令:npx skills add https://github.com/jeremy0x/meta-tag-boilerplate --skill seo-meta-tags。建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

seo-meta-tags 怎么安装?

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

seo-meta-tags 支持哪些 AI 工具?

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

seo-meta-tags 需要什么权限?

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

seo-meta-tags 是免费的吗?

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

seo-meta-tags 用的人多吗?

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

seo-meta-tags 安全吗?

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

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

值得选的地方

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

SEO meta tags 搜索 · 本页

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

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

SKILL.md 原文

SEO Meta Tags

Boilerplate and component library for production-ready metadata across three framework targets.

Decision Tree

Determine the correct framework path first:

  1. Static HTML site or any-backend project — Read references/html.md
  2. Next.js 13+ App Router — Read references/nextjs.md
  3. Vite + React — Read references/vite.md, React section
  4. Vite + Vue 3 — Read references/vite.md, Vue section
  5. Multiple frameworks at once — Read all relevant reference files

Then determine action type:

  • Creating metadata from scratch? — Read matching reference → copy boilerplate → replace placeholders.
  • Updating existing metadata? — Load file → keep structure → change requested values → verify parity across tag families.
  • Auditing / reviewing metadata? — Run through Quality Gate below → report issues.
  • Migrating between frameworks? — Read source reference → read target reference → map fields.

Framework Selection

FrameworkWhen to useReference
HTMLStatic sites, any backend, SSGsreferences/html.md
Next.jsNext.js 13+ App Router projectsreferences/nextjs.md
ViteVite + React or Vite + Vue appsreferences/vite.md

Read only the reference file that matches the user's target framework.

Metadata Families

Every framework target must keep parity across these families. When modifying one family, verify the others remain consistent.

1. Essential / Primary

TagConstraint
<title> / titleUnder 60 characters
description150-160 characters
keywords5-10 terms max, comma-separated
authorFull name
robotsindex, follow by default; include max-image-preview:large, max-snippet:-1, max-video-preview:-1
canonicalAbsolute URL, must match deployment URL
viewportwidth=device-width, initial-scale=1.0

2. Open Graph (og:*)

PropertyNotes
og:typewebsite for home/landing; article for blog posts; product for e-commerce
og:urlAbsolute URL
og:titleCan differ from <title> for social context
og:descriptionCan differ from meta description
og:imageAbsolute URL, 1200x630px, JPG or PNG, under 1 MB
og:image:width / og:image:height1200 / 630
og:image:altRequired when image is present
og:site_nameBrand name
og:localee.g. en_US

For article type also include: article:published_time, article:modified_time, article:author, article:tag.

3. Twitter Cards (twitter:*)

PropertyNotes
twitter:cardsummary_large_image (default) or summary
twitter:siteOrganization handle with @ prefix
twitter:creatorAuthor handle with @ prefix
twitter:titleUnder 70 characters
twitter:descriptionUnder 200 characters
twitter:imageSame spec as OG image
twitter:image:altRequired when image is present

4. Theme Color

Provide three values:

  • Default: <meta name="theme-color" content="..."> or single value
  • Light: media="(prefers-color-scheme: light)"
  • Dark: media="(prefers-color-scheme: dark)"

Next.js uses the themeColor array in the Metadata object.

5. Icons and Manifest

AssetSizeFormat
favicon.ico32x32 or multi-sizeICO
icon-16x16.png16x16PNG
icon-32x32.png32x32PNG
apple-touch-icon.png180x180PNG
site.webmanifestn/aJSON

Generate with favicon.io or RealFaviconGenerator.

6. Structured Data (JSON-LD)

Emit a <script type="application/ld+json"> block (HTML/Vite) or use a separate Script component in Next.js. Required keys:

{
	"@context": "https://schema.org",
	"@type": "WebSite",
	"name": "",
	"description": "",
	"url": "",
	"image": { "@type": "ImageObject", "url": "", "width": 1200, "height": 630 },
	"author": { "@type": "Person", "name": "" },
	"publisher": {
		"@type": "Organization",
		"name": "",
		"logo": { "@type": "ImageObject", "url": "" }
	}
}

Common @type values: WebSite, Article, Organization, Product, FAQPage, BreadcrumbList.

7. Internationalization (hreflang)

<link rel="alternate" hreflang="en" href="https://example.com/en/" />
<link rel="alternate" hreflang="es" href="https://example.com/es/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/" />

Next.js equivalent: alternates.languages in the Metadata object.

8. Performance Hints

Include when external resources are used:

<link rel="preconnect" href="https://fonts.googleapis.com" />
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
<link rel="dns-prefetch" href="https://www.google-analytics.com" />

Placeholder Tokens

All boilerplate files use {{PLACEHOLDER_NAME}} tokens. Common tokens:

TokenPurpose
{{PAGE_TITLE}}Page <title>
{{PAGE_DESCRIPTION}}Meta description
{{PAGE_URL}}Page URL (absolute)
{{CANONICAL_URL}}Canonical URL
{{KEYWORDS}}Comma-separated keywords
{{AUTHOR_NAME}}Content author
{{SITE_NAME}}Brand / site name
{{THEME_COLOR}} / {{THEME_COLOR_LIGHT}} / {{THEME_COLOR_DARK}}Hex color codes
{{OG_TITLE}} / {{OG_DESCRIPTION}} / {{OG_IMAGE_URL}} / {{OG_IMAGE_ALT}}Open Graph
{{TWITTER_TITLE}} / {{TWITTER_DESCRIPTION}} / {{TWITTER_IMAGE_URL}} / {{TWITTER_IMAGE_ALT}}Twitter
{{TWITTER_HANDLE}} / {{TWITTER_CREATOR_HANDLE}}Twitter handles
{{SCHEMA_TYPE}} / {{SCHEMA_IMAGE_URL}}JSON-LD
{{PUBLISHER_NAME}} / {{PUBLISHER_LOGO_URL}}Publisher org
{{FAVICON_32x32_URL}} / {{FAVICON_16x16_URL}} / {{APPLE_TOUCH_ICON_URL}}Icons
{{AUTHOR_URL}}Author website URL (Next.js)
{{CREATOR_NAME}}Content creator name (Next.js)
{{CATEGORY}}Site category (Next.js)
{{GOOGLE_VERIFICATION_CODE}} / {{YANDEX_VERIFICATION_CODE}} / {{FACEBOOK_VERIFICATION_CODE}}Search engine verification codes (Next.js)
{{EN_URL}} / {{ES_URL}}Language-specific alternate URLs (Next.js)
{{ALTERNATE_EN_URL}} / {{ALTERNATE_DEFAULT_URL}}hreflang alternate URLs (HTML/Vite)

When implementing for a user, replace every {{...}} token. Never leave placeholders in production output.

Quality Gate

Run these checks before considering any metadata task complete:

  1. No placeholders — grep for {{ in all modified files; count must be zero.
  2. Absolute URLs — canonical, OG url, OG image, Twitter image, JSON-LD url/image must start with https://.
  3. Image alt text — every og:image / twitter:image must have a corresponding alt field.
  4. No duplicate tags — no two conflicting <title>, description, or canonical tags in the same scope.
  5. Title length — verify under 60 characters.
  6. Description length — verify 150-160 characters.
  7. JSON-LD validity — valid JSON with required @context and @type keys.
  8. OG/Twitter parity — if OG title is set, Twitter title should also be set (and vice versa).
  9. Canonical consistency — canonical URL matches the actual page URL or intended redirect target.
  10. Theme color — includes both light and dark media variants.
  11. hreflang — includes x-default when language alternates exist.
  12. Robots — allows indexing unless user explicitly requests noindex.

Image Specifications

Use caseDimensionsRatioFormatMax size
OG / Twitter1200x6301.91:1JPG or PNG1 MB
Favicon 3232x321:1PNGn/a
Favicon 1616x161:1PNGn/a
Apple Touch180x1801:1PNGn/a

Testing Tools

Recommend to users after deployment:

Common Mistakes

MistakeImpactFix
Relative URLs in og:image or twitter:imageSocial platforms can't fetch the imageAlways use absolute URLs starting with https://
Missing <HelmetProvider> in Vite ReactAll <SEO> tags silently fail to renderWrap app root in <HelmetProvider> in main.tsx
Missing createHead() in Vite VueuseHead() throws at runtimeCall app.use(createHead()) in main.ts
Committing verification codes to public reposExposes site ownership tokensUse environment variables for verification values
Duplicate <title> or description tagsCrawlers pick an unpredictable oneUse only one source of truth per scope (layout vs. page)
og:image set without og:image:altAccessibility failure, some validators warnAlways pair image with alt text
Using generateMetadata for static pagesUnnecessary async overhead on every requestUse static export const metadata when values are known at build time
Leaving {{...}} placeholder tokensBroken display on social platforms, poor SEOGrep for {{ before shipping
JSON-LD with trailing commas or commentsInvalid JSON, structured data ignoredValidate JSON before finishing
twitter:card set to summary when image is 1200x630Image gets cropped to tiny squareUse summary_large_image for landscape images

Migration Paths

FromToNotes
react-helmetVite React (SEO.tsx)Replace with react-helmet-async; wrap root in <HelmetProvider>
vue-metaVite Vue (SEO.vue)Replace metaInfo with @unhead/vue useHead() composable
next-seoNext.js (metadata.ts)Remove <NextSeo>; use exported metadata or generateMetadata
Pages Router <Head>App RouterReplace import Head with export const metadata

平台分布

Codex

35.62%
按下载量换算30

Claude

29.65%
按下载量换算25

Cursor

19.69%
按下载量换算16

Gemini CLI

9.37%
按下载量换算8

安全审计

Gen Agent Trust Hub

可疑

Socket

通过

Snyk

通过

权限和风险

接触敏感数据

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

安装前确认

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

继续浏览同类 Skills