BC 100m-offers
Alex Hormozi's "$100M Offers: How To Make Offers So Good People Feel Stupid Saying No" — the complete framework for creating Grand Slam Offers that eliminate price comparison and multiply revenue 22x. Covers 5 use cases: ① Grand Slam Offer construction — ("how to make an irresistible offer" "grand slam offer" "value equation" "offer framework") ② Pricing strategy — ("charge more" "premium pricing" "stop competing on price" "raise your prices" "commodity problem") ③ Value Equation mastery — ("dream outcome" "perceived likelihood" "guarantee" "bonuses" "time delay" "effort sacrifice") ④ Offer enhancements — ("scarcity" "urgency" "guarantees" "stacking bonuses" "naming your offer") ⑤ Market selection — ("starving crowd" "niche selection" "right market" "high demand" "blue ocean") Trigger when users say: "100m offers" "Alex Hormozi" "how to price" "make an offer" "value proposition" "grand slam offer" "premium pricing" "charge what you're worth" "stop competing on price" "offer so good they can't say no" "Acquisition.com" "value equation"
Alex Hormozi's "$100M Offers: How To Make Offers So Good People Feel Stupid Saying No" — the complete framework for creating Grand Slam Offers that eliminate…
As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- Shorten the description to 1024 characters.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1050 chars, limit 1024
Process rating: all ten parameters 52/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 14 mutating operations with no state check
- 40Consistency. Frontmatter name (100m-offers) differs from the folder (100m-offers-v2)
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 34 steps
- 100Execution cost. Instruction body is 2207 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1050: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 38 example trigger phrases
- +4Structure: 8 headings
- +3Step-by-step instructions: 34 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (4 of 5)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.