GTM Outbound Strategy
v1.0.0Design outbound GTM campaigns and write ready-to-send sequences. Use when building a new outbound motion, writing cold email or LinkedIn outreach, designing...
⭐ 0· 110·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 and description (outbound GTM campaign design and ready-to-send sequences) match the SKILL.md steps: confirming setup, building messaging, selecting channels, designing a sequence, and writing copy. There are no extraneous requirements (no binaries, env vars, or config paths) that would be unexpected for this purpose.
Instruction Scope
Runtime instructions are narrowly scoped to campaign design and copywriting. The SKILL.md instructs the agent to ask the user for segment/persona/product/trigger details before writing and to produce ready-to-send messages. It does not instruct the agent to read local files, access environment variables, call external services, or transmit data to third parties.
Install Mechanism
No install spec or code files are present; this is an instruction-only skill. That minimizes disk and network footprint and aligns with the stated functionality.
Credentials
The skill declares no required environment variables, credentials, or config paths. Its needs are proportional to its purpose (copy generation) and do not request unrelated secrets or permissions.
Persistence & Privilege
The skill does not request always:true and is user-invocable only. It does not attempt to modify other skills or agent-wide settings. Autonomous invocation is allowed by platform default, but that is not a red flag here because the skill has no extra privileges or access to credentials.
Assessment
This skill is instruction-only and internally coherent, so technical risk is low. Before using it, consider: (1) never supply real credentials or sensitive files to the agent when asking it to craft outreach; (2) review and verify all factual 'hooks' (funding, job posts, customer names) — do not fabricate claims; (3) check generated messages for PII/leakage and legal/compliance rules (CAN-SPAM, GDPR, platform policies on LinkedIn); (4) test on a small sample before sending at scale; and (5) always human-review and approve outbound copy before sending.Like a lobster shell, security has layers — review code before you run it.
latestvk97cxsad68demjf1p8sm0jygnh833d8q
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
