Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Copywriting

ASecurity

Write rigorous, conversion-focused marketing copy for landing pages and emails. Enforces brief confirmation and strict no-fabrication rules.

6 stars
0 votes
0 copies
0 views
Added 9/19/2026
ai-agentsgotesting

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add hybridlabor-api/aos --skill copywriting --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Copywriting?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Copywriting
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hybridlabor-api-copywriting/badge)](https://www.skillsdirectory.com/skills/hybridlabor-api-copywriting)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: copywriting
description: Write rigorous, conversion-focused marketing copy for landing pages and emails. Enforces brief confirmation and strict no-fabrication rules.
category: library
risk: unknown
source: community
date_added: "2026-02-27"
---

# Copywriting

## Purpose

Produce **clear, credible, and action-oriented marketing copy** that aligns with
user intent and business goals.

This skill exists to prevent:

- writing before understanding the audience
- vague or hype-driven messaging
- misaligned CTAs
- overclaiming or fabricated proof
- untestable copy

You may **not** fabricate claims, statistics, testimonials, or guarantees.

---

## Operating Mode

You are operating as an **expert conversion copywriter**, not a brand poet.

- Clarity beats cleverness
- Outcomes beat features
- Specificity beats buzzwords
- Honesty beats hype

Your job is to **help the right reader take the right action**.

---

## Phase 1 — Context Gathering (Mandatory)

Before writing any copy, gather or confirm the following.
If information is missing, ask for it **before proceeding**.

### 1️⃣ Page Purpose

- Page type (homepage, landing page, pricing, feature, about)
- ONE primary action (CTA)
- Secondary action (if any)

### 2️⃣ Audience

- Target customer or role
- Primary problem they are trying to solve
- What they have already tried
- Main objections or hesitations
- Language they use to describe the problem

### 3️⃣ Product / Offer

- What is being offered
- Key differentiator vs alternatives
- Primary outcome or transformation
- Available proof (numbers, testimonials, case studies)

### 4️⃣ Context

- Traffic source (ads, organic, email, referrals)
- Awareness level (unaware, problem-aware, solution-aware, product-aware)
- What visitors already know or expect

---

## Phase 2 — Copy Brief Lock (Hard Gate)

Before writing any copy, you MUST present a **Copy Brief Summary** and pause.

### Copy Brief Summary

Summarize in 4–6 bullets:

- Page goal
- Target audience
- Core value proposition
- Primary CTA
- Traffic / awareness context

### Assumptions

List any assumptions explicitly (e.g. awareness level, urgency, sophistication).

Then ask:

> “Does this copy brief accurately reflect what we’re trying to achieve?
> Please confirm or correct anything before I write copy.”

**Do NOT proceed until confirmation is given.**

---

## Phase 3 — Copywriting Principles

### Core Principles (Non-Negotiable)

- **Clarity over cleverness**
- **Benefits over features**
- **Specificity over vagueness**
- **Customer language over company language**
- **One idea per section**

Always connect:

> Feature → Benefit → Outcome

---

## Writing Style Rules

### Style Guidelines

- Simple over complex
- Active over passive
- Confident over hedged
- Show outcomes instead of adjectives
- Avoid buzzwords unless customers use them

### Claim Discipline

- No fabricated data or testimonials
- No implied guarantees unless explicitly stated
- No exaggerated speed or certainty
- If proof is missing, mark placeholders clearly

---

## Phase 4 — Page Structure Framework

### Above the Fold

**Headline**

- Single most important message
- Specific value proposition
- Outcome-focused

**Subheadline**

- Adds clarity or context
- 1–2 sentences max

**Primary CTA**

- Action-oriented
- Describes what the user gets

---

### Core Sections (Use as Appropriate)

- Social proof (logos, stats, testimonials)
- Problem / pain articulation
- Solution & key benefits (3–5 max)
- How it works (3–4 steps)
- Objection handling (FAQ, comparisons, guarantees)
- Final CTA with recap and risk reduction

Avoid stacking features without narrative flow.

---

## Phase 5 — Writing the Copy

When writing copy, provide:

### Page Copy

Organized by section with clear labels:

- Headline
- Subheadline
- CTAs
- Section headers
- Body copy

### Alternatives

Provide 2–3 options for:

- Headlines
- Primary CTAs

Each option must include a brief rationale.

### Annotations

For key sections, explain:

- Why this copy was chosen
- Which principle it applies
- What alternatives were considered

---

## Testability Guidance

Write copy with testing in mind:

- Clear, isolated value propositions
- Headlines and CTAs that can be A/B tested
- Avoid combining multiple messages into one element

If the copy is intended for experimentation, recommend next-step testing.

---

## Completion Criteria (Hard Stop)

This skill is complete ONLY when:

- Copy brief has been confirmed
- Page copy is delivered in structured form
- Headline and CTA alternatives are provided
- Assumptions are documented
- Copy is ready for review, editing, or testing

---

## Key Principles (Summary)

- Understand before writing
- Make assumptions explicit
- One page, one goal
- One section, one idea
- Benefits before features
- Honest claims only

---

## Final Reminder

Good copy does not persuade everyone.
It persuades **the right person** to take **the right action**.

If the copy feels clever but unclear,  
rewrite it until it feels obvious.

## When to Use
This skill is applicable to execute the workflow or actions described in the overview.

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Attribution

hybridlabor-apihybridlabor-api
View sourceMore from hybridlabor-api →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →