Homepage copy review checklist
Skill ArthurZakirov/ProofStack/skills/homepage-copy-review-checklist
Public-safe skills and schemas for turning private work evidence into career signal
npx -y skills add ArthurZakirov/ProofStack --skill homepage-copy-review-checklistAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Review homepage copy for clarity, authority, reader value, and layout usefulness.
SKILL.md
1.9 KB, as published. Nobody here has run it
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?