What makes copywriting-cta notable?

1K downloads. Trust evidence available

How should copywriting-cta be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

copywriting-cta

Design end-of-article CTAs (calls-to-action placed at the bottom of blog posts, newsletters, essays, articles, or any long-form content). Use this skill whenever the user asks to write, design, review, or improve a CTA at the bottom of an article, blog post, or essay; mentions "end-of-post CTA", "bottom of the article", "call-to-action", "signup box", "newsletter CTA", "subscribe block", "what should I put at the bottom", "how do I get readers to subscribe / share / book a call / buy / follow / join / download"; or asks how to convert article readers into subscribers, leads, customers, community members, or supporters. Also trigger when the user wants A/B testing guidance or accessibility review for a CTA block. Covers independent / personal writing, newsletter publications, and brand / content-marketing blogs across any topic — tech, finance, food, climate, design, lifestyle, B2B, B2C. Produces both the copy (content) and the structural / visual design (form), matched to the user's objective and audience. Skill: copywriting-cta Owner: samber Summary: Design end-of-article CTAs (calls-to-action placed at the bottom of blog posts, newsletters, essays, articles, or any long-form content). Use this skill whenever the user asks to write, design, review, or improve a CTA at the bottom of an article, blog post, or essay; mentions "end-of-post CTA", "bottom of the article", "call-to-action", "signup box", "newsletter CTA", "s

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.0k

Updated

Oct 11, 2026

Version

1.1.0

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1K downloadsadoption · observed Oct 11, 2026
Latest release: 1.1.0release · observed Aug 20, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s173arkhs3131fq5jf769qq75583hdgt:copywriting-cta

Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-samber-copywriting-cta/snapshot"

Run-check

$0.02 USD

1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.

Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.

Documentation

CLAWHUB

132,248 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: copywriting-cta
description: Design end-of-article CTAs (calls-to-action placed at the bottom of blog posts, newsletters, essays, articles, or any long-form content). Use this skill whenever the user asks to write, design, review, or improve a CTA at the bottom of an article, blog post, or essay; mentions "end-of-post CTA", "bottom of the article", "call-to-action", "signup box", "newsletter CTA", "subscribe block", "what should I put at the bottom", "how do I get readers to subscribe / share / book a call / buy / follow / join / download"; or asks how to convert article readers into subscribers, leads, customers, community members, or supporters. Also trigger when the user wants A/B testing guidance or accessibility review for a CTA block. Covers independent / personal writing, newsletter publications, and brand / content-marketing blogs across any topic — tech, finance, food, climate, design, lifestyle, B2B, B2C. Produces both the copy (content) and the structural / visual design (form), matched to the user's objective and audience.
user-invocable: true
license: MIT
compatibility: Designed for Claude or similar AI agents.
metadata:
  author: samber
  version: "1.1.0"
  openclaw:
    emoji: "🎯"
    homepage: https://github.com/samber/cc-skills
allowed-tools: Read Edit Write Glob Grep Agent AskUserQuestion
---

**Questions:** Ask the user through the environment's question tool — never as plain-text prose. One question at a time, 2–4 tappable options, wait for the answer. If the environment has no question tool, ask in prose with the same options, one at a time.

# End-of-Article CTA Designer

Designing an end-of-article CTA is a function of three inputs: the **objective** (what action), the **audience** (who reads it, in what relationship to the author), and the **context** (independent writing, newsletter, brand publication). Get those three right and the copy + form follow almost mechanically. Skip them and you get the universal failure mode: a generic "Subscribe for more" or "Learn More" that converts at the noise floor.

This skill runs a tight interview to capture those three inputs, then prescribes a CTA: copy (what it says), form (how it looks and sits on the page), mechanism (whether to use urgency, scarcity, curiosity, reciprocity, social proof, or none), an A/B test plan, and an accessibility check.

---

## Workflow

Run the four steps below in order. Do not skip the interview. The user may have given partial context already; pull what's available from the conversation, then ask only for the missing pieces.

### Step 1 — Interview

Ask one question at a time. Do not stack questions in prose. Each question must have 2-4 tappable options. Fall back to free text only if the answer genuinely cannot be enumerated.

Ask these in order, skipping any already answered:

**Q1. Article context.** Options: `Personal / independent blog or essay` · `Newsletter / paid publication (Substack, beehiiv, Ghost, etc.)` · `Brand / company / cont

_meta.json

{
  "ownerId": "kn72rhnkwjfeex9wr1n7y24qa983cjn3",
  "slug": "copywriting-cta",
  "version": "1.1.0",
  "publishedAt": 1787239505671
}

references/ab-testing.md

# A/B Testing CTAs — Priority, Method, Pitfalls

A/B testing CTAs is high-leverage when you have enough traffic. It is theatre when you don't. This file covers what to test, in what order, with what sample size, and the failure modes that produce confidently wrong conclusions.

---

## When NOT to A/B test

If any of the following is true, skip A/B testing and just ship a single well-designed CTA:

- Article gets fewer than ~1,000 unique readers per month. Below this threshold, runs take forever and confidence intervals are noise.
- Baseline conversion rate is below 0.5%. The signal is too weak to detect any but the largest lifts.
- You haven't written a strong baseline yet. Testing "Subscribe" vs. "Sign up" on a generic CTA is rearranging deck chairs; rewrite the value statement first.
- You don't have event tracking wired up. Without per-CTA click and downstream conversion tracking, you can't measure outcomes.

Effort is better spent improving the baseline CTA copy and content quality until traffic justifies testing.

---

## Priority order: what to test first

Test variables in this order (Foundry CRO's "priority stack" plus operator experience):

### Tier 1 — Highest leverage

1. **Number of CTAs.** One primary vs. one primary + one secondary vs. multiple equal-weight CTAs. Single-CTA pages convert ~30%+ better than multi-CTA pages in repeated case studies.
2. **Value statement.** "Subscribe to our newsletter" vs. "Get one [specific thing] a week." This is the single highest-impact variable in most tests.
3. **Specificity of the offer.** "Download our guide" vs. "Download the 14-line shell script we used to cut infra costs 40%." Specific concrete artifacts can lift conversion 2-5x.

### Tier 2 — Significant leverage

1. **Button copy.** "Submit" vs. "Send me the next one." Apply Wiebe's "I want to \_\_\_" completion test.
2. **Proof co-location.** No proof vs. subscriber count vs. testimonial vs. logo wall.
3. **Mechanism applied.** Value-only vs. with social proof vs. with reciprocity. Test one mechanism at a time.

### Tier 3 — Marginal leverage

1. **Placement.** End-only vs. end + sticky vs. end + mid-article repeat.
2. **Visual weight.** Button size, color, contrast. The Demio case showed +57.79% from larger and darker, with no color change.
3. **Form length.** Single field (email only) vs. multi-field (name + email + role).

### Tier 4 — Marginal-to-noise

1. **Button color.** Red vs. green vs. orange vs. blue. The well-known ~21% lift cited in CXL is real but small and contextual. Contrast with surroundings matters more than the specific color.
2. **Microcopy variations** ("100% spam-free" vs. "We respect your inbox"). Stop here unless top tiers are exhausted.

---

## Method: one variable per test

**Always change one variable per test.** HubSpot's Carly Stec: "Avoid testing multiple variables at the same time." Multi-variable tests produce results you can't attribute. The lift could be from any of the changes or from interactions bet

references/accessibility.md

# Accessibility Checklist for CTA Blocks

A CTA that excludes readers with disabilities is a CTA that converts at a lower ceiling. This is also an EAA / WCAG compliance concern for any commercial European-facing content as of June 2025.

This file lists the WCAG 2.2 requirements that apply to end-of-article CTA blocks, with concrete pass/fail criteria. Apply all of these to every CTA you ship. There is no acceptable trade-off.

---

## 1. Color contrast (WCAG 2.2 SC 1.4.3 / 1.4.11)

### Text contrast

- **Normal text (< 18pt regular / < 14pt bold):** contrast ratio ≥ **4.5:1** against the background. AA requirement.
- **Large text (≥ 18pt regular / ≥ 14pt bold):** contrast ratio ≥ **3:1**. AA requirement.
- **AAA target (recommended for primary CTAs):** ≥ **7:1** for normal text, ≥ **4.5:1** for large text.

### Non-text contrast (UI components, button outlines, icons)

- **UI components (button boundaries, focus indicators, form fields):** contrast ratio ≥ **3:1** against the adjacent background. SC 1.4.11, AA requirement.

### Common failure: light-gray "Subscribe" text on white

"Subtle" gray-on-white CTAs (#999 on #FFF = 2.84:1) fail WCAG by a wide margin. The fix: use a darker text color (#595959 on #FFF = 7.02:1) or fill the button.

### How to check

- **Browser DevTools:** Chrome and Firefox both ship contrast checkers in the color picker of the inspector.
- **CLI / programmatic:** axe-core, pa11y, Lighthouse.
- **Quick web tools:** WebAIM Contrast Checker, Coolors Contrast Checker, Stark.

---

## 2. Touch target size (WCAG 2.2 SC 2.5.8)

- **Minimum target size:** ≥ **24×24 CSS pixels**. AA requirement, introduced in WCAG 2.2.
- **Recommended target size:** ≥ **44×44 CSS pixels**. AAA requirement, also the Apple HIG / Google Material guideline.

### Practical thresholds

- Button: minimum 44×44px tap target including padding. Even on desktop, this margin makes the button hittable on a touchpad without precision.
- Inline text links: ensure ≥ 24×24px hit area (typically achieved with line-height + padding around the link).
- Adjacent CTAs (e.g., "Subscribe" + "RSS" + "Mastodon"): require ≥ 8px spacing between targets so adjacent taps don't trigger the wrong link.

---

## 3. Semantic markup (WCAG 2.2 SC 4.1.2)

### Use the right element

- **Submitting a form (e.g., newsletter signup):** `<button type="submit">`. Always inside a `<form>` with an explicit `action` and `method`.
- **Navigating to another page:** `<a href="...">`. Not a `<button>` styled as a link, not a `<div>` with an onClick.
- **Toggling state in-place (e.g., expanding a section):** `<button type="button">`.

### Common failures

- `<div onClick={...}>` styled as a button: invisible to screen readers, not keyboard-focusable by default. Always replace with `<button>` or `<a>`.
- `<a>` with no `href` and an onClick: same problem. Use a `<button>`.
- `<button>` that navigates: technically works, but loses right-click "Open in new tab" and middle-click behavior. Use `<a>` f

references/anti-patterns.md

# Anti-Patterns — Failure Modes to Call Out by Name

Twelve failure modes that recur across end-of-article CTAs. When the user's inputs put them at risk of one of these, call it out explicitly. Do not soften.

---

## 1. "Subscribe for more"

**Why it fails:** Says nothing about value, frequency, content, or who else is in. Conversion floor.

**Fix:** State the value proposition, frequency, and a proof signal in one line. "Get one debugging trick a week. Friday morning. 12,000+ engineers read it."

---

## 2. Generic verbs: "Learn More" / "Read More" / "Click Here" / "Get Started"

**Why they fail:** Andy Crestodina is blunt: these are not calls to action. They name no value and no destination. NN/g's "Get Started" Stops Users documents how "Get Started" specifically funnels first-time visitors into signup flows they didn't ask for.

**Fix:** Replace with the specific noun and verb. "Read more" → "Read the deep-dive on Go runtime maps." "Get Started" → "Start the 5-minute tutorial."

---

## 3. Three equally weighted buttons

**Why it fails:** Hick's Law. Equal visual weight on multiple CTAs creates decision paralysis. Reader picks none.

**Fix:** One primary CTA (button), demote others to subordinate text links or smaller secondaries. The StoryBrand "direct + transitional" dyad is the proven pattern.

---

## 4. Begging for comments

**Why it fails:** "Let me know what you think in the comments!" gets ignored. The reader can't think of anything specific to say and bounces.

**Fix:** Ask a specific question that requires recall of a personal experience or technical opinion. "What's the worst bug you shipped on a Friday afternoon?" gets answers; "What do you think?" does not.

---

## 5. Hard-sell CTA ("Book a Demo" / "Talk to Sales") on a TOFU post

**Why it fails:** Top-of-funnel readers are discovering the topic, not ready to buy. A hard-sell ask at the bottom collapses credibility for the rest of the article retroactively. For sophisticated audiences (technical, professional, niche-expert), the effect is even stronger. Yacine Hmito (Head of Technology, Fabriq): "If I see 'Book a demo' or 'Talk to Sales,' I am out." The same reflex applies to readers in professional services, healthcare, journalism, and any context where credibility is the readership currency.

**Fix:** Use a transitional asset (PDF, template, calculator, checklist) if this is brand content. Use an author-signature subscribe if this is independent content. Save "Book a Demo" for BOFU content that explicitly precedes a buying decision — and even then, prefer "Talk to a Human" or "Get a 20-min audit" verbs (both produced documented 110%+ conversion lifts vs. "Book a Demo").

---

## 6. Buzzword stacking

**Why it fails:** Generic adjectives stack without adding information. Every industry has its own catalog: tech ("AI-infused," "enterprise-grade," "single pane of glass," "synergy," "leverage," "seamless," "scalable," "at scale," "digital transformation" — Redis published an audi

Github ReposUpdated 2d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.