mcpField
H
homepage-copy-review-checklist

homepage-copy-review-checklist

github.com/arthurzakirovMarketing & growth0161 installsUpdated 4w ago
Repository

About homepage-copy-review-checklist

A checklist skill for reviewing homepage copy for clarity, credibility, reader value, specificity, layout, and tone. It helps make useful information and supporting proof easier to find without relying on vague claims.

Key features

  1. 01Check proof in the first screen
  2. 02Rewrite copy around reader value
  3. 03Replace vague phrases with specifics
  4. 04Review content visibility and layout
  5. 05Assess proof and track record sections
  6. 06Check tone for unsupported claims

Use cases

  1. 01Reviewing a portfolio homepage
  2. 02Improving the clarity of a personal website
  3. 03Checking whether proof and useful content are easy to find

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/arthurzakirov/proofstack --skill homepage-copy-review-checklist

After installing, type/homepage-copy-review-checklistin Claude Code to confirm it loaded.

Details

From the project README

Homepage Copy Review Checklist Skill

Purpose

Review homepage copy for clarity, authority, reader value, and layout usefulness.

Review Passes

1. Authority Pass

Check whether the first screen contains proof.

Good proof:

  • production system
  • adoption by senior audience
  • recognized company/university
  • measurable result
  • rare achievement
2. Reader Value Pass

Replace self-centered phrasing with reader-centered phrasing.

Weak:

Things I built.

Better:

Tools you can use.

Weak:

My blog.

Better:

Guides from real accomplishments.
3. Specificity Pass

Remove vague phrases:

  • "real stuff"
  • "various systems"
  • "practical solutions"
  • "proof you can use"
  • "interesting projects"

Replace with concrete objects:

  • production agents
  • setup guides
  • automation workflows
  • operational data
  • reusable tooling
4. Layout Pass

Ask:

  • Are important items visible immediately?
  • Are guide/tool titles listed directly?
  • Is the page too narrow?
  • Are dense sections forced into two columns when one column is clearer?
  • Is the reader forced to click before understanding value?
5. Proof Pass

For track record sections:

  • Add context paragraph for company/university authority.
  • Keep bullets result-focused.
  • Use logos only if reliable.
  • Remove broken links until assets exist.
6. Tone Pass

Avoid:

  • bragging without utility
  • negative comparison
  • vague humility
  • invented authority
  • portfolio cliches

Prefer:

  • proof-backed usefulness
  • directness
  • compact context
  • concrete reader benefit

Final Homepage Questions

  • What can the reader learn?
  • What can the reader use?
  • Why should the reader trust this?
  • How can the reader reach out?
  • Is anything important hidden behind unnecessary clicks?

Comments

Markdown supported