Individual skill
offer-design
Use when deciding what a buyer receives, why it solves their problem, and which promises, extras and conditions the seller can support. Produces an evidence-backed offer brief. NOT setting price levels (that is `pricing`) or writing the page (that is `landing-copy`).
skills/offer-design/SKILL.md
Source commit d9d6bb338f66cc1e23998585e580a0ea45bbcb82
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 561
- Repository last updated
- Nov 4, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- agentic-ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- claude-code Repository topic
- cli Repository topic
- cline Repository topic
- codex Repository topic
- coding-assistant Repository topic
- cursor Repository topic
- offer Declared skill tag
- value-proposition Declared skill tag
- differentiation Declared skill tag
- guarantee Declared skill tag
- deliverables Declared skill tag
- commercial-terms Declared skill tag
- design Derived category
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,439 bytesSKILL.mdcore · 7,439 bytesSKILL.mdcore · 7,439 bytesevals/README.mddoc · 2,377 bytesevals/cases.yamlasset · 4,650 bytes
Read excerpt
# Offer design — a promise the business can fulfill
Define the exchange between seller and buyer before expressing it in a landing or video. An offer can be a paid service, a product, a trial or a free tool. Respect the actual business model; a free project does not need an invented price, bonus or refund promise.
## Read the facts once
Load existing buyer research, product facts, approved terms and campaign artifacts. Identify the buyer's desired result, the current alternative, available proof and delivery constraints. Missing buyer evidence goes to `customer-research`; choosing price levels, tiers and margin floors goes to `pricing`. You can draft around an unknown, but mark it as proposed or unresolved.
Use the user's approved price and conditions. Never replace them because a template favors a different offer. If two artifacts disagree, identify their revisions and resolve the conflict from owner-approved terms; otherwise ask which is authoritative before treating either as settled.
For an authorized saved campaign, reuse its location or write `02-DOCS/wiki/marketing/<campaign>/offer.md`, linked from `02-DOCS/wiki/index.md`. Give the offer a stable ID and revision, with the research revision it consumes. Analysis-only requests stay in the response.
## Construct the promise from delivery outward
