Content Engine
PassAudited by VirusTotal on May 12, 2026.
Overview
Type: OpenClaw Skill Name: content-engine Version: 1.0.0 The skill bundle is designed for a full-stack content creation pipeline, involving web research, content generation, SEO optimization, CMS formatting, and social media promotion. All instructions within `SKILL.md` are directly aligned with this stated purpose. It utilizes standard agent capabilities such as `web_search`, storing data in OpenClaw memory, saving files to the workspace, and interacting with other skills (e.g., WordPress, Notion, Mixpost). While capabilities like 'offer to publish directly' are powerful, they are core to the skill's function and do not show evidence of intentional harmful behavior, unauthorized data access, exfiltration, or prompt injection against the agent itself. The skill's instructions are conditional and task-oriented, lacking any indicators of malice or exploitation attempts.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If the user approves publishing, mistakes or unwanted content could be posted to a live site.
Direct CMS publication can affect public-facing content, but the artifact frames it as an offered action rather than an automatic default.
Publish or save: if CMS integration is available, offer to publish directly. Otherwise, save the final file and tell the user where it is.
Review the final draft, metadata, target site, and publication status before approving any direct publish action.
The skill may use already-connected CMS account authority to create or publish content.
Using connected WordPress or Notion integrations may rely on delegated account permissions, even though no credentials are declared or embedded in this skill.
WordPress: use WordPress skill if available ... Notion: create a Notion page via Notion skill if available
Confirm which CMS account is connected and ensure its permissions are limited to the sites or workspaces where you want content created.
Stored brand or style preferences may persist across future writing tasks and could affect later content if outdated or incorrect.
The skill intentionally reads and writes persistent memory so brand preferences can influence later outputs.
look in OpenClaw memory for stored brand guidelines, tone preferences, or writing style notes. If none exist, ask the user on first run and store for future use.
Store only non-sensitive brand guidance, and review or update saved preferences when your style or CMS setup changes.