heading-structure
v1.0.1When the user wants to optimize heading structure (H1-H6), fix heading hierarchy, or improve content structure. Also use when the user mentions "H1," "headin...
⭐ 0· 58·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & 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.
Assessment
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.Like a lobster shell, security has layers — review code before you run it.
latestvk9780tc2bm620qwnbybzg0wjms8493fq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.