[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CX3J9HTF1B236T4JH8GFKC":3,"skill-same:01M7CX3J9HTF1B236T4JH8GFKC":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":39,"updatedAt":40,"install":41,"resources":53},"01M7CX3J9HTF1B236T4JH8GFKC","copywriting-cta",null,"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 \u002F share \u002F book a call \u002F buy \u002F follow \u002F join \u002F download\"; or asks how to convert article readers into subscribers, leads, customers, community members, or supporters. Also trigger when the user wants A\u002FB testing guidance or accessibility review for a CTA block. Covers independent \u002F personal writing, newsletter publications, and brand \u002F content-marketing blogs across any topic — tech, finance, food, climate, design, lifestyle, B2B, B2C. Produces both the copy (content) and the structural \u002F visual design (form), matched to the user's objective and audience.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fsamber-cc-skills\u002Fcopywriting-cta\u002Fskills\u002Fcopywriting-cta\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: copywriting-cta\ndescription: 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 \u002F share \u002F book a call \u002F buy \u002F follow \u002F join \u002F download\"; or asks how to convert article readers into subscribers, leads, customers, community members, or supporters. Also trigger when the user wants A\u002FB testing guidance or accessibility review for a CTA block. Covers independent \u002F personal writing, newsletter publications, and brand \u002F content-marketing blogs across any topic — tech, finance, food, climate, design, lifestyle, B2B, B2C. Produces both the copy (content) and the structural \u002F visual design (form), matched to the user's objective and audience.\nuser-invocable: true\nlicense: MIT\ncompatibility: Designed for Claude or similar AI agents.\nmetadata:\n  author: samber\n  version: \"1.0.0\"\n  openclaw:\n    emoji: \"🎯\"\n    homepage: https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills\nallowed-tools: Read Edit Write Glob Grep Agent AskUserQuestion\n---\n\n# End-of-Article CTA Designer\n\nDesigning 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.\n\nThis 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\u002FB test plan, and an accessibility check.\n\n---\n\n## Workflow\n\nRun 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.\n\n### Step 1 — Interview\n\nUse the `ask_user_input_v0` tool. 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.\n\nAsk these in order, skipping any already answered:\n\n**Q1. Article context.** Options: `Personal \u002F independent blog or essay` · `Newsletter \u002F paid publication (Substack, beehiiv, Ghost, etc.)` · `Brand \u002F company \u002F content-marketing blog` · `Other (free text)`\n\n**Q2. Primary objective.** (Pick the one outcome you most want from a reader who finishes the article. If they say \"all of them,\" push back: multiple objectives is the #1 cause of CTA failure.)\n\nOptions:\n\n- `Newsletter \u002F email subscription`\n- `Social follow \u002F personal branding`\n- `Lead generation (download \u002F gated asset)`\n- `Product or service signup \u002F free trial`\n- `Demo or sales call booking`\n- `Direct purchase`\n- `Community join (Discord \u002F Slack \u002F forum)`\n- `Engagement (reply \u002F comment \u002F share \u002F restack)`\n- `Reader support (paid subscription \u002F tip \u002F sponsorship)`\n- `Try-it \u002F direct action (use the code, run the tool, fork the template, open the calculator)`\n- `Other (free text)`\n\nIf the user lists more than one, ask which is primary. You can offer 1-2 secondaries later, but the primary must be singular.\n\n**Q3. Audience and relationship.** Options: `First-time visitor (organic search \u002F social)` · `Returning reader, not subscribed` · `Existing subscriber \u002F customer` · `Mixed \u002F unknown`\n\n**Q4. Funnel stage.** (Where is the reader mentally?) Options: `TOFU: discovery, learning, no buying intent yet` · `MOFU: evaluating options, comparing` · `BOFU: ready to act, just needs a nudge` · `Not applicable (no buying funnel — e.g., personal blog, journalism, hobby content)`\n\n**Q5. Mechanism preference.** (Only ask if a mechanism could legitimately help. See `references\u002Fmechanisms.md`. For sophisticated, skeptical, or repeat-reader audiences, default to \"None \u002F value-only\" without asking.) Options: `None: value statement only` · `Curiosity gap (\"Want to know more?\")` · `Reciprocity (free asset first)` · `Discount \u002F offer` · `Urgency (real deadline)` · `Scarcity \u002F FOMO (limited spots)` · `Social proof (count \u002F testimonial)`\n\nCapture any free-text constraints the user volunteers (length limit, brand voice, no popups, multi-language, etc.). Note them.\n\n### Step 2 — Diagnose\n\nMap the inputs to a CTA archetype. The decision logic:\n\n```\ncontext = INDEPENDENT \u002F PERSONAL\n├── objective = newsletter \u002F email      → Archetype A: Author-signature subscribe\n├── objective = try-it \u002F direct action  → Archetype B: Inline action + source link\n├── objective = reader support \u002F tip    → Archetype C: Reader-supported funding link\n├── objective = community               → Archetype D: Proof-counted community invite\n├── objective = social follow           → Archetype A (variant: lead with social links)\n├── objective = engagement              → Archetype E: Specific reply prompt\n└── objective = product \u002F demo          → ⚠️ FLAG. Only valid on personal\u002Fprofessional\n                                          blog where the author IS the product\n                                          (consultants, coaches, solo founders, indie devs).\n                                          Frame as \"if you hit this, here's how I help\"\n                                          — never \"Book a Demo\" verbatim.\n\ncontext = NEWSLETTER PUBLICATION\n├── objective = growth \u002F subs           → Archetype F: Share\u002Frestack + native widget\n├── objective = engagement              → Archetype E: Specific reply prompt\n├── objective = paid conversion         → Archetype G: Value-gap tease\n├── objective = monetization \u002F sponsor  → Archetype H: Inline sponsor block (not bottom)\n├── objective = community               → Archetype D\n└── objective = direct purchase         → Archetype K (rare on newsletters; use BOFU only)\n\ncontext = BRAND \u002F CONTENT MARKETING\n├── stage = TOFU                        → Archetype I: Transitional asset (lead magnet)\n├── stage = MOFU                        → Archetype J: Direct + Transitional pair\n├── stage = BOFU                        → Archetype K: Direct CTA + risk reversal\n├── objective = community               → Archetype D\n└── objective = engagement              → Archetype E (rarely the right call here)\n```\n\nRead `references\u002Ftaxonomy.md` for the full archetype catalog with copy templates, form specs, when each works, and verbatim examples from named publications.\n\n### Step 3 — Compose the recommendation\n\nOutput the recommendation in this exact structure. Do not deviate. Do not add filler.\n\n```markdown\n## Recommended CTA\n\n**Archetype:** [letter + name from decision tree] **Why this fits:** [1-2 sentences naming the input combination]\n\n### Content (copy)\n\n**Headline \u002F value line:**\n\n> [exact text]\n\n**Body \u002F proof line (1-2 lines):**\n\n> [exact text]\n\n**Button copy:**\n\n> [exact text]\n\n**Risk reversal \u002F subtext (if applicable):**\n\n> [exact text, or \"Omit: would feel forced for this audience\"]\n\n### Form (structure)\n\n- **Placement:** [end-only \u002F end + sticky \u002F end + mid-article repeat]\n- **Visual weight:** [low \u002F medium \u002F high, with justification]\n- **Layout:** [single button \u002F button + text link \u002F native widget cluster \u002F one-line signature]\n- **Proof to co-locate:** [subscriber count \u002F star count \u002F testimonial \u002F named recommenders \u002F logo wall \u002F none]\n\n### Mechanism\n\n[Named mechanism + 1 sentence on why it is appropriate, OR \"None: value statement carries it. Mechanisms would erode trust for this audience.\"]\n\n### A\u002FB test plan\n\n- **First test:** [single variable, e.g., button copy A vs. B]\n- **Why this one first:** [1 sentence]\n- **Sample size needed:** [rough estimate based on baseline traffic, or \"skip A\u002FB for now — traffic too low\" with the alternative recommendation]\n- **Next 2 tests to queue:** [in priority order]\n\n### Accessibility check\n\n- **Color contrast:** [target ratio + concrete pairing if colors known]\n- **Touch target:** [size requirement]\n- **Semantic markup:** [\u003Cbutton> vs. \u003Ca> vs. form]\n- **ARIA:** [only if non-obvious]\n- **Keyboard \u002F focus:** [requirement]\n- **Color-independence:** [non-color affordance]\n```\n\nAfter printing the recommendation, list 2-3 anti-patterns the user is at risk of falling into given their inputs, directly, as a contrarian check. Pull these from `references\u002Fanti-patterns.md`.\n\nIf the user is writing in a non-English language, translate the content section into that language but keep the structure (headings, labels) in English. Honor formality cues (e.g., `tu` vs. `vous` in French, `du` vs. `Sie` in German) based on prior conversation context, and flag the choice explicitly.\n\n### Step 4 — Offer next moves\n\nSuggest 2-3 follow-up directions:\n\n1. **Steelman the opposite.** Offer to design the CTA you would recommend against — e.g., the hard-sell version on a TOFU post — so the user can see why it fails.\n2. **Variant for a different audience or platform.** If the article will be cross-posted (own site + Medium + LinkedIn + a syndication network), offer to rewrite per platform.\n3. **End-to-end review.** Offer to audit the rest of the article for CTA-supporting signals: author bio, related-post links, in-line proof.\n\n---\n\n## Style inheritance\n\nThe copy templates in `references\u002Ftaxonomy.md` are starting points, not finished copy. Always adapt them to:\n\n- The user's stated brand voice or any `\u003CuserPreferences>` in scope (formality, language, em-dash avoidance, length limits).\n- The language of the article. Output copy in the article's language; never default to English.\n- The publication's existing voice. If the user has prior posts visible, mirror their cadence and vocabulary.\n- The reader's expected level of expertise. A CTA for a beginner-finance blog uses different vocabulary than one for a quant-trading newsletter.\n\nNever output a template verbatim if it conflicts with the user's stated style preferences.\n\n---\n\n## Reference files\n\nRead these as needed during diagnosis and composition. Read the relevant file in full before composing the recommendation; do not paraphrase from memory.\n\n- **`references\u002Ftaxonomy.md`**: All 11 archetypes (A through K) with copy templates, form specs, verbatim examples from named publications, and conversion expectations.\n- **`references\u002Fmechanisms.md`**: When to use urgency, scarcity, FOMO, discount, curiosity, reciprocity, social proof, authority, unity. When NOT to use them.\n- **`references\u002Fab-testing.md`**: Priority order of variables to test, sample-size rules of thumb, common pitfalls, when to skip A\u002FB testing entirely.\n- **`references\u002Faccessibility.md`**: WCAG 2.2 specifics for CTA blocks: contrast ratios, touch targets, ARIA patterns, focus states, keyboard support, motion preferences.\n- **`references\u002Fanti-patterns.md`**: 12 failure modes to call out by name when they apply to the user's inputs.\n\n---\n\n## Operating principles\n\n- **One primary CTA per post.** Multiple competing CTAs is the dominant failure mode (single-CTA pages convert ~30%+ better than multi-CTA pages in repeated case studies).\n- **Match the voice of the publication.** A personal-essay footer that reads like a SaaS landing page collapses credibility. A SaaS footer that reads like a casual signature converts at noise.\n- **Specificity beats cleverness.** \"Get one essay a week on indie filmmaking\" beats \"Subscribe to our awesome newsletter.\" Joanna Wiebe's \"I want to \\_\\_\\_\" completion test is the cleanest filter for button copy.\n- **Proof co-located with the ask.** Subscriber count, testimonial, customer logos, star count, named recommenders — whichever signal is honest for the context, place it inside or adjacent to the CTA block.\n- **Mechanisms are tools, not garnish.** Most well-written value statements need no mechanism. Add urgency, scarcity, FOMO, or discount only when the context genuinely supports them; theatrical mechanisms erode trust faster than they lift conversion.\n- **Push back on bad asks.** If the user wants \"Book a Demo\" at the bottom of a beginner tutorial for first-time visitors, say so. Do not produce a polished version of a CTA that will fail. Propose the alternative, explain why, then if the user still wants the original, deliver it with the failure mode flagged.\n","# End-of-Article CTA Designer\n\nDesigning 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.\n\nThis 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\u002FB test plan, and an accessibility check.\n\n---\n\n## Workflow\n\nRun 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.\n\n### Step 1 — Interview\n\nUse the `ask_user_input_v0` tool. 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.\n\nAsk these in order, skipping any already answered:\n\n**Q1. Article context.** Options: `Personal \u002F independent blog or essay` · `Newsletter \u002F paid publication (Substack, beehiiv, Ghost, etc.)` · `Brand \u002F company \u002F content-marketing blog` · `Other (free text)`\n\n**Q2. Primary objective.** (Pick the one outcome you most want from a reader who finishes the article. If they say \"all of them,\" push back: multiple objectives is the #1 cause of CTA failure.)\n\nOptions:\n\n- `Newsletter \u002F email subscription`\n- `Social follow \u002F personal branding`\n- `Lead generation (download \u002F gated asset)`\n- `Product or service signup \u002F free trial`\n- `Demo or sales call booking`\n- `Direct purchase`\n- `Community join (Discord \u002F Slack \u002F forum)`\n- `Engagement (reply \u002F comment \u002F share \u002F restack)`\n- `Reader support (paid subscription \u002F tip \u002F sponsorship)`\n- `Try-it \u002F direct action (use the code, run the tool, fork the template, open the calculator)`\n- `Other (free text)`\n\nIf the user lists more than one, ask which is primary. You can offer 1-2 secondaries later, but the primary must be singular.\n\n**Q3. Audience and relationship.** Options: `First-time visitor (organic search \u002F social)` · `Returning reader, not subscribed` · `Existing subscriber \u002F customer` · `Mixed \u002F unknown`\n\n**Q4. Funnel stage.** (Where is the reader mentally?) Options: `TOFU: discovery, learning, no buying intent yet` · `MOFU: evaluating options, comparing` · `BOFU: ready to act, just needs a nudge` · `Not applicable (no buying funnel — e.g., personal blog, journalism, hobby content)`\n\n**Q5. Mechanism preference.** (Only ask if a mechanism could legitimately help. See `references\u002Fmechanisms.md`. For sophisticated, skeptical, or repeat-reader audiences, default to \"None \u002F value-only\" without asking.) Options: `None: value statement only` · `Curiosity gap (\"Want to know more?\")` · `Reciprocity (free asset first)` · `Discount \u002F offer` · `Urgency (real deadline)` · `Scarcity \u002F FOMO (limited spots)` · `Social proof (count \u002F testimonial)`\n\nCapture any free-text constraints the user volunteers (length limit, brand voice, no popups, multi-language, etc.). Note them.\n\n### Step 2 — Diagnose\n\nMap the inputs to a CTA archetype. The decision logic:\n\n```\ncontext = INDEPENDENT \u002F PERSONAL\n├── objective = newsletter \u002F email      → Archetype A: Author-signature subscribe\n├── objective = try-it \u002F direct action  → Archetype B: Inline action + source link\n├── objective = reader support \u002F tip    → Archetype C: Reader-supported funding link\n├── objective = community               → Archetype D: Proof-counted community invite\n├── objective = social follow           → Archetype A (variant: lead with social links)\n├── objective = engagement              → Archetype E: Specific reply prompt\n└── objective = product \u002F demo          → ⚠️ FLAG. Only valid on personal\u002Fprofessional\n                                          blog where the author IS the product\n                                          (consultants, coaches, solo founders, indie devs).\n                                          Frame as \"if you hit this, here's how I help\"\n                                          — never \"Book a Demo\" verbatim.\n\ncontext = NEWSLETTER PUBLICATION\n├── objective = growth \u002F subs           → Archetype F: Share\u002Frestack + native widget\n├── objective = engagement              → Archetype E: Specific reply prompt\n├── objective = paid conversion         → Archetype G: Value-gap tease\n├── objective = monetization \u002F sponsor  → Archetype H: Inline sponsor block (not bottom)\n├── objective = community               → Archetype D\n└── objective = direct purchase         → Archetype K (rare on newsletters; use BOFU only)\n\ncontext = BRAND \u002F CONTENT MARKETING\n├── stage = TOFU                        → Archetype I: Transitional asset (lead magnet)\n├── stage = MOFU                        → Archetype J: Direct + Transitional pair\n├── stage = BOFU                        → Archetype K: Direct CTA + risk reversal\n├── objective = community               → Archetype D\n└── objective = engagement              → Archetype E (rarely the right call here)\n```\n\nRead `references\u002Ftaxonomy.md` for the full archetype catalog with copy templates, form specs, when each works, and verbatim examples from named publications.\n\n### Step 3 — Compose the recommendation\n\nOutput the recommendation in this exact structure. Do not deviate. Do not add filler.\n\n```markdown\n## Recommended CTA\n\n**Archetype:** [letter + name from decision tree] **Why this fits:** [1-2 sentences naming the input combination]\n\n### Content (copy)\n\n**Headline \u002F value line:**\n\n> [exact text]\n\n**Body \u002F proof line (1-2 lines):**\n\n> [exact text]\n\n**Button copy:**\n\n> [exact text]\n\n**Risk reversal \u002F subtext (if applicable):**\n\n> [exact text, or \"Omit: would feel forced for this audience\"]\n\n### Form (structure)\n\n- **Placement:** [end-only \u002F end + sticky \u002F end + mid-article repeat]\n- **Visual weight:** [low \u002F medium \u002F high, with justification]\n- **Layout:** [single button \u002F button + text link \u002F native widget cluster \u002F one-line signature]\n- **Proof to co-locate:** [subscriber count \u002F star count \u002F testimonial \u002F named recommenders \u002F logo wall \u002F none]\n\n### Mechanism\n\n[Named mechanism + 1 sentence on why it is appropriate, OR \"None: value statement carries it. Mechanisms would erode trust for this audience.\"]\n\n### A\u002FB test plan\n\n- **First test:** [single variable, e.g., button copy A vs. B]\n- **Why this one first:** [1 sentence]\n- **Sample size needed:** [rough estimate based on baseline traffic, or \"skip A\u002FB for now — traffic too low\" with the alternative recommendation]\n- **Next 2 tests to queue:** [in priority order]\n\n### Accessibility check\n\n- **Color contrast:** [target ratio + concrete pairing if colors known]\n- **Touch target:** [size requirement]\n- **Semantic markup:** [\u003Cbutton> vs. \u003Ca> vs. form]\n- **ARIA:** [only if non-obvious]\n- **Keyboard \u002F focus:** [requirement]\n- **Color-independence:** [non-color affordance]\n```\n\nAfter printing the recommendation, list 2-3 anti-patterns the user is at risk of falling into given their inputs, directly, as a contrarian check. Pull these from `references\u002Fanti-patterns.md`.\n\nIf the user is writing in a non-English language, translate the content section into that language but keep the structure (headings, labels) in English. Honor formality cues (e.g., `tu` vs. `vous` in French, `du` vs. `Sie` in German) based on prior conversation context, and flag the choice explicitly.\n\n### Step 4 — Offer next moves\n\nSuggest 2-3 follow-up directions:\n\n1. **Steelman the opposite.** Offer to design the CTA you would recommend against — e.g., the hard-sell version on a TOFU post — so the user can see why it fails.\n2. **Variant for a different audience or platform.** If the article will be cross-posted (own site + Medium + LinkedIn + a syndication network), offer to rewrite per platform.\n3. **End-to-end review.** Offer to audit the rest of the article for CTA-supporting signals: author bio, related-post links, in-line proof.\n\n---\n\n## Style inheritance\n\nThe copy templates in `references\u002Ftaxonomy.md` are starting points, not finished copy. Always adapt them to:\n\n- The user's stated brand voice or any `\u003CuserPreferences>` in scope (formality, language, em-dash avoidance, length limits).\n- The language of the article. Output copy in the article's language; never default to English.\n- The publication's existing voice. If the user has prior posts visible, mirror their cadence and vocabulary.\n- The reader's expected level of expertise. A CTA for a beginner-finance blog uses different vocabulary than one for a quant-trading newsletter.\n\nNever output a template verbatim if it conflicts with the user's stated style preferences.\n\n---\n\n## Reference files\n\nRead these as needed during diagnosis and composition. Read the relevant file in full before composing the recommendation; do not paraphrase from memory.\n\n- **`references\u002Ftaxonomy.md`**: All 11 archetypes (A through K) with copy templates, form specs, verbatim examples from named publications, and conversion expectations.\n- **`references\u002Fmechanisms.md`**: When to use urgency, scarcity, FOMO, discount, curiosity, reciprocity, social proof, authority, unity. When NOT to use them.\n- **`references\u002Fab-testing.md`**: Priority order of variables to test, sample-size rules of thumb, common pitfalls, when to skip A\u002FB testing entirely.\n- **`references\u002Faccessibility.md`**: WCAG 2.2 specifics for CTA blocks: contrast ratios, touch targets, ARIA patterns, focus states, keyboard support, motion preferences.\n- **`references\u002Fanti-patterns.md`**: 12 failure modes to call out by name when they apply to the user's inputs.\n\n---\n\n## Operating principles\n\n- **One primary CTA per post.** Multiple competing CTAs is the dominant failure mode (single-CTA pages convert ~30%+ better than multi-CTA pages in repeated case studies).\n- **Match the voice of the publication.** A personal-essay footer that reads like a SaaS landing page collapses credibility. A SaaS footer that reads like a casual signature converts at noise.\n- **Specificity beats cleverness.** \"Get one essay a week on indie filmmaking\" beats \"Subscribe to our awesome newsletter.\" Joanna Wiebe's \"I want to \\_\\_\\_\" completion test is the cleanest filter for button copy.\n- **Proof co-located with the ask.** Subscriber count, testimonial, customer logos, star count, named recommenders — whichever signal is honest for the context, place it inside or adjacent to the CTA block.\n- **Mechanisms are tools, not garnish.** Most well-written value statements need no mechanism. Add urgency, scarcity, FOMO, or discount only when the context genuinely supports them; theatrical mechanisms erode trust faster than they lift conversion.\n- **Push back on bad asks.** If the user wants \"Book a Demo\" at the bottom of a beginner tutorial for first-time visitors, say so. Do not produce a polished version of a CTA that will fail. Propose the alternative, explain why, then if the user still wants the original, deliver it with the failure mode flagged.\n",{"name":5,"license":15,"metadata":24,"description":7,"allowed-tools":30,"compatibility":31,"user-invocable":32},{"author":25,"version":26,"openclaw":27},"samber","1.0.0",{"emoji":28,"homepage":29},"🎯","https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills","Read Edit Write Glob Grep Agent AskUserQuestion","Designed for Claude or similar AI agents.",true,"main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fsamber-cc-skills\u002Fcopywriting-cta\u002Fskills\u002Fcopywriting-cta",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":32},[43,46,49],{"tool":44,"command":45},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill copywriting-cta",{"tool":47,"command":48},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill copywriting-cta",{"tool":50,"command":51},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill copywriting-cta","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fsamber-cc-skills\u002Fcopywriting-cta\u002Fskills\u002Fcopywriting-cta\u002FSKILL.md",[],[55,62,67,74,79,86],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":63,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":75,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":87,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]