Loading source
Pulling the file list, source metadata, and syntax-aware rendering for this listing.
Source from repo
Creates and validates agent skills using Test-Driven Development — write test scenarios, baseline behavior, then the skill itself.
Files
Skill
Size
Entrypoint
Format
Open file
Syntax-highlighted preview of this file as included in the skill package.
persuasion-principles.md
1# Persuasion Principles for Skill Design23## Overview45LLMs respond to the same persuasion principles as humans. Understanding this psychology helps you design more effective skills - not to manipulate, but to ensure critical practices are followed even under pressure.67**Research foundation:** Meincke et al. (2025) tested 7 persuasion principles with N=28,000 AI conversations. Persuasion techniques more than doubled compliance rates (33% → 72%, p < .001).89## The Seven Principles1011### 1. Authority12**What it is:** Deference to expertise, credentials, or official sources.1314**How it works in skills:**15- Imperative language: "YOU MUST", "Never", "Always"16- Non-negotiable framing: "No exceptions"17- Eliminates decision fatigue and rationalization1819**When to use:**20- Discipline-enforcing skills (TDD, verification requirements)21- Safety-critical practices22- Established best practices2324**Example:**25```markdown26✅ Write code before test? Delete it. Start over. No exceptions.27❌ Consider writing tests first when feasible.28```2930### 2. Commitment31**What it is:** Consistency with prior actions, statements, or public declarations.3233**How it works in skills:**34- Require announcements: "Announce skill usage"35- Force explicit choices: "Choose A, B, or C"36- Use tracking: TodoWrite for checklists3738**When to use:**39- Ensuring skills are actually followed40- Multi-step processes41- Accountability mechanisms4243**Example:**44```markdown45✅ When you find a skill, you MUST announce: "I'm using [Skill Name]"46❌ Consider letting your partner know which skill you're using.47```4849### 3. Scarcity50**What it is:** Urgency from time limits or limited availability.5152**How it works in skills:**53- Time-bound requirements: "Before proceeding"54- Sequential dependencies: "Immediately after X"55- Prevents procrastination5657**When to use:**58- Immediate verification requirements59- Time-sensitive workflows60- Preventing "I'll do it later"6162**Example:**63```markdown64✅ After completing a task, IMMEDIATELY request code review before proceeding.65❌ You can review code when convenient.66```6768### 4. Social Proof69**What it is:** Conformity to what others do or what's considered normal.7071**How it works in skills:**72- Universal patterns: "Every time", "Always"73- Failure modes: "X without Y = failure"74- Establishes norms7576**When to use:**77- Documenting universal practices78- Warning about common failures79- Reinforcing standards8081**Example:**82```markdown83✅ Checklists without TodoWrite tracking = steps get skipped. Every time.84❌ Some people find TodoWrite helpful for checklists.85```8687### 5. Unity88**What it is:** Shared identity, "we-ness", in-group belonging.8990**How it works in skills:**91- Collaborative language: "our codebase", "we're colleagues"92- Shared goals: "we both want quality"9394**When to use:**95- Collaborative workflows96- Establishing team culture97- Non-hierarchical practices9899**Example:**100```markdown101✅ We're colleagues working together. I need your honest technical judgment.102❌ You should probably tell me if I'm wrong.103```104105### 6. Reciprocity106**What it is:** Obligation to return benefits received.107108**How it works:**109- Use sparingly - can feel manipulative110- Rarely needed in skills111112**When to avoid:**113- Almost always (other principles more effective)114115### 7. Liking116**What it is:** Preference for cooperating with those we like.117118**How it works:**119- **DON'T USE for compliance**120- Conflicts with honest feedback culture121- Creates sycophancy122123**When to avoid:**124- Always for discipline enforcement125126## Principle Combinations by Skill Type127128| Skill Type | Use | Avoid |129|------------|-----|-------|130| Discipline-enforcing | Authority + Commitment + Social Proof | Liking, Reciprocity |131| Guidance/technique | Moderate Authority + Unity | Heavy authority |132| Collaborative | Unity + Commitment | Authority, Liking |133| Reference | Clarity only | All persuasion |134135## Why This Works: The Psychology136137**Bright-line rules reduce rationalization:**138- "YOU MUST" removes decision fatigue139- Absolute language eliminates "is this an exception?" questions140- Explicit anti-rationalization counters close specific loopholes141142**Implementation intentions create automatic behavior:**143- Clear triggers + required actions = automatic execution144- "When X, do Y" more effective than "generally do Y"145- Reduces cognitive load on compliance146147**LLMs are parahuman:**148- Trained on human text containing these patterns149- Authority language precedes compliance in training data150- Commitment sequences (statement → action) frequently modeled151- Social proof patterns (everyone does X) establish norms152153## Ethical Use154155**Legitimate:**156- Ensuring critical practices are followed157- Creating effective documentation158- Preventing predictable failures159160**Illegitimate:**161- Manipulating for personal gain162- Creating false urgency163- Guilt-based compliance164165**The test:** Would this technique serve the user's genuine interests if they fully understood it?166167## Research Citations168169**Cialdini, R. B. (2021).** *Influence: The Psychology of Persuasion (New and Expanded).* Harper Business.170- Seven principles of persuasion171- Empirical foundation for influence research172173**Meincke, L., Shapiro, D., Duckworth, A. L., Mollick, E., Mollick, L., & Cialdini, R. (2025).** Call Me A Jerk: Persuading AI to Comply with Objectionable Requests. University of Pennsylvania.174- Tested 7 principles with N=28,000 LLM conversations175- Compliance increased 33% → 72% with persuasion techniques176- Authority, commitment, scarcity most effective177- Validates parahuman model of LLM behavior178179## Quick Reference180181When designing a skill, ask:1821831. **What type is it?** (Discipline vs. guidance vs. reference)1842. **What behavior am I trying to change?**1853. **Which principle(s) apply?** (Usually authority + commitment for discipline)1864. **Am I combining too many?** (Don't use all seven)1875. **Is this ethical?** (Serves user's genuine interests?)188