OrgX Marketing Agent
v1.0.0OrgX marketing execution contract for OpenClaw. Use for launch assets, positioning, content packs, and channel-specific copy with measurement hooks.
⭐ 0· 49·0 current·0 all-time
byHope Atina@hopeatina
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description (marketing execution, launch assets, channel copy) align with the SKILL.md content. The skill declares no binaries, no env vars, and no installs — which is proportionate for a pure instruction/persona contract.
Instruction Scope
The SKILL.md contains sensible marketing deliverable requirements and a short reporting protocol (orgx_emit_activity, orgx_request_decision, orgx_apply_changeset). These are reasonable for an execution contract, but the instructions give the agent autonomy to 'pick the channel and ship channel-ready drafts' and to use apply_changeset when mutation tools are exposed. That is intentionally vague about when and how external posting/mutations occur; you should confirm how those orgx_* hooks are implemented by the runtime/platform.
Install Mechanism
No install mechanism or code files are present (instruction-only). This is low-risk from a file/installation perspective.
Credentials
The skill requests no environment variables, credentials, or config paths, which is proportionate for a marketing persona/instructions-only skill. Note: the SKILL.md references platform hooks (orgx_*); any credentials or external connectors would come from the runtime, not this skill.
Persistence & Privilege
always:false and user-invocable:true. The skill does not request persistent presence or special system privileges. It allows agent autonomy in its text, but that is an instruction-level behavior rather than a request for elevated platform privileges.
Assessment
This skill is instruction-only and doesn't request secrets or install code, which is good. Before enabling it for autonomous runs, verify what the runtime/platform implements for the orgx_emit_activity, orgx_request_decision, and orgx_apply_changeset hooks: specifically, can apply_changeset or the runtime post directly to social channels or change live content without human approval? If so, require explicit human approval for external posting or limit the skill to drafting-only. Also consider who published the skill (source/homepage unknown); if you rely on it in production, validate outputs in a safe environment and confirm the owner or provenance.Like a lobster shell, security has layers — review code before you run it.
latestvk9760c7ypx65z6fv6zn824dycx83sm7n
License
MIT-0
Free to use, modify, and redistribute. No attribution required.