agentleFS
fjilvvifjilvvi/growthlens/skills/positioning-messaging-audit/SKILL.md

positioning-messaging-audit

Skill2 starsChanged 5 months agoMITView on GitHub

Audit a company's positioning and messaging from its homepage and key pages — category, target customer, unique value, the message hierarchy, clarity, and differentiation — and rewrite the weak parts. Use when the user asks to "audit our messaging", "is our positioning clear", "review our homepage copy", "what's our value proposition", or shares a site and wants the positioning critiqued and sharpened.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user wants a rewrite, ask for the one outcome they most want a visitor to feel.

    line 41
  2. Distinctive:

    Call out say/do gaps (claims the rest of the page doesn't back up).

    line 108

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Positioning & Messaging Audit

Find out whether a site's message is clear, differentiated, and aimed at the right buyer — then sharpen it.

What it does

Evaluates positioning (the strategic choice of category, audience, and differentiator) and messaging (how that choice is expressed on the page). It scores clarity and differentiation, maps the message hierarchy, and rewrites the weakest hero and value-prop copy.

When to use this skill

  • "Audit our positioning / messaging."
  • "Is our value proposition clear?"
  • "Review the homepage copy and tell me what's weak."
  • Comparing how two competitors position against each other.

Inputs needed

  • Required: the homepage URL (plus product/about pages if relevant).
  • Helpful: who the user thinks they're for, their main competitor, and what they believe their differentiator is — so you can flag say/do gaps.
  • If the user wants a rewrite, ask for the one outcome they most want a visitor to feel.

Method

  1. Capture the message as-is — copy the hero headline, subhead, primary CTA, and the top 3 value props verbatim.
  2. Apply the positioning frame (April Dunford-style):
    • Competitive alternatives — what does a customer use instead?
    • Unique attributes — what only this product has.
    • Value — what those attributes enable, that customers care about.
    • Best-fit customer — who cares most.
    • Category — the frame of reference the messaging sets.
  3. Run the 5-second clarity test — from the hero alone, can a stranger tell what it is, who it's for, and why it's better? Grade each.
  4. Map the message hierarchy — does the page flow promise → proof → objection handling → CTA? Are the value props ordered by what the buyer cares about?
  5. Check differentiation — is the differentiator real and specific, or a commodity claim ("easy", "powerful", "all-in-one") any competitor could make?
  6. Score & rewrite — score clarity, differentiation, and audience-fit (1–5 each), then rewrite the hero and the weakest value prop.

Output format

# Positioning & Messaging Audit — <Company>

## TL;DR
- Clarity __/5 · Differentiation __/5 · Audience-fit __/5
- The single biggest message problem.

## Current message (verbatim)
- Hero headline / subhead / CTA:
- Top value props:

## Positioning read
| Element | Finding |
|---------|---------|
| Competitive alternatives | |
| Unique attributes | |
| Value delivered | |
| Best-fit customer | |
| Category framing | |

## 5-second clarity test
- What it is: ✅/⚠️/❌ —
- Who it's for: ✅/⚠️/❌ —
- Why it's better: ✅/⚠️/❌ —

## Message hierarchy
- Flow & ordering issues:

## Differentiation
- Real vs commodity claims:

## Rewrites
**Hero (before → after):**
**Weakest value prop (before → after):**

## Prioritized fixes
| # | Fix | Why | Impact | Effort |
|---|-----|-----|--------|--------|

Quality bar

  • Quote the current copy exactly before critiquing it.
  • Rewrites must be specific to this company — no swappable platitudes.
  • Call out say/do gaps (claims the rest of the page doesn't back up).
  • Differentiation verdicts must explain why a claim is or isn't ownable.

Common mistakes to avoid

  • Critiquing tone/grammar instead of the strategic message.
  • Rewriting to sound clever rather than clear.
  • Accepting a vague differentiator because it "sounds good".

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.