← 返回 Skills 市场

heading-structure

Name: heading-structure
Author: kostja94

作者 Kostja Zhang · GitHub ↗ · v1.0.1 · MIT-0

cross-platform ✓ 安全检测通过

143

总下载

当前安装

版本数

在 OpenClaw 中安装

/install heading-structure

功能描述

When the user wants to optimize heading structure (H1-H6), fix heading hierarchy, or improve content structure. Also use when the user mentions "H1," "headin...

使用说明 (SKILL.md)

SEO On-Page: Heading Structure

Guides heading (H1-H6) optimization for SEO and content structure.

When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Scope (On-Page SEO)

H1 tag: One per page; clear headline; matches content; primary keyword near start
Header tags (H1-H6): Logical hierarchy; keyword in headers; one idea per heading

Initial Assessment

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for target keywords.

Identify:

Page type: Homepage, article, product, etc.
Primary keyword: Target search query
Content outline: Main sections and subsections

Best Practices

H1

Principle	Guideline
One per page	Single H1 per page
Primary keyword	Include target keyword naturally
Descriptive	Clearly describe page content
Match intent	Align with title tag and user intent

H2-H6 Hierarchy

Principle	Guideline
Logical order	H1 -> H2 -> H3; don't skip levels
One idea per heading	Each heading = one topic
Scannable	Headings should summarize section content
Keyword variation	Use related keywords in subheadings

Structure

H1 (page title)
-> H2 (section 1)
   -> H3 (subsection)
   -> H3
-> H2 (section 2)
   -> H3
-> H2 (section 3)

Common Issues

Issue	Fix
Multiple H1s	Use single H1; use H2 for other sections
Skipped levels	Use H2 after H1, H3 after H2
Generic headings	Make descriptive; avoid "Introduction," "Conclusion"
Keyword stuffing	Natural language; avoid forced keywords

Output Format

H1 recommendation (with keyword)
H2-H6 outline for content
Hierarchy check
References: Google headings

Related Skills

featured-snippet: H2/H3 for snippet extraction; semantic HTML for list/table snippets
page-metadata: Hreflang, meta robots; metadata complements heading structure
content-optimization: H2 keyword placement, quantity, tables, lists; complements heading structure
article-page-generator: Article page H1-H3 structure, intro/body/conclusion
title-tag: H1 should align with title tag
schema-markup: Article schema uses headline (often H1)
content-strategy: Content outline informs headings

安全使用建议

This skill appears safe and coherent for SEO heading guidance. Before installing, note that it will read project-context files (.claude/project-context.md or .cursor/project-context.md) if they exist — verify those files don't contain sensitive secrets you wouldn't want read. No external installs, credentials, or network calls are required. As with any skill, review sample outputs before using recommendations verbatim, and remove or redact any sensitive workspace files if you don't want them used for context.

功能分析

Type: OpenClaw Skill Name: heading-structure Version: 1.0.1 The skill bundle provides standard SEO guidelines for optimizing heading structures (H1-H6). The instructions in SKILL.md are purely functional, directing the agent to analyze content hierarchy and check local project context files for keyword relevance. No malicious code, data exfiltration, or harmful prompt injection attempts were found.

能力评估

✓ Purpose & Capability

Name, description, and the runtime instructions all focus on optimizing heading hierarchy and content structure for on‑page SEO. There are no unrelated requirements (no binaries, env vars, or external services), so requested capabilities match the stated purpose.

ℹ Instruction Scope

Instructions are narrowly scoped to analyzing heading usage and producing recommendations. They explicitly ask the agent to read local context files (.claude/project-context.md or .cursor/project-context.md) if present to extract target keywords — this is reasonable for a content/SEO skill but does mean the skill will access workspace files when available. No instructions to call external endpoints, run shell commands, or exfiltrate data are present.

✓ Install Mechanism

No install spec and no code files are present (instruction-only). This minimizes filesystem and execution risk.

✓ Credentials

The skill declares no environment variables, credentials, or config paths beyond the optional local project-context files. The requested access is proportional to an SEO/content-helping skill.

✓ Persistence & Privilege

always is false and the skill does not request persistent or cross-skill configuration changes. Autonomous invocation is enabled (the platform default) but not combined with any broad credentials or elevated privileges.

如何使用

确保已安装 OpenClaw（本地或 Docker 部署）
在对话框中输入安装命令：/install heading-structure
安装完成后，直接呼叫该 Skill 的名称或使用 /heading-structure 触发
根据 Skill 的参数说明提供必要输入，即可获得结构化输出

版本历史

v1.0.1

Automated batch sync

v1.0.0

Automated batch sync

元数据

Slug heading-structure

版本 1.0.1

许可证 MIT-0

累计安装 0

当前安装数 0

历史版本数 2

常见问题