Content Creator
v2.1.1Deprecated redirect skill that routes legacy 'content creator' requests to the correct specialist. Use when a user invokes 'content creator', asks to write a...
⭐ 11· 4.9k·47 current·47 all-time
byAlireza Rezvani@alirezarezvani
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description say this is a redirect to specialist skills; the skill requests no binaries, env vars, installs, or files that would be necessary for doing writing/SEO/strategy itself. The included docs and templates are consistent with a helper/redirect artifact. Note: examples refer to scripts (brand_voice_analyzer.py, seo_optimizer.py) but those are described as part of the successor skill (content-production), not this redirect — that is coherent.
Instruction Scope
SKILL.md explicitly instructs the agent to route requests rather than handle them. The runtime instructions do not direct the agent to read system files, environment variables, or call external endpoints. The repository contains only static markdown templates, examples, and references; there are no runtime commands embedded in the skill that would expand its scope.
Install Mechanism
No install spec and no code files — instruction-only. Nothing is downloaded or written to disk by this skill, so install risk is minimal.
Credentials
The skill declares no required env vars, no credentials, and no config paths. That aligns with a passive redirect/helper role and is proportionate to its stated purpose.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request elevated/persistent privileges or modify other skills' configuration. Autonomous invocation is permitted by platform default but this skill's behavior (routing) is low-risk and consistent with that model.
Assessment
This skill is a lightweight, deprecated redirect that only maps legacy 'content creator' requests to two specialist skills (content-production and content-strategy). It contains only documentation and templates and does not request credentials or install code. Before relying on it, consider: (1) prefer installing/using the successor skills (content-production/content-strategy) if you need real functionality — those may require environment variables or install steps; (2) the examples reference scripts that are not included here (they live in the successor), so expect the actual tooling to be in those other skills; (3) because this skill is deprecated, consider removing it and invoking the appropriate specialist directly to avoid an unnecessary indirection.Like a lobster shell, security has layers — review code before you run it.
latestvk975b4w6y1zc0cjg4jfh46qhmd82j0hw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.