agentleFS
sumuligesumulige/sumulige-claude/.claude/skills/seo-optimization/SKILL.md

seo-optimization

Skill2 starsChanged 10 months agoMITView on GitHub

SEO best practices for Git, documentation, and web projects

  • Installs packages

8 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use analytics and code-review.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    analytics

    Also in 3 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 3 projects that use this

The file

Files
SKILL.md

SEO Optimization

搜索引擎优化最佳实践 - Git、文档、Web 全覆盖

触发场景

场景触发时机
Commit写提交信息时
Release发布新版本时
README创建/更新 README 时
Web创建网页/Landing Page 时

1. Git Commit SEO

Conventional Commits 格式

<type>(<scope>): <subject>

<body>

<footer>

Type 关键词(提升可搜索性)

Type用途SEO 价值
feat新功能高 - 功能搜索
fixBug 修复高 - 问题搜索
docs文档中 - 文档搜索
perf性能优化中 - 性能搜索
refactor重构低
chore杂项低

Subject 最佳实践

✅ feat: add user authentication with OAuth2
✅ fix: resolve memory leak in WebSocket connection
✅ docs: add API reference for payment module

❌ feat: add feature
❌ fix: fix bug
❌ update code

规则:

  • 动词开头(add, fix, update, remove, implement)
  • 50 字符内
  • 包含核心关键词
  • 不用句号结尾

2. GitHub Release SEO

标题格式

v{version} - {简短描述}

示例:
v1.10.0 - Multi-Platform Support (8 → 10 AI CLIs)
v2.0.0 - Complete Architecture Rewrite

Release Notes 结构

## Highlights

{1-2 句话总结最重要的变化}

## What's New

### Features
- **{功能名}**: {描述} (#PR)

### Bug Fixes
- Fix {问题描述} (#PR)

### Breaking Changes
- {破坏性变更说明}

## Statistics
- Files changed: X
- Lines added: +Y
- Lines removed: -Z

## Installation

\`\`\`bash
npm install package@version
\`\`\`

3. README SEO

首段优化(最重要)

# {项目名}

**{项目名}** is {英文一句话描述}. {核心价值}.

Supports **{平台数}** including {平台列表}.
Features {特性1}, {特性2}, and {特性3}.

关键点:

  • 首段必须包含项目名 2-3 次
  • 包含核心关键词
  • 150-200 字符内
  • 被 GitHub 和搜索引擎索引

Badge 优化

[![npm version](https://img.shields.io/npm/v/{pkg}.svg)](https://npmjs.com/package/{pkg})
[![License](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
[![Platform](https://img.shields.io/badge/platforms-{N}%20supported-blue.svg)](#platforms)

H2 标题关键词

## Quick Start        ← 安装搜索
## Features           ← 功能搜索
## Installation       ← 安装搜索
## Usage              ← 使用搜索
## API Reference      ← API 搜索
## Contributing       ← 贡献搜索
## License            ← 许可搜索

4. Technical SEO (Web)

Meta Tags 检查清单

<!-- 必须 -->
<title>{项目} - {核心价值} | {品牌}</title>
<meta name="description" content="{150字描述}">

<!-- Open Graph -->
<meta property="og:title" content="{标题}">
<meta property="og:description" content="{描述}">
<meta property="og:image" content="{预览图 1200x630}">
<meta property="og:url" content="{URL}">

<!-- Twitter Card -->
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="{标题}">
<meta name="twitter:description" content="{描述}">
<meta name="twitter:image" content="{预览图}">

结构化数据 (JSON-LD)

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "{项目名}",
  "description": "{描述}",
  "applicationCategory": "DeveloperApplication",
  "operatingSystem": "Any",
  "offers": {
    "@type": "Offer",
    "price": "0",
    "priceCurrency": "USD"
  }
}
</script>

5. SEO 检查清单

发布前检查

  • Commit message 使用 conventional commits
  • CHANGELOG 包含当前版本
  • README 首段包含项目名和关键词
  • Release notes 有清晰的分类
  • 版本号遵循 semver

文档检查

  • 标题使用 H1-H6 层级
  • 首段包含核心关键词
  • 有明确的行动号召(Quick Start)
  • Badge 链接正确

Web 检查

  • title 50-60 字符
  • description 150-160 字符
  • Open Graph 图片 1200x630
  • 移动端友好

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.