lvtd-llc/skills

eighty-twenty-usp-guarantee

Create 80/20-style unique selling propositions, guarantees, and result-based offers. Use when positioning an offer, strengthening a value proposition, raising prices, creating a guarantee, or making a sales promise more specific and credible.

First seen Jun 21, 2026

Installation

$ npx skills add lvtd-llc/skills --skill eighty-twenty-usp-guarantee

Also in this package

Other skills from lvtd-llc/skills · top by installs.

npx skills add lvtd-llc/skills

Browse all from lvtd-llc/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version0.1.0
LicenseMIT
CompatibilityCodex, Claude Code, and other Agent Skills-compatible clients.
Declared agents claude-code codex
More metadata
version
0.1.0
displayName
80/20 USP Guarantee
category
Marketing
tags
eighty-twenty,positioning,offers,guarantees,sales

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,854 B
  • docs SUMMARY.md 277 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 57 installs

SKILL.md

80/20 USP Guarantee

Use this skill to turn vague positioning into a specific promise for a specific buyer under specific conditions. It is based on 80/20 Sales and Marketing by Perry Marshall.

Source Traceability

Primary source: 80/20 Sales and Marketing, chapters 8 and 13.

  • Chapter 8 covers business and personal unique selling propositions.
  • Chapter 13 covers result-based selling, power guarantees, and premium offers.

Workflow

1. Clarify The Buyer And Result

Capture:

  • Buyer type.
  • Current state.
  • Desired result.
  • Time horizon.
  • Constraints.
  • Proof the seller can credibly claim.

The USP should not try to persuade everyone. It should make the right buyer feel seen and the wrong buyer opt out.

2. Separate Procedure From Result

List what the seller does, then translate it into what the buyer gets.

Ask:

  • What outcome does the buyer actually pay for?
  • What risk does the buyer want removed?
  • What result could be guaranteed under clear conditions?
  • What buyer commitments are required for the result?

3. Build The Power USP

Use this structure:

  • If you are [qualified buyer].
  • And you commit [requirements].
  • Then you will achieve [specific result].
  • Or else [seller penalty, refund, extra work, or other meaningful remedy].

Keep the penalty real enough to signal confidence, but bounded enough to be operationally safe.

4. Stress Test The Guarantee

Check:

  • Is the buyer qualified tightly enough?
  • Are buyer responsibilities explicit?
  • Is the result measurable?
  • Is the remedy meaningful?
  • Could fulfillment actually support this promise?

Output Format

# USP And Guarantee

## Buyer And Result
- Qualified buyer:
- Desired result:
- Time horizon:
- Required buyer commitments:

## Procedure To Result Translation
| Seller Activity | Buyer Result | Proof |
|-----------------|--------------|-------|

## Power USP Draft
[If buyer + commitment, then result, or remedy.]

## Risk Controls
- Qualification rule:
- Buyer responsibilities:
- Exclusions:
- Operational constraint:

Quality Bar

  • Do not write a USP that applies to everyone.
  • Do not guarantee a result without buyer commitments.
  • Do not confuse deliverables with outcomes.
  • Make the remedy specific.
  • Flag operational risk before recommending a bold guarantee.