Token导航 LogoToken导航TokenDH.com
前端设计需要联网github未标认证来源可访问clear审计通过

seo-optimizationSEO optimization 前端

Agent Skill

用于辅助前端页面、组件、样式和交互逻辑的开发与维护。它适合让 Agent 生成或审查 React、Next.js、Vue、Tailwind、CSS 等相关代码,整理组件结构,或定位布局和性能问题。使用时需要结合项目现有设计系统、路由和构建方式,避免只生成孤立片段;涉及页面改动时,应配合本地预览和构建检查确认视觉效果。

总安装

272

周安装

11

GitHub Stars

公开资料未说明

下载量

85
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/vapvarun/claude-backup --skill seo-optimization

简介

用于辅助前端页面开发与维护,支持 React、Next.js 等框架。

  • 适合生成或审查组件、样式及交互逻辑代码。
  • 通过 npx 命令从 GitHub 仓库安装并使用。
  • 使用时需结合项目现有技术栈,避免孤立输出;涉及页面改动时应配合本地预览验证效果。
  • seo-optimization 属于前端设计类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

SEO Optimization Skill

Instructions

When optimizing for SEO:

1. On-Page SEO

Title Tags:

  • 50-60 characters max
  • Primary keyword near the beginning
  • Include brand name at end
  • Make it compelling and clickable
<title>Primary Keyword - Secondary Keyword | Brand Name</title>

Meta Descriptions:

  • 150-160 characters
  • Include primary keyword
  • Call-to-action
  • Unique for each page
<meta name="description" content="Compelling description with keyword that encourages clicks. Learn more about X today!">

Heading Structure:

<h1>One H1 per page with primary keyword</h1>
<h2>Section headings with secondary keywords</h2>
<h3>Subsections for organization</h3>

2. Technical SEO

Essential Meta Tags:

<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="robots" content="index, follow">
<link rel="canonical" href="https://example.com/page/">

Open Graph (Social Sharing):

<meta property="og:title" content="Page Title">
<meta property="og:description" content="Description">
<meta property="og:image" content="https://example.com/image.jpg">
<meta property="og:url" content="https://example.com/page/">
<meta property="og:type" content="website">

Twitter Cards:

<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Page Title">
<meta name="twitter:description" content="Description">
<meta name="twitter:image" content="https://example.com/image.jpg">

3. Schema Markup (JSON-LD)

Organization:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Company Name",
  "url": "https://example.com",
  "logo": "https://example.com/logo.png",
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+1-xxx-xxx-xxxx",
    "contactType": "customer service"
  },
  "sameAs": [
    "https://facebook.com/company",
    "https://twitter.com/company"
  ]
}

Product:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Product Name",
  "image": "https://example.com/product.jpg",
  "description": "Product description",
  "brand": {"@type": "Brand", "name": "Brand"},
  "offers": {
    "@type": "Offer",
    "price": "49.99",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.8",
    "reviewCount": "124"
  }
}

Article/Blog Post:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Article Title",
  "author": {"@type": "Person", "name": "Author Name"},
  "datePublished": "2025-01-15",
  "dateModified": "2025-01-20",
  "image": "https://example.com/article-image.jpg"
}

FAQ:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Question text?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Answer text."
    }
  }]
}

4. Core Web Vitals

LCP (Largest Contentful Paint) < 2.5s:

  • Optimize images (WebP, lazy loading)
  • Preload critical assets
  • Use CDN

FID (First Input Delay) < 100ms:

  • Minimize JavaScript
  • Break up long tasks
  • Use web workers

CLS (Cumulative Layout Shift) < 0.1:

  • Set image dimensions
  • Reserve space for ads/embeds
  • Avoid inserting content above existing content

5. Image SEO

<img
  src="image.webp"
  alt="Descriptive alt text with keyword"
  width="800"
  height="600"
  loading="lazy"
  decoding="async"
>

6. URL Structure

Good:

  • example.com/category/product-name
  • example.com/blog/how-to-do-something

Avoid:

  • example.com/p?id=123
  • example.com/category/sub/sub/page

7. Internal Linking

  • Use descriptive anchor text
  • Link to related content
  • Create topic clusters
  • Maintain reasonable link depth (3 clicks max)

8. SEO Checklist

  • Unique title tag with keyword
  • Meta description with CTA
  • One H1 with primary keyword
  • Schema markup implemented
  • Images optimized with alt text
  • Internal links added
  • Mobile-friendly
  • Page speed optimized
  • Canonical URL set
  • XML sitemap updated

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

29.14%
按下载量换算25

Gemini CLI

21.41%
按下载量换算18

windsurf

15.81%
按下载量换算13

Codex

12.88%
按下载量换算11

Antigravity

8.08%
按下载量换算7

OpenCode

3.46%
按下载量换算3

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

继续浏览同类 Skills