Autonomous content creation engine for agents. Writes platform-native posts, threads, newsletters, and long-form articles that meet the highest standards of...
Security Analysis
high confidenceContent Creator Pro is internally coherent: it creates, tracks, and audits content in the workspace and does not request external credentials or perform network I/O.
The name/description (autonomous content authoring + performance tracking) matches the included files and code: SKILL.md, editorial references, calendar/performance JSONs, hooks.md, and content_tracker.py implement writing, tracking, and hook validation. Declared required_paths align with the files the skill reads/writes (voice.md, calendar.json, performance.json, hooks.md, queue/library, AUDIT.md, ERRORS.md).
Runtime instructions and metadata limit the skill to filesystem operations under /workspace (read/write of voice/calendar/performance/hooks, writing queue and library, audit/errors). The code (content_tracker.py) only reads/writes JSON/markdown in those paths and does not perform network calls or access unrelated system paths or environment variables.
No install spec is present (instruction-only with a helper Python script). There are no downloads, external package installs, or extracted archives; risk from installation is minimal.
The skill does not request environment variables, credentials, or external tokens. The files it touches are consistent with content creation/tracking; there are no unexplained secrets or unrelated service credentials required.
The skill is not always-on (always:false) and is user-invocable. The agent-default ability to invoke skills autonomously remains (disable-model-invocation:false), which is normal — but because this skill writes ready-to-publish content into /workspace/content/queue/, you should confirm whether acquisition-master (or other publishing skills) will publish automatically or require human review.
Guidance
This skill appears to do exactly what it says: create, store, and analyze content inside the agent's workspace without network calls or credential access. Before installing, confirm two practical things: (1) ensure no sensitive secrets (API keys, private data) are stored anywhere under /workspace, because the skill will read/write files there (library/, performance.json, hooks.md, AUDIT.md, ERRORS.md); (2) verify your publishing pipeline (acquisition-master or other skills) has an explicit review/approval step if you don't want posts published automatically when the content-queue is populated. If you want extra safety, run the skill in a sandboxed workspace copy first to observe its outputs and logs (AUDIT.md / .learnings/ERRORS.md) before enabling it in production.
Latest Release
v1.0.7
Version 1.0.7 - Added hooks.md file to the project. - Updated required file paths in metadata to include /workspace/content/hooks.md for both reading and writing. - No other structural or behavior changes.
More by @georges91560
Published by @georges91560 on ClawHub
