Hero Section Diagnosis
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.
Install
npx skills add mardab96/landing-pages-claude-skills --skill hero-section-diagnosisgit 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/hero-section-diagnosis ~/.claude/skills/hero-section-diagnosisPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Hero Section Diagnosis ## Use this skill when - the hero elements are all available and the section reads as four separate decisions rather than one argument. - each hero element looks fine reviewed alone, and the section still does not land. - the headline and the subhead appear to be speaking to two different people. This skill reads the four hero elements as one argument. For what is visible without scrolling, use `above-the-fold-clarity-review`. ## Required input - all four hero elements together: headline, subhead, visual, primary CTA. Partial input produces a partial review, and this skill is specifically about the interaction between them. - what the product does, in the team's own words, so the hero can be checked against it. - who the hero is meant to address. - optional: any variant of the hero that has run before, and how it performed. - If the visual is described rather than supplied, say the visual findings are based on a description. Not for: what is visible without scrolling (`above-the-fold-clarity-review`), or whether the offer is specific (`offer-clarity-diagnosis`). ## Analysis workflow 1. Assess headline, subheadline, primary CTA, visual, proof cue and form entry point as one decision unit. 2. Check whether the hero matches traffic intent and buyer stage. 3. Flag hero failures: vague headline, no concrete outcome, weak proof, no audience cue, buried CTA or visual noise. 4. Compare hero promise with downstream section content and form commitment.
Details
- Skill name
hero-section-diagnosis- Repository
- mardab96/landing-pages-claude-skills
- Path
hero-section-diagnosis/SKILL.md- License
- MIT
- Repo updated
- 30 July 2026
FAQ
What does the Hero Section Diagnosis skill do?
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.
How do I install the Hero Section Diagnosis skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add mardab96/landing-pages-claude-skills --skill hero-section-diagnosis. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Hero Section Diagnosis popular?
It lives in mardab96/landing-pages-claude-skills, which has 9 GitHub stars and 3 forks.
Related skills
Above the Fold Clarity Review
9mardab96/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.
Accessibility Conversion Blocker Check
9mardab96/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.
Comparison Page Positioning Review
9mardab96/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.
Mobile Conversion Review
9mardab96/landing-pages-claude-skills
Diagnoses what breaks on a phone specifically: thumb reach, viewport competition, tap targets, keyboard behaviour and scroll cost. Use when the mobile conversion rate sits well below desktop and the layout is nominally responsive.
Form Friction Finder
9mardab96/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.
Page Speed Impact Review
9mardab96/landing-pages-claude-skills
Turns speed measurements into a conversion priority instead of a scoreboard, and says which specific asset to fix first. Use when a speed report has been run and nobody knows whether any of it is worth the engineering time.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.