agentsclimarketplace
Sign in

Cta generator

Skill bg-szy/TOP-SKILLS/skills/superskills/cta-generator

When the user wants to design, optimize, or audit call-to-action (CTA) buttons. Also use when the user mentions "CTA," "call to action," "button design," "conversion button," "primary action," "CTA copy," "button text," "CTA placement," "conversion CTA," or "action button." For landing pages, use landing-page-generator.From its SKILL.md

Install
npx -y skills add bg-szy/TOP-SKILLS --skill cta-generator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.4 KB, 745 tokens by cl100k_base, as published. Nobody here has run it

Components: Call-to-Action (CTA)

Guides CTA button design for conversion. A well-designed CTA can increase conversion by 25–10%.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Initial Assessment

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for conversion goals.

Identify:

  1. Context: Hero, form, pricing, product page
  2. User stage: Awareness, consideration, decision
  3. Primary action: Sign up, buy, trial, download

Design Principles

Visual Clarity

  • Look like buttons: Background, border, corner radius, shadow
  • Stand out: Contrasting color; clear hierarchy
  • Size: ≥48×48px for touch; minimum 48px wide

Hierarchy

  • Primary CTA: One per section; impossible to miss
  • Secondary CTA: Lower priority; visually distinct
  • Avoid: Multiple competing CTAs causing choice overload

Color & Shape

  • Color: High contrast; red/orange for urgency
  • Shape: Rounded = friendly; angled = dynamic
  • Accessibility: →.5:1 contrast for text

Copy Best Practices

  • Action-oriented: "Buy," "Sign up," "Subscribe," "Get started"
  • Loss aversion: "Claim Your Discount Before It's Gone" vs "Get 10% Off"; see discount-marketing-strategy for discount campaign design
  • Clear, no ambiguity: User knows exactly what happens
  • Scarcity/urgency: When appropriate; avoid overuse

Placement

  • Above the fold for primary actions
  • After value proposition; build value before CTA
  • Near trust signals (testimonials, badges)
  • Sticky/fixed for long pages (use sparingly)

Technical

  • Semantic HTML: <button> or <a> with role="button" when needed
  • Visible focus state for keyboard users
  • Loading state for async actions: disable button during async operations; show spinner or loading text; prevent double-submit
  • cursor-pointer: Add cursor-pointer to all clickable CTAs; default cursor on interactive elements is poor UX
  • aria-label: Use aria-label for icon-only buttons (e.g., close, search); screen readers need descriptive labels
  • Hover stability: Use color/opacity transitions (150–300ms); avoid scale transforms that shift layout

Testing

  • A/B test: color, copy, placement, size
  • Measure: click-through rate, conversion rate

Output Format

  • CTA copy suggestions
  • Design notes (color, size, hierarchy)
  • Placement recommendations
  • Accessibility checklist (cursor-pointer, aria-label, focus, loading state)

Related Skills

  • hero-generator: Hero typically contains primary CTA
  • landing-page-generator: CTA is step 5 of landing page flow; single-goal pages
  • testimonials-generator: Testimonials near CTAs boost conversion
  • trust-badges-generator: Badges near CTAs increase trust
  • pricing-page-generator: CTA on pricing pages (e.g., "Start free trial")

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most design frontend skills give in 745 tokens

Counted across 1,169 of the 1,878 authors here whose files we hold, read 2026-08-07

  • Use CSS variables for color consistencyin 72 of 1169, across 23 files
  • Commit to one bold aesthetic direction before codingin 72 of 1169, across 27 files
  • Match implementation complexity to the aesthetic visionin 70 of 1169, across 20 files
  • Add atmospheric background effects and texturesin 57 of 1169, across 9 files
  • Use unexpected spatial compositions and layoutsin 56 of 1169, across 8 files
  • Implement real working codein 55 of 1169, across 7 files
  • Vary themes and aesthetics across different designsin 48 of 1169, across 7 files
  • Launch chromium in headless modein 47 of 1169, across 4 files
  • Close the browser when donein 47 of 1169, across 4 files
  • Run provided scripts with help flag firstin 47 of 1169, across 4 files
  • Wait for network idle statein 47 of 1169, across 4 files
  • Use descriptive selectors for elementsin 47 of 1169, across 4 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,758. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.