一键导入
seo-metadata-audit
Audit SEO metadata such as title, description, headings, alt, robots, canonical, schema, viewport, charset, and social tags.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Audit SEO metadata such as title, description, headings, alt, robots, canonical, schema, viewport, charset, and social tags.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Harness Engineering 第一阶段:扫描现有项目,生成 AGENTS.md(目录文件)和完整的 docs/ 知识库结构。 当用户想要"为项目添加 agent 支持"、"让 AI 更好地理解我的项目"、"开始 harness engineering"、 "创建 AGENTS.md"、"搭建 agent 文档结构"、"让 Claude Code 更好地工作"时,立即使用此 skill。 也适用于用户说"帮我把项目文档整理好给 agent 用"、"我想开始用 AI agent 开发"、 "梳理这个项目能解决什么业务问题"或要求建立 business-solution.md 等场景。
Harness Engineering 第一阶段第二步:深度分析项目代码,填充业务解决方案、架构、约定、技术决策和质量标准等 docs/ 知识库内容。 在 harness-step1-create-agents-md 创建好目录骨架之后使用。当用户说"填充文档内容"、 "完善 docs/ 文件"、"让文档有实质内容"、"分析项目写架构文档"、"写 ARCHITECTURE.md"、 "写技术决策文档"、"从业务视角理解项目"、"完善 business-solution.md"时,立即使用此 skill。 前置条件:项目中已有 AGENTS.md 和 docs/ 目录骨架(由 harness-step1 创建)。
Developer implementation guide for building hierarchical (folded) memory into an Agent. Three-layer architecture where recent turns stay detailed, older content compresses into episodes, and the oldest distills into durable semantic facts. Use when compact-memory-implementation is not retaining enough, or when agents need to recall decisions from many sessions ago.
Design and implement a layered, configurable permission/safety system for agent tools. Use this skill when building an agent that needs to control which tool calls are auto-allowed, which require user confirmation, and which are denied — especially when the system must be configurable across multiple scopes (project/user/enterprise) and extensible via hooks. Triggers on: "权限系统", "工具安全", "tool permission", "permission system", "tool safety", "allow/deny rules", "hook system", "构建安全机制".
Define agent tools using the fail-closed design pattern — unified name/schema/security/execution in one class, with three-layer execution (validate → permission → call). Use this skill whenever the user wants to define a new agent tool, add permission or validation logic to an existing tool, or asks about 'build a tool', '定义一个工具', 'create a tool for X', '工具定义'. Framework-agnostic: works with hermes-agent, LangChain, or any Python agent framework.
Build LangChain (Python) tools using Claude Code's fail-closed design pattern — unified name/schema/security/execution in one class, with automatic three-layer execution (validate → permission → call). Use this skill whenever the user wants to define a new LangChain tool, add permission or validation logic to an existing tool, set up the ClaudeStyleTool base class in a project, or asks about "build_tool", "Claude Code style tool", "工具定义", or "langchain tool with permissions". Also trigger when the user says "create a tool for X" or "定义一个工具" in a LangChain Python project context, even without mentioning Claude Code explicitly.
| name | seo-metadata-audit |
| description | Audit SEO metadata such as title, description, headings, alt, robots, canonical, schema, viewport, charset, and social tags. |
| license | Skill distillation for personal/educational use. Do not reproduce source passages verbatim. |
Knowledge source: 影响SEO最重要的10个metadata by 哥飞.
Use this skill to audit a webpage's most important SEO metadata and produce a prioritized repair plan. It supports SEO practitioners, developers, founders, and content teams who need to diagnose whether a page gives search engines clear, crawlable, canonical, mobile-friendly, and structured signals.
Use this skill when the user provides a URL, HTML, page spec, or metadata list and asks:
SEO metadata works as a system: each tag clarifies what the page is about, how search engines should process it, and how users see it in search or social contexts. Do not optimize one tag while breaking crawlability, canonicalization, mobile rendering, or semantic structure.
| Workflow | User question pattern | Inputs | Steps | Output | Independent trigger? | Distinct references? | Triage score | Should be subskill? | Reason |
|---|---|---|---|---|---|---|---|---|---|
| Full metadata audit | "Audit this page" | URL/HTML, target keyword, page purpose | Inspect all tag families; rank issues | Priority issue table | Yes | Yes | 3 | No | Primary workflow; all tags interact. |
| Snippet optimization | "Fix title/description" | Title, description, keyword, intent | Check length, uniqueness, click value | Rewrite variants | Yes | Yes | 3 | No | Narrow but uses same metadata scoring. |
| Crawl/index control | "Should this page be indexed?" | Page role, duplicates, robots/canonical | Decide index, follow, canonical | Indexing directive plan | Yes | Yes | 3 | No | Kept single-file because output rolls into audit plan. |
| Structured/social preview | "Add schema/Open Graph" | Page type, entity data, social preview | Choose schema and OG/Twitter tags | Markup checklist | Yes | Yes | 3 | No | Same input and repair report. |
Metadata tags can be checked independently, but mistakes often arise from interactions: canonical can override indexing intent, title affects snippet relevance, heading and schema affect semantic clarity, and viewport affects mobile rendering. A single audit skill keeps these dependencies visible.
The Rule: Title, description, and headings must communicate page topic and search intent clearly without keyword stuffing.
When the user shares HTML or metadata, audit snippet signals first because they determine both search understanding and user click behavior.
The Rule: Robots and canonical tags must tell search engines which URLs deserve indexing and authority consolidation.
For indexation questions, state the desired search-engine behavior first, then choose robots and canonical directives to match that behavior.
The Rule: Search engines and users need accessible images, mobile rendering, and correct character interpretation.
When auditing technical metadata, flag these as foundational issues even if they are not the user's original focus.
The Rule: Schema and social metadata help machines and platforms understand, classify, and preview the page.
Recommend schema and social tags only after identifying page type, entity, and user intent.
## SEO Metadata Audit
**Page:** ...
**Verdict:** Healthy / Needs fixes / Indexing risk / Snippet weak
| Tag / Signal | Status | Issue | Recommended Fix | Priority |
|---|---|---|---|---|
## Corrected Metadata
```html
...
## Critical Reminders
1. Title is important, but metadata is a system.
2. Description influences clicks even when it is not a direct ranking factor.
3. Canonical errors can erase good content from search visibility.
4. Do not block important pages accidentally.
5. Schema must describe real visible content.
## CITATION RULES
Every substantive metadata recommendation must include a citation to the source quote files.
**Quote files:**
- `seo-metadata-quotes.md` — strategy, title, description, H1, alt, nofollow, canonical, and canonical mistakes.
- `seo-technical-quotes.md` — technical tag details, robots, viewport, charset, Open Graph, and schema markup.
**Citation format:**
> "Author's exact words here."
>
> — [*影响SEO最重要的10个metadata*, cited excerpt](https://github.com/simbajigege/book2skills/blob/main/skills/seo-metadata-audit/quotes/FILENAME.md#ANCHOR)
**Anchor mapping:**
- `seo-metadata-quotes.md`: `#comprehensive-strategy`, `#title-importance`, `#title-keyword-ranking`, `#semantic-matching`, `#description-click-rate`, `#h1-essential`, `#alt-for-image-search`, `#nofollow-weight`, `#canonical-weight-aggregation`, `#canonical-mistake`
- `seo-technical-quotes.md`: `#comprehensive-seo-strategy`, `#title-length-importance`, `#title-brand-position`, `#description-length`, `#heading-hierarchy`, `#alt-description-best-practice`, `#nofollow-evolution`, `#robots-meta-control`, `#canonical-purpose`, `#viewport-mobile`, `#charset-encoding`, `#open-graph-social`, `#schema-markup`
**Rules:**
- Cite the closest tag-specific anchor for each major recommendation.
- If auditing a real page, distinguish observed defects from general best practice.
- Do not invent quote text; use exact quote files only.