Cta Clarity Check

Checks whether each call to action states the next step plainly, and whether the page is asking for one thing or quietly asking for five. Use when clicks on the primary action are low, or when a page has accumulated buttons over time.

9 stars 3 forksOther

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add mardab96/landing-pages-claude-skills --skill cta-clarity-check
Manual install
git clone --depth 1 https://github.com/mardab96/landing-pages-claude-skills.git /tmp/landing-pages-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/landing-pages-claude-skills/cta-clarity-check ~/.claude/skills/cta-clarity-check

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Cta Clarity Check

## Use this skill when

- every CTA label and its position on the page are available, and the primary action is getting fewer clicks than the traffic and scroll data suggest it should.
- buttons accumulated over a year and nobody removed any.
- the same action carries two different labels in two places on the page.

This skill reviews the asks the page makes. Which ask it *should* make belongs to `trial-vs-demo-path-decision`.

## Required input

- every CTA on the page: exact label, position, visual weight, and whether it is a button, a link or a form.
- which single conversion is the primary one, stated explicitly by the user.
- any secondary asks living on the page: newsletter field, chat, download, demo video.
- optional: clicks per CTA, which is what turns this from a structural review into a measured one.
- If the primary conversion is not stated, ask. Without it there is no way to tell a competing CTA from a supporting one.

### If the data does not exist

- **No per-CTA clicks:** this is the normal case, because it requires each button to be tagged. Say the finding about which CTA absorbs attention is unavailable, and run the rest, since duplicate labels and four equal-weight commitments are read off the page.
- **To get them:** the cheapest route is giving each CTA a distinct destination or query string and reading the destination traffic. The proper route is a GTM click trigger per button, which is a developer task, not a page fix.
Read the full skill on GitHub

Details

Skill name
cta-clarity-check
Path
cta-clarity-check/SKILL.md
License
MIT
Repo updated
30 July 2026

FAQ

What does the Cta Clarity Check skill do?

Checks whether each call to action states the next step plainly, and whether the page is asking for one thing or quietly asking for five. Use when clicks on the primary action are low, or when a page has accumulated buttons over time.

How do I install the Cta Clarity Check skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add mardab96/landing-pages-claude-skills --skill cta-clarity-check. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Cta Clarity Check popular?

It lives in mardab96/landing-pages-claude-skills, which has 9 GitHub stars and 3 forks.

Related skills

Above the Fold Clarity Review

9

mardab96/landing-pages-claude-skills

Judges what a visitor can actually understand and do in the first screen, before any scroll. Use when bounce is high, when a page was redesigned, or when the hero has to carry cold traffic that knows nothing about the brand.

Frontend & Design

Accessibility Conversion Blocker Check

9

mardab96/landing-pages-claude-skills

Finds the accessibility defects that also block conversion: unreadable contrast, tap targets too small to hit, form fields with no label, and error states nobody can perceive. Use when a page is being shipped, when mobile form completion is poor, or when an audit flagged accessibility and nobody knows which items matter commercially.

Frontend & Design

Comparison Page Positioning Review

9

mardab96/landing-pages-claude-skills

Reviews a "versus competitor" or alternatives page for claims that will not survive contact with the competitor's own page. Use when a comparison page is being written, when it ranks but does not convert, or when a competitor changed their pricing or feature set.

Marketing, Sales & Business

Form Friction Finder

9

mardab96/landing-pages-claude-skills

Finds the fields, validation rules, error states and steps that stop people finishing a form they intended to finish. Use when form starts are healthy and submits are not, or when a field was added and completion dropped.

Other

Conversion Leak Finder

9

mardab96/landing-pages-claude-skills

Traces every way a visitor can leave the page without converting: outbound links, navigation, dead ends and paths that lead nowhere. Use when sessions are healthy, the offer is clear, and conversions still do not appear.

Other

Hero Section Diagnosis

9

mardab96/landing-pages-claude-skills

Reads the headline, subhead, visual and primary CTA as one unit and finds where they contradict each other. Use when each hero element looks fine alone but the section as a whole does not land, or before a hero rewrite ships.

Other

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.