bundles/startup/skills/offer-validator/SKILL.md
Validate existing offers using Hormozi's Value Equation. Scores offers, exposes weaknesses, and provides actionable fixes. Activates for "validate my offer," "rate my offer," or "is my offer good."
npx skillsauth add shipshitdev/library offer-validatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Ruthlessly assess existing offers against Hormozi's Value Equation. Score them, expose weaknesses, and provide actionable fixes.
Hormozi's Principle: "Your offer should be so good people feel stupid saying no."
Your Role: Score the offer. Find the gaps. Prescribe the fixes.
Value = (Dream Outcome × Perceived Likelihood) / (Time Delay × Effort Required)
| Dimension | Weight | What It Measures | |-----------|--------|------------------| | Dream Outcome | 2x | How desirable is the promised result? | | Perceived Likelihood | 2x | How believable is it they'll achieve it? | | Time to Results | 1.5x | How fast will they see results? | | Effort Required | 1.5x | How much work do they have to do? | | Bonus Stack | 1x | Does value stack overwhelm with extras? | | Guarantee Strength | 1x | Is the risk completely removed? |
Max Score: 100 points
| Score | Rating | Verdict | |-------|--------|---------| | 85-100 | Grand Slam | Ready to scale. Minor optimizations only. | | 70-84 | Strong | Good foundation. Fix weak points, then launch. | | 55-69 | Decent | Significant gaps. Improve before scaling. | | 40-54 | Weak | Major issues. Rebuild key components. | | 0-39 | Broken | Start over. Fundamental problems. |
Ask:
| Skill | When to Use |
|-------|-------------|
| offer-architect | Rebuild weak components |
| copy-validator | Validate sales copy |
| funnel-validator | Validate entire funnel |
| pricing-strategist | Fix pricing issues |
For detailed scoring criteria, examples, and output templates: references/full-guide.md
development
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
testing
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
testing
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
development
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.