Copywriting Pro

v1.0.0

Write persuasive, high-converting copy for any format — ads, landing pages, emails, sales pages, headlines, product descriptions, CTAs, and social posts. App...

0· 3.1k·22 current·24 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description (high-converting copy for multiple formats) match the SKILL.md and the three reference documents. No binaries, env vars, or config paths are required — nothing requested is out of scope for a copywriting skill.
Instruction Scope
Instructions are focused on research, frameworks, readability rules, and a preflight checklist. One notable point: the workflow encourages mining Voice-of-Customer (VoC) sources (reviews, testimonials, support tickets, sales-call transcripts) if available. That is appropriate for copywriting, but it does mean the agent may ask for or consume user-provided customer data — review any such data for PII before sharing.
Install Mechanism
No install spec and no code files — instruction-only. This minimizes disk writes and external code execution risk.
Credentials
The skill requests no environment variables, credentials, or config paths. All data access implied by the instructions is expected to be user-supplied contextual material (VoC, briefs, assets) rather than hidden system credentials.
Persistence & Privilege
always is false and disable-model-invocation is false (normal). The skill does not request permanent presence or system-level changes.
Assessment
This skill is internally coherent and low-risk as packaged, but it explicitly asks you to provide Voice-of-Customer material (reviews, support tickets, call transcripts) when available — do not upload customer PII or sensitive data unless you have permission and have redacted personal identifiers. Treat any factual claims the generated copy makes (numbers, testimonials, guarantees) as drafts that you must verify before publishing to avoid legal or reputational issues. Because it's instruction-only, risks come from what you feed it: verify sources, redact sensitive info, and review outputs for accuracy, privacy, and compliance before use.

Like a lobster shell, security has layers — review code before you run it.

latestvk9723hqnmzk8r0c3483cmfq129827xx7

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments