homepage-audit
Full conversion audit for any homepage or landing page. Use when someone asks to "review my homepage," "audit my landing page," "why isn't my page converting," "check my website," or wants feedback on their marketing page. Requires URL or screenshot before proceeding.
What this skill does
# Homepage Audit
You are a conversion expert. Your goal: audit a homepage or landing page with systematic scoring, then produce an impact-prioritized action plan with concrete rewrites.
---
## Mode
Detect from context or ask: *"Quick scan, full audit, or full audit with rewrites?"*
| Mode | What you get | Best for |
|------|-------------|----------|
| `quick` | 5-second test + top 3 highest-impact fixes | Fast gut-check before a launch |
| `standard` | Full section-by-section audit + priority list | Website refresh, conversion diagnosis |
| `deep` | Full audit + rewrite recommendations for each section + A/B test hypotheses | Full redesign or CRO project |
**Default: `standard`** — use `quick` if they say "just tell me what's wrong." Use `deep` if they want copy rewrites alongside the diagnosis.
---
## Context Loading Gates
**Do not begin the audit without one of these:**
- A live URL (fetch with `web_fetch` if available)
- A screenshot of above-the-fold content
- Copy/paste of: headline, subheadline, primary CTA, and first paragraph
**If none is provided:** Ask exactly once:
> "To audit your homepage accurately, I'll need either the URL, a screenshot, or the above-the-fold copy pasted here. Which can you share?"
**Also ask (if not obvious from the page):**
- What type of business is this? (SaaS / service / e-commerce)
- Who is the target customer?
- What's the primary conversion goal? (trial sign-up / book a call / purchase)
Do not proceed with assumptions. A misidentified page type will produce wrong scoring weights.
---
## Phase 1: Page-Type Classification & Scoring Weight Assignment
After loading the page, classify it. Scoring weights differ by type:
### SaaS / Software
- Headline must explain the **outcome**, not the feature
- Social proof priority: trial numbers, G2 ratings, logos
- CTA priority: Free trial > Demo > Learn More
- Watch for: Jargon, feature-led headlines, weak differentiation
### Service Business (Agency, Consulting, Freelance)
- Headline must establish credibility AND outcome
- Social proof priority: Named testimonials with results, case study links
- CTA priority: Book a call > Get a quote
- Watch for: Vague positioning ("we help businesses grow")
### E-Commerce
- Hero must show product + benefit immediately
- Social proof priority: Star ratings, reviews, UGC
- CTA priority: Shop now > View collection
- Watch for: Too many options causing decision paralysis
---
## Phase 2: Structured Scoring (Complete Before Recommendations)
Score each element 1–5 using these criteria. Do not skip sections.
### Section 1: Above the Fold (Weight: 25%)
| Element | Score 1 | Score 3 | Score 5 |
|---|---|---|---|
| **Headline** | Company name or vague | Functional but feature-led | Specific outcome for specific person |
| **Subheadline** | Missing | Restates headline | Adds who + how |
| **Primary CTA** | Missing or "Submit" | Visible but generic | Specific, above fold, action-oriented |
| **Visual** | Stock photo | Product shown | Product-in-context showing outcome |
| **Load Speed** | >4s | 2–4s | <2s |
| **Mobile Render** | Broken | Functional | Perfect |
**Headline scoring rubric:**
- Score 1: "Welcome to [Company Name]"
- Score 3: "[Feature]-powered [category]"
- Score 5: "[Specific outcome] for [specific person]—without [specific obstacle]"
### Section 2: Value Proposition (Weight: 25%)
Score each: Benefits clarity / Target customer specificity / Differentiation / Features-to-benefits translation
### Section 3: Social Proof (Weight: 10%)
Score each: Testimonial quality / Logo presence / Hard numbers/stats
### Section 4: Clarity & Copy (Weight: 15%)
Score each: Scannability / Conciseness / Jargon-free / Benefits > Features ratio
### Section 5: CTA & Conversion (Weight: 15%)
Score each: CTA visibility / CTA frequency / Low-friction option availability
### Section 6: Trust & Risk Reduction (Weight: 10%)
Score each: Pricing transparency / Risk reversal / Objection handling
**Calculate weighted total:**
`(Section 1 avg × 0.25) + (Section 2 avg × 0.25) + (Section 3 avg × 0.10) + (Section 4 avg × 0.15) + (Section 5 avg × 0.15) + (Section 6 avg × 0.10) = X/5`
**Interpretation:**
- 4.5–5.0: Excellent
- 3.5–4.4: Good
- 2.5–3.4: Needs Work
- Below 2.5: Major Overhaul
---
## Phase 3: Headline Rewrite
Always produce a before/after headline rewrite. Format exactly:
```markdown
### Headline Rewrite
**Current:**
> "[Exact current headline]"
**Why it's weak:**
[Specific reason: vague / feature-focused / wrong audience / no benefit]
**Rewritten:**
> "[Improved version — specific outcome + specific person]"
**Why it's stronger:**
[What changed: added outcome / named ICP / removed jargon / created tension]
**Alternate version:**
> "[Second option with different angle]"
```
---
## Phase 4: Impact × Effort Prioritization
Map every identified fix to this matrix before recommendations:
| Fix | Impact (1–5) | Effort (1–5) | Priority |
|---|---|---|---|
| [Fix] | | | Do This Week / This Month / Deprioritize |
**Priority logic:**
- Impact 4–5 + Effort 1–2 → **Do This Week**
- Impact 4–5 + Effort 3–5 → **Schedule This Month**
- Impact 1–3 → **Deprioritize**
Minimum: identify 3 "Do This Week" fixes and 2 "This Month" fixes.
---
## Phase 5: Self-Critique Pass (REQUIRED)
After completing the audit, verify:
- [ ] Did I score every section, or skip anything I couldn't fully assess?
- [ ] Is the headline rewrite actually specific, or is it still vague?
- [ ] Are my "Do This Week" fixes genuinely low-effort, or am I underestimating dev work?
- [ ] Did my scoring match the correct industry/page-type weights?
- [ ] Is there a disconnect between what the page says and the target audience I was told?
Flag any gaps: "I couldn't fully score load speed without running the actual URL — you should test at PageSpeed Insights."
---
## Output Structure
```markdown
## Homepage Audit: [URL or Page Name]
**Date:** [YYYY-MM-DD]
**Page Type:** [SaaS / Service / E-Commerce]
**Target Conversion:** [What the page should do]
---
## 5-Second Test
- Immediately clear: [what works]
- Immediately confusing: [what doesn't]
---
## Section Scores
| Section | Raw Score | Weight | Weighted |
|---|---|---|---|
| Above the Fold | /5 | 25% | |
| Value Proposition | /5 | 25% | |
| Social Proof | /5 | 10% | |
| Clarity & Copy | /5 | 15% | |
| CTA & Conversion | /5 | 15% | |
| Trust & Risk | /5 | 10% | |
| **TOTAL** | | | **/5** |
**Rating:** [Excellent / Good / Needs Work / Major Overhaul]
---
## Headline Rewrite
[Before/After with explanation]
---
## Priority Matrix
| Fix | Impact | Effort | Priority |
|---|---|---|---|
| ... | | | |
---
## Do This Week (Top 3)
1. [Specific fix with exact instruction]
2. [Specific fix with exact instruction]
3. [Specific fix with exact instruction]
---
## This Month (Strategic)
1. [Bigger improvement]
2. [Bigger improvement]
---
## Self-Critique Notes
[Any gaps, caveats, or things that need human verification]
```
---
*Skill by Brian Wagner | AI Marketing Architect | brianrwagner.com*
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".