content-optimization

v1.2.1

When the user wants to optimize content for SEO—word count, H2 keywords, keyword density, multimedia, tables, lists. Also use when the user mentions "content...

0· 95·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (SEO content optimization) match the SKILL.md contents. The guidance (word count, H2 keyword placement, multimedia, tables, lists) aligns with the stated purpose and does not request unrelated resources or credentials.
Instruction Scope
Instructions are mostly in-scope. The skill explicitly tells the agent to read project context files (.claude/project-context.md or .cursor/project-context.md) if present — this is reasonable for tailoring SEO advice but is access to user-local files and therefore privacy-sensitive. The skill references other internal skills (competitor-research, article-content, featured-snippet) but does not itself instruct any external network calls or unexpected data exfiltration.
Install Mechanism
No install spec and no code files — instruction-only. This is low-risk: nothing will be downloaded or written to disk by an installer.
Credentials
Requires no environment variables, no credentials, and no config paths beyond the optional project-context files mentioned in the instructions. The requested access is proportional to an SEO/content task.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request permanent/system-wide privileges or changes to other skills. Autonomous invocation is allowed by default but not combined with other high-risk factors here.
Assessment
This skill appears to be what it says: an instruction-only SEO/content optimizer that asks no credentials and installs nothing. Before installing, note that it instructs the agent to read optional local project context files (.claude/project-context.md or .cursor/project-context.md) to tailor recommendations — if those files contain sensitive information, review or remove that content first. Also be aware it references other skills (competitor-research, article-content, etc.); those other skills (if present and invoked) could have their own scopes or requirements, so review them too. If you want stricter privacy, disable autonomous invocation or avoid storing sensitive data in the referenced project-context files.

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

latestvk972av23696ep66ts7ctab252x846yaa

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments