OpenClaw Marketing OS
v3.238.0Run, audit, or improve an OpenClaw/ClawLite-style multi-agent marketing operating system. Use when the task is to operate or package a full marketing engine...
⭐ 0· 128·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description match the instructions: the SKILL.md describes a multi-agent marketing OS (roles, lanes, receipts, truth states) and all required behaviors (research → packaging → publishing → QA → state closure) align with that purpose. There are no unrelated dependencies or unexpected required credentials declared.
Instruction Scope
SKILL.md and reference docs define processes, role contracts, and evidence/receipt rules but do not instruct the agent to read unrelated system files, access secret env vars, or call arbitrary external endpoints. The guidance is operational and process-oriented rather than instructing intrusive data collection. Note: it presumes integration with external publishing channels (X, blogs, email), which is expected for this purpose.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, so nothing is written to disk or downloaded during installation.
Credentials
The skill declares no required environment variables or credentials, which is consistent with its instruction-only nature. However, practical use of the operating system will typically require separate credentials for publishing/email/blogging platforms; those credentials are not requested here. Users should ensure any integration code they pair with this operating model only requests the minimal, appropriate credentials.
Persistence & Privilege
always is false and there are no install actions or modifications to other skills or system-wide settings. The skill does not request permanent presence or elevated platform privileges.
Assessment
This skill is an operational playbook (no code, no installs, no declared secrets) and appears coherent with its marketing-OS purpose. Before using it in a live agent that will publish or send messages, note: 1) actual integrations (X, blog CMS, email providers) will need credentials — only grant those to trusted code and review any integration layer that will perform publishes or sends; 2) establish strict guardrails (approval steps, sandboxing, rate limits) before allowing autonomous publishing; 3) the skill emphasizes receipts/proofs — verify that any implementation actually performs live verification rather than relying on agent claims; and 4) if you open-source or share an implementation based on this, remove private data as the doc itself recommends. If you want a deeper review, provide any integration code or deployment manifests that will run alongside this instruction set.Like a lobster shell, security has layers — review code before you run it.
growthvk971794e0s89q6kyzaegyae51s83gr0klatestvk97ceyfjjkm7ezzqdh2q1az1bd83m5cmmarketingvk971794e0s89q6kyzaegyae51s83gr0kopenclawvk971794e0s89q6kyzaegyae51s83gr0kseovk971794e0s89q6kyzaegyae51s83gr0k
License
MIT-0
Free to use, modify, and redistribute. No attribution required.