scarcity-urgency
Skill32 starsChanged 8 months agoMITView on GitHub
Generate ethical scarcity and urgency elements for DTC offers — genuine limited stock, time-limited pricing, bonus deadlines, seasonal relevance, and enrollment caps with copy, visual treatment, and ethical justification.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Zenobia0000/dtc-copywriting-skillsedited, first seen Mar 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- Zenobia0000/dtc-copywriting-skills★ 460% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository41 other files it gives its agents.
- ab-test-planSkill
- ad-angle-generatorSkill
- ad-creative-auditSkill
- advertorial-writerSkill
- bonus-stackSkill
- broadcast-emailSkill
- cart-abandonment-flowSkill
- checkout-abandonmentSkill
- competitor-offer-analysisSkill
- copy-rewriteSkill
- creative-briefSkill
- email-promoSkill
- email-retention-sequencesSkill
- fb-ad-copySkill
- free-offer-briefSkill
- funnel-architectureSkill
- funnel-auditSkill
- guarantee-writerSkill
- hook-batterySkill
- ingredient-researchSkill
- lander-copySkill
- lead-writerSkill
- mechanism-ideationSkill
- media-buying-briefSkill
- offer-stackSkill
- order-form-croSkill
- pdp-ecomm-templateSkill
- post-purchase-sequenceSkill
- pricing-strategySkill
- reengagement-sequenceSkill
- rmbc-contextSkill
- rmbc-copy-auditSkill
- soap-opera-sequenceSkill
- thank-you-pageSkill
- ugc-briefSkill
- unified-research-synthesizerSkill
- upsell-scriptSkill
- upsell-sequence-writerSkill
- vsl-scriptSkill
- webinar-registration-copySkill
- welcome-sequenceSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 7 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
Before writing any copy, verify the scarcity is genuine:
- Distinctive: line 73
If the scarcity type is borderline or the user has no genuine scarcity, recommend these ethical alternatives:
- Distinctive: line 152
Every scarcity claim must pass the ethical validation — no fabricated urgency, ever
- Distinctive: line 153
If scarcity cannot be verified as genuine, the skill must say so explicitly and offer alternatives
- Distinctive: line 160
Specificity gate: Every claim in the copy must include a number, name, or timeframe — no "get results" or "improve your business"
- Distinctive: line 161
Mechanism quantification: When referencing the mechanism, include at least one specific data point (number, timeframe, study reference)
- Distinctive: line 163
Proof diversity: Use at least 2 different proof types (testimonial, statistical, authority, case study) — do not rely on a single proof mode
- Very specific: line 168
Run /order-form-cro to integrate scarcity elements into checkout pages
- Very specific: line 169
Run /lander-copy to weave urgency into the full sales page
- Very specific: line 170
Run /offer-stack to ensure the offer itself justifies the urgency
- Very specific: line 171
Run /pricing-strategy to develop the pricing that scarcity protects
- Very specific: line 172
Run /broadcast-email to write deadline-driven promotional emails
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
scarcity-urgency
Purpose
Generate ethical scarcity and urgency elements for DTC offers. Scarcity and urgency are the two most powerful conversion accelerators in direct response — and the two most abused. Fake countdown timers, fabricated "only 3 left" claims, and phantom deadlines destroy trust and invite chargebacks. This skill produces scarcity/urgency elements that are genuinely true, ethically defensible, and conversion-effective. Every element includes copy text, visual treatment guidance, and an ethical justification proving the scarcity is real. If the scarcity isn't real, the skill says so and recommends alternatives.
Inputs
| Input | Required | Description |
offer_description | Yes | The product/service, price, and what the prospect gets |
scarcity_type | Yes | One of: limited_stock, time_limited, bonus_deadline, seasonal, enrollment_cap |
deadline | No | Specific date/time if applicable (e.g., "March 31, 2026 at midnight") |
inventory_count | No | Actual remaining inventory or enrollment slots (must be truthful) |
target_audience | Yes | Who the prospect is — awareness level and sophistication matter for scarcity framing |
Execution Protocol
Step 1 — Load Framework Context
Read rmbc-context/SKILL.md to load RMBC framework definitions. Scarcity and urgency sit at the CTA layer of RMBC — they answer "why now?" after the mechanism answers "why this?" and proof answers "why believe?" Without a strong mechanism and proof foundation, urgency feels manipulative. With them, urgency feels like helpful information.
Step 2 — Validate the Scarcity Claim
Before writing any copy, verify the scarcity is genuine:
| Scarcity Type | Genuine When | Fabricated When |
| Limited Stock | Physical inventory has actual production/supply constraints | Digital product with "only 47 left" |
| Time-Limited Pricing | Price genuinely increases after deadline (and stays increased) | Countdown resets on page refresh |
| Bonus Deadline | Bonus is genuinely removed after date (and doesn't come back) | Bonus "expires" but is offered again next week |
| Seasonal | Offer tied to real calendar event, season, or market cycle | "Summer sale" in February |
| Enrollment Cap | Genuine capacity limit — coaching seats, cohort size, bandwidth | Artificial cap on a digital course with no interaction |
If the scarcity claim cannot be ethically justified, STOP. Output an honest assessment and recommend an alternative urgency approach (see Step 3 alternatives).
Step 3 — Generate Scarcity Elements
For the validated scarcity type, produce three elements at different intensity levels:
Soft (Informational)
- States the scarcity as a fact without pressure
- Tone: helpful, matter-of-fact
- Best for: high-awareness, sophisticated audiences who resist hard sells
Medium (Motivational)
- States the scarcity with consequence framing — what happens if they miss it
- Tone: direct, clear stakes
- Best for: mid-awareness audiences who need a reason to act today vs. "someday"
Strong (Urgent)
- States the scarcity with specific numbers, countdown, and immediate consequence
- Tone: time-sensitive, concrete
- Best for: ready-to-buy prospects who need a final nudge, not more persuasion
For each intensity level, provide:
- Headline/Banner Copy — The primary scarcity statement (1 line)
- Supporting Copy — Context that makes the scarcity believable (2-3 sentences)
- Visual Treatment — How to display it on the page (banner, badge, inline text, countdown)
- Placement — Where on the page this element belongs (above fold, near CTA, in cart)
- Ethical Justification — Why this claim is truthful and defensible
Step 4 — Recommend Alternatives (If Scarcity Is Weak)
If the scarcity type is borderline or the user has no genuine scarcity, recommend these ethical alternatives:
| Alternative | How It Works | Example |
| Loss aversion framing | Frame the cost of NOT buying (ongoing problem cost) | "Every month without this, you're losing $X to..." |
| Momentum urgency | The sooner they start, the sooner they see results | "Start today, see your first results by [date]" |
| Social proof velocity | Show how many people are buying/joining right now | "147 people joined this week" (if true) |
| Decision fatigue | Position buying as the END of their search, not a new commitment | "Stop researching — this is the solution" |
| Seasonal relevance | Connect to a real upcoming event or season | "Get ready before summer" (if it's spring) |
Step 5 — Assemble the Scarcity Stack
Combine elements into a recommended page implementation:
- Primary placement — The single most impactful scarcity element and where it goes
- Reinforcement — A secondary mention that echoes the scarcity without repeating the same copy
- CTA integration — How the scarcity language integrates into the call-to-action button and surrounding copy
- Email/ad echo — How to reference the same scarcity in ads and emails driving to the page (must match exactly — mismatched urgency kills trust)
Output Format
## Scarcity & Urgency: [Offer Name]
**Scarcity Type:** [type]
**Deadline:** [date/time or "ongoing"]
**Inventory:** [count or "N/A"]
**Ethical Status:** VERIFIED / BORDERLINE / NOT GENUINE
---
### SOFT (Informational)
**Banner:** "[copy]"
**Supporting:** [2-3 sentences]
**Visual:** [treatment]
**Placement:** [location]
**Ethics:** [justification]
---
### MEDIUM (Motivational)
**Banner:** "[copy]"
**Supporting:** [2-3 sentences]
**Visual:** [treatment]
**Placement:** [location]
**Ethics:** [justification]
---
### STRONG (Urgent)
**Banner:** "[copy]"
**Supporting:** [2-3 sentences]
**Visual:** [treatment]
**Placement:** [location]
**Ethics:** [justification]
---
### SCARCITY STACK (Recommended Implementation)
| Element | Location | Copy |
|---------|----------|------|
| Primary | [placement] | [copy] |
| Reinforcement | [placement] | [copy] |
| CTA integration | [button area] | [copy] |
| Email/ad echo | [subject line + preview] | [copy] |
---
### ALTERNATIVES (if applicable)
[Ethical alternatives if primary scarcity is weak]Quality Criteria
- Every scarcity claim must pass the ethical validation — no fabricated urgency, ever
- If scarcity cannot be verified as genuine, the skill must say so explicitly and offer alternatives
- Three intensity levels must be genuinely different in tone and approach — not the same copy with more exclamation marks
- Visual treatment must be specific and implementable — "add urgency" is not guidance
- Placement must account for mobile-first layout — scarcity elements must be visible without scrolling past the CTA
- CTA integration must feel natural — bolted-on urgency next to a calm CTA creates cognitive dissonance
- Email/ad scarcity must match page scarcity exactly — mismatched deadlines or claims destroy credibility
- Specificity gate: Every claim in the copy must include a number, name, or timeframe — no "get results" or "improve your business"
- Mechanism quantification: When referencing the mechanism, include at least one specific data point (number, timeframe, study reference)
- Audience journey: The copy must reference where the reader IS (what they've tried, what's failing) — not just who they are demographically
- Proof diversity: Use at least 2 different proof types (testimonial, statistical, authority, case study) — do not rely on a single proof mode
- Objection handling: The copy must address at least 2 likely objections with concrete responses (ROI math, proof of similar result, risk reversal)
Related Skills
- Run
/order-form-croto integrate scarcity elements into checkout pages - Run
/lander-copyto weave urgency into the full sales page - Run
/offer-stackto ensure the offer itself justifies the urgency - Run
/pricing-strategyto develop the pricing that scarcity protects - Run
/broadcast-emailto write deadline-driven promotional emails - Validate the full page with
/rmbc-copy-audit
Attribution
Generated using RMBC framework by Stefan Georgi. Learn more: copyaccelerator.com/join
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

