Skillv1.1.0

ClawScan security

Content Monetizer · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

BenignMar 16, 2026, 6:49 AM

Verdict: benign
Confidence: high
Model: gpt-5-mini
Summary: Instruction-only content monetization helper that is internally consistent with its description — it requests no credentials, installs nothing, and its instructions stay within expected scope.
Guidance: This skill is an instruction-only helper and appears coherent with its purpose. Before using it: (1) don't pass highly sensitive files (the agent will read any content files you provide); (2) review and, if desired, edit ~/.openclaw/config/content-monetizer.json to set platform weights to your comfort; (3) be aware the agent may send content to whatever LLM or analysis back-end your OpenClaw agent is configured to use — if you need strict privacy, run analysis locally or avoid uploading private content. If you plan to combine it with other skills (e.g., content-creator-cn), review those skills' permissions as well.

Purpose & Capability: okName/description (content monetization) match the instructions and examples. Required resources are minimal (none) and the single config path (~/.openclaw/config/content-monetizer.json) is coherent for user-configurable platform weights.
Instruction Scope: okSKILL.md contains only content-analysis and recommendation workflows (examples call analyze/distribute/compare on user content files). It does not instruct reading unrelated system files, accessing secrets, or sending data to unexpected external endpoints.
Install Mechanism: okNo install spec and no code files — lowest-risk instruction-only skill. Nothing will be downloaded or written by an installer.
Credentials: okNo environment variables, credentials, or external tokens are requested. The only persistent data is an optional config file under ~/.openclaw, which is appropriate for user preferences.
Persistence & Privilege: okalways is false and the skill does not request elevated or cross-skill configuration changes. Storing user preferences in its own OpenClaw config path is reasonable.