Marketing Agency Operations
v1.0.0Operations system for small marketing agencies (2-20 person shops). Client reporting automation, campaign performance summaries, proposal drafting, deadline...
⭐ 0· 20·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description match the SKILL.md tasks (reporting, campaign tracking, proposals, billing reminders). No declared binaries, env vars, or installs that would be inconsistent with a marketing-ops assistant.
Instruction Scope
SKILL.md is an instruction-only spec that stays within marketing ops, but it's high-level and leaves integration details unspecified (e.g., 'send automated report reminders', 'alert 48 hours before deliverable', 'maintain asset library', 'pull key metrics'). That vagueness gives an agent broad discretion about how to obtain/send data (which connectors or credentials to use) but the file itself does not instruct reading system files or secrets.
Install Mechanism
No install spec and no code files — lowest-risk delivery model (instruction-only). Nothing is written to disk or fetched at install time.
Credentials
Skill declares no required environment variables, credentials, or config paths. The declared requirements are proportionate to the instruction-only nature. Note: many practical features (email/calendar/drive/CRM access) would normally require credentials, but none are requested here.
Persistence & Privilege
always is false and the skill does not request persistent or elevated system privileges. Autonomous invocation is allowed by default (platform standard) but not excessive in the skill metadata.
Assessment
This skill is coherent and lightweight as provided, but its feature list implies integrations (email/calendar/CRM/cloud storage) that are not specified. Before using, decide which connectors you'll allow and how you'll provide access: prefer limited-scope OAuth or throwaway/test accounts rather than long-lived API keys; do not paste full admin credentials into chat. If you don't want the agent to act autonomously (send reminders, modify calendars, or push invoices), keep autonomous invocation disabled or require explicit confirmation for actions that touch external systems. If the agent asks for credentials later, verify where and why they'll be used and consider testing in a restricted environment first.Like a lobster shell, security has layers — review code before you run it.
latestvk97ah5919dpgv76127jq59m0y984z1z0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.