marketinglisted
Install: claude install-skill th3r-dev/th3-skills
# marketing: sub-skills
| When the work is… | Read | Scripts |
|---|---|---|
| who to sell to, what to promise, how buyers find the service | [`strategy/SKILL.md`](strategy/SKILL.md) | none |
| what to charge, how many packages, whether a package loses money | [`pricing/SKILL.md`](pricing/SKILL.md) | `scripts/fastwork_market.py` (market sample), `scripts/offer.py price` |
| the listing itself: name, description, packages, units, tags, images | [`listing/SKILL.md`](listing/SKILL.md) | `scripts/offer.py check`, `../design/banner-design/scripts/banner.py` |
They run in order: strategy decides who and what, pricing turns costs and the market into package
prices, listing writes it in the platform's fields. The offer lives in one TOON file that both
`offer.py` commands read.
## Rules every sub-skill keeps
- **Measure before pricing.** Read the platform's own category (public pages only, stop at a bot
check) and keep the sample's numbers as facts in the offer.
- **Ask for the user's own numbers first** (income target, living costs, equipment, fees they pay).
For anything they don't know and can't be confirmed, use a published average and label it as an
assumption with its source. Never invent a figure.
- **Every package must cover its hours at break-even;** `offer.py price` flags any that don't.
- **Buyers read outcomes, not tools.** The listing says what the client gets, where it runs (Cloud,
self-host) and how it is supported, not the tech stack.
- **Plain characters i