ClawHub

title-tag

v1.4.0

When the user wants to optimize the title tag, page title, or SERP title. Also use when the user mentions "title tag," "meta title," "page title," "SEO title...

⭐ 0· 26·0 current·0 all-time
by@kostja94
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (title tag optimization) align with the SKILL.md content. The skill is instruction-only, requires no binaries, env vars, or installs — consistent with a text-guidance SEO helper.
ℹ
Instruction Scope
Instructions are focused on title-tag guidance and best practices. They do instruct the agent to read project context files if present (.claude/project-context.md or .cursor/project-context.md) to gather brand voice and keywords — this is reasonable for SEO work but means the skill will access repository/project files when available. The SKILL.md mentions Google Search Console and pixel checkers but does not include steps that require network credentials or external endpoints.
✓
Install Mechanism
No install spec and no code files; the skill is instruction-only so nothing is written to disk or downloaded. Low install risk.
✓
Credentials
The skill requests no environment variables, secrets, or credentials. There are no disproportionate credential requirements for the stated functionality.
✓
Persistence & Privilege
always is false and the skill does not request system-wide changes or persistent installation. It does not modify other skills or agent configs per the provided metadata.
Assessment
This is an instruction-only SEO helper and appears coherent with its purpose. It may read project context files (.claude/project-context.md or .cursor/project-context.md) if they exist to adapt voice/keywords — review those files for any sensitive content you don't want the agent to access. The skill references Google Search Console for CTR-driven optimizations but does not itself request GSC credentials; only provide external API keys or console access if you explicitly connect a separate GSC integration. Overall this skill is low-risk, but as with any assistant extension, avoid placing secrets in project-context files the skill may read.

Like a lobster shell, security has layers — review code before you run it.

latestvk975de5zame7zph8ad9vx53gt1848wz7

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments