Content Engine
PassAudited by ClawScan on May 1, 2026.
Overview
Content Engine is a coherent instruction-only content workflow, with disclosed but noteworthy use of persistent preferences and optional publishing through connected CMS tools.
Before installing, decide whether you are comfortable with an instruction-only workflow that can use web search, remember brand/CMS preferences, and optionally publish through connected CMS tools. Review content carefully before approving any live publication.
Findings (3)
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.