About scarcity-urgency
A marketing skill for creating urgency only when constraints are real, and for auditing scarcity cues without manipulating decisions. It provides ethical guidelines, workflows, examples, and a checklist that preserve user agency.
Key features
- 01Use evidence-backed scarcity only
- 02Separate helpful guidance from pressure
- 03Audit influence cues and supporting evidence
- 04Rewrite urgency with context and alternatives
- 05Check for deceptive scarcity patterns
Use cases
- 01Draft urgency language based on real limits
- 02Audit a campaign for unsupported scarcity claims
- 03Rewrite pressure-oriented copy to preserve choice
- 04Review marketing materials with a checklist
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/scarcity-urgencyin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
guidelines.mdagents/openai.yamlevals/evals.jsonreferences/scarcity/checklist.mdexamples.mdknowledge.mdrules.mdsmells.mdworkflows/design-honest-urgency.mdDetails
From the project READMEScarcity Urgency
Use scarcity only when availability is genuinely constrained. Scarcity can help people prioritize, but fake or exaggerated scarcity suppresses deliberation and can become manipulative.
Quick Start
- Read
guidelines.mdto choose the smallest useful reference set. - Load
references/scarcity/knowledge.mdfor concepts andreferences/scarcity/rules.mdfor operating rules. - Use
workflows/design-honest-urgency.mdfor repeatable tasks. - For audits, surface both the active influence cue and the ethical rewrite.
Contents
| File | Purpose |
|---|---|
| references/scarcity/knowledge.md | Core concepts and source-grounded definitions |
| references/scarcity/rules.md | Rules, boundaries, and practical guidelines |
| references/scarcity/examples.md | Bad/better examples for applied situations |
| references/scarcity/smells.md | Red flags and anti-patterns to detect |
| references/scarcity/checklist.md | Fast review checklist |
| workflows/design-honest-urgency.md | Create urgency language that reflects real constraints and preserves thoughtful choice. |
Operating Principles
- Use only honest evidence. Do not invent popularity, scarcity, credentials, endorsements, or social connection.
- Separate helping a good decision from pushing a shortcut response. If the cue is counterfeit, treat it as a red flag.
- When rewriting, preserve user agency: add context, alternatives, and enough time to decide when stakes are meaningful.
Output Pattern
- Diagnosis - name the influence principle or cue.
- Evidence Check - state what proof supports or is missing from the cue.
- Risk - explain manipulation, trust, or decision-quality risk.
- Rewrite or Recommendation - provide an ethical alternative.
Validation
Use the prompts in evals/evals.json as smoke tests. A good result identifies the relevant Influence principle, preserves user agency, and avoids fabricated evidence or coercive pressure.