sumulige-claude: Skill for Claude Code

.claude/skills/seo-optimization/SKILL.md

seo-optimization is a skill for Claude Code from sumulige/sumulige-claude. It costs 15 tokens per session (1,246 once invoked), scanned A, original, MIT.

A set of search-engine optimisation guidelines for Git history, project documentation, release notes, and web pages. It covers how to write clearer, more searchable commit messages and page content.

In plain words
What is it for?
Use it when writing commits, publishing releases, creating or updating README files, or building web pages and landing pages.
Why use it?
It helps avoid vague commit messages, release notes, and documentation that are harder for people and search engines to find or understand.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is sumulige/sumulige-claude's own configuration. It tells Claude Code how to work on sumulige-claude itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything sumulige-claude configures →

Reuse

Borrowing it

Nothing to install: this file belongs to sumulige/sumulige-claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/sumulige/sumulige-claude/main/.claude/skills/seo-optimization/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/sumulige/sumulige-claude

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for seo-optimization

README.md
[![agentmods](https://agentmods.dev/badge/skills/sumulige/sumulige-claude/seo-optimization.svg)](https://agentmods.dev/skills/sumulige/sumulige-claude/seo-optimization)
Your own site
<a href="https://agentmods.dev/skills/sumulige/sumulige-claude/seo-optimization"><img src="https://agentmods.dev/badge/skills/sumulige/sumulige-claude/seo-optimization.svg" alt="Measured on agentmods" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,246 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00015 $0.01246
Opus 5 $0.00008 $0.00623
Sonnet 5 $0.00003 $0.00249
Haiku 4.5 $0.00002 $0.00125

Measured 6d ago against content hash 607eb2d0bd68, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

seo-optimization scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/seo-optimization/SKILL.md · 216 lines

How it starts

The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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 新功能 高 - 功能搜索
fix Bug 修复 高 - 问题搜索
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            ← 许可搜索

Read the full file on GitHub · 216 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 216 lines · 15 tokens per session scan A 607eb2d0bd68

Subscribe to this mod's changes

seo-optimization is a skill published in the GitHub repository sumulige/sumulige-claude (2 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 1,246 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

codex-build

Orchestrate Codex to BUILD code in the background while this Claude Code session (typically Opus) plans and reviews — never babysitting. The session composes the implementation plan, kicks the dev-review runner detached via a background Bash task with --preset codex-build, ENDS ITS TURN, and is woken on exit to run a…

alanshurafa/co-evolution · 181 tokens

co-evolution

General-purpose co-evolution for questions, ideas, drafts, plans, specs, arguments, and markdown documents. Composes or bounces content between agents using [CONTESTED]/[CLARIFY] markers until it converges. Triggers on "co-evolution", "co-evolve", "co evolve", "bounce", "bounce document", "agent bouncer", "refine with…

alanshurafa/co-evolution · 118 tokens

recursive-task-optimizer

Build, configure, run, inspect, or troubleshoot agent-agnostic recursive improvement loops for a repository or artifact. Use when a task should be attempted repeatedly by Claude Code, Codex CLI, Hermes, or another CLI agent; when candidates must inherit mutable task instructions, a self-improving meta-procedure, and…

laruss/recursive-task-optimizer · 101 tokens

dev-review

Code-focused plan-bounce-execute workflow between Claude Code (Opus) and Codex CLI. Use when the user wants repo files changed, a bug fixed, a feature implemented, or a code plan verified before execution. One AI composes a plan, it bounces between agents with [CONTESTED]/[CLARIFY] markers until refined, then the…

alanshurafa/co-evolution · 176 tokens

cao-workflow

Author and run CAO Python workflow scripts — multi-step, parameterized, fan-out orchestrations executed by cao workflow run. Use when the user wants a repeatable multi-step job (e.g. data analysis over many files, a review pipeline, a parameterized batch). Authoring ends at a validated script file; running it is a…

awslabs/cli-agent-orchestrator · 79 tokens

aidlc-portfolio

Coordinate multiple AI-DLC workflows across repositories and Git worktrees using an evidence-backed portfolio catalog and deterministic workspace tooling. Use when initializing an AI-DLC portfolio workspace, discovering organization or business context, registering projects and dependencies, creating child intents and…

awslabs/cli-agent-orchestrator · 74 tokens