Cta Generator
Design, rewrite, and audit primary and secondary CTA buttons so landing pages, pricing blocks, and hero sections convert without choice overload.
Overview
CTA Generator is an agent skill most often used in Validate (also Launch, Grow) that designs, optimizes, and audits call-to-action buttons for conversion-focused pages.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill cta-generatorWhat is this skill?
- Initial assessment for context (hero, form, pricing, product page), user stage, and primary action
- Visual clarity rules: button affordance, contrast, ≥48×48px touch targets
- One primary CTA per section with visually distinct secondary actions
- Pairs with landing-page-generator for full-page work; this skill focuses on button-level conversion
- References project context files (.claude/.cursor project-context.md) for conversion goals
- ≥48×48px minimum touch target sizing
- Claims well-designed CTAs can increase conversion by 25–10% (as stated in skill copy)
Adoption & trust: 797 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have traffic or a draft page but weak or competing buttons so visitors never commit to signup, trial, or purchase.
Who is it for?
Solo builders tuning hero, pricing, or form CTAs on a landing or product page before or during a launch push.
Skip if: Full landing-page structure, wireframes, or SEO copy—use landing-page-generator instead when the whole page is in scope.
When should I use this skill?
User wants to design, optimize, or audit CTAs; mentions CTA, call to action, button design, conversion button, primary action, CTA copy, placement, or action button.
What do I get? / Deliverables
You get hierarchy-aligned primary and secondary CTAs with clear copy, contrast, and touch-safe sizing ready to ship on hero, form, and pricing sections.
- CTA hierarchy recommendation per section
- Primary and secondary button copy and visual specs
- Conversion-focused audit notes for hero, form, or pricing context
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Landing and pricing validation is where CTA hierarchy and copy are decided before you scale traffic. Prototype and landing experiments need one obvious primary action per section—the skill’s initial assessment explicitly targets hero, form, and pricing contexts.
Where it fits
Pick one primary signup CTA and a softer secondary for the MVP landing hero before paid tests.
Align pricing-table buttons with decision-stage copy (start trial vs contact sales).
Refresh campaign landing CTAs so they contrast with ad creative and match the promised offer.
Tune email-linked product CTAs for upgrade or reactivation without duplicating competing actions.
How it compares
Button- and conversion-focused skill, not a full landing-page generator or generic UI kit.
Common Questions / FAQ
Who is cta-generator for?
Indie founders and marketers shipping SaaS, content, or ecommerce pages who want agent-guided CTA copy, hierarchy, and visual specs without hiring a conversion specialist.
When should I use cta-generator?
During Validate on landing and pricing experiments, at Launch when polishing distribution pages, and in Grow when improving lifecycle or campaign landing CTAs—whenever you say CTA, button text, placement, or conversion audit.
Is cta-generator safe to install?
Review the Security Audits panel on this Prism page before installing; the skill is guidance-only and does not require shell or network by default.
SKILL.md
READMESKILL.md - Cta Generator
# 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")