Skill Tracer
Skills › Superpowers › writing-skills › persuasion-principles.md

persuasion-principles.md

187 lines · skills/writing-skills/references/persuasion-principles.md at 2ce8aa1

Open on GitHub
1# Persuasion Principles for Skill Design
2

Persuasion Principles for Skill Design

Raw lines 1 to 2
3## Overview
4
5LLMs 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.
6
7**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).
8

Overview

LLMs 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.

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).

Raw lines 3 to 8
9## The Seven Principles

The Seven Principles

Raw lines 9 to 10
11### 1. Authority
12**What it is:** Deference to expertise, credentials, or official sources.
14**How it works in skills:**
15- Imperative language: "YOU MUST", "Never", "Always"
16- Non-negotiable framing: "No exceptions"
17- Eliminates decision fatigue and rationalization
19**When to use:**
20- Discipline-enforcing skills (TDD, verification requirements)
21- Safety-critical practices
22- Established best practices
24**Example:**
25```markdown
26✅ Write code before test? Delete it. Start over. No exceptions.
27❌ Consider writing tests first when feasible.
28```

1. Authority

What it is: Deference to expertise, credentials, or official sources.

How it works in skills:

  • Imperative language: "YOU MUST", "Never", "Always"
  • Non-negotiable framing: "No exceptions"
  • Eliminates decision fatigue and rationalization

When to use:

  • Discipline-enforcing skills (TDD, verification requirements)
  • Safety-critical practices
  • Established best practices

Example:

✅ Write code before test? Delete it. Start over. No exceptions.
❌ Consider writing tests first when feasible.
Raw lines 11 to 29
30### 2. Commitment
31**What it is:** Consistency with prior actions, statements, or public declarations.
33**How it works in skills:**
34- Require announcements: "Announce skill usage"
35- Force explicit choices: "Choose A, B, or C"
36- Use tracking: todos for checklists
38**When to use:**
39- Ensuring skills are actually followed
40- Multi-step processes
41- Accountability mechanisms
43**Example:**
44```markdown
45✅ 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```

2. Commitment

What it is: Consistency with prior actions, statements, or public declarations.

How it works in skills:

  • Require announcements: "Announce skill usage"
  • Force explicit choices: "Choose A, B, or C"
  • Use tracking: todos for checklists

When to use:

  • Ensuring skills are actually followed
  • Multi-step processes
  • Accountability mechanisms

Example:

✅ When you find a skill, you MUST announce: "I'm using [Skill Name]"
❌ Consider letting your partner know which skill you're using.
Raw lines 30 to 48
49### 3. Scarcity
50**What it is:** Urgency from time limits or limited availability.
52**How it works in skills:**
53- Time-bound requirements: "Before proceeding"
54- Sequential dependencies: "Immediately after X"
55- Prevents procrastination
57**When to use:**
58- Immediate verification requirements
59- Time-sensitive workflows
60- Preventing "I'll do it later"
62**Example:**
63```markdown
64✅ After completing a task, IMMEDIATELY request code review before proceeding.
65❌ You can review code when convenient.
66```

3. Scarcity

What it is: Urgency from time limits or limited availability.

How it works in skills:

  • Time-bound requirements: "Before proceeding"
  • Sequential dependencies: "Immediately after X"
  • Prevents procrastination

When to use:

  • Immediate verification requirements
  • Time-sensitive workflows
  • Preventing "I'll do it later"

Example:

✅ After completing a task, IMMEDIATELY request code review before proceeding.
❌ You can review code when convenient.
Raw lines 49 to 67
68### 4. Social Proof
69**What it is:** Conformity to what others do or what's considered normal.
71**How it works in skills:**
72- Universal patterns: "Every time", "Always"
73- Failure modes: "X without Y = failure"
74- Establishes norms
76**When to use:**
77- Documenting universal practices
78- Warning about common failures
79- Reinforcing standards
81**Example:**
82```markdown
83✅ Checklists without todo tracking = steps get skipped. Every time.
84❌ Some people find a todo list helpful for checklists.
85```

4. Social Proof

What it is: Conformity to what others do or what's considered normal.

How it works in skills:

  • Universal patterns: "Every time", "Always"
  • Failure modes: "X without Y = failure"
  • Establishes norms

When to use:

  • Documenting universal practices
  • Warning about common failures
  • Reinforcing standards

Example:

✅ Checklists without todo tracking = steps get skipped. Every time.
❌ Some people find a todo list helpful for checklists.
Raw lines 68 to 86
87### 5. Unity
88**What it is:** Shared identity, "we-ness", in-group belonging.
90**How it works in skills:**
91- Collaborative language: "our codebase", "we're colleagues"
92- Shared goals: "we both want quality"
94**When to use:**
95- Collaborative workflows
96- Establishing team culture
97- Non-hierarchical practices
99**Example:**
100```markdown
101✅ We're colleagues working together. I need your honest technical judgment.
102❌ You should probably tell me if I'm wrong.
103```

5. Unity

What it is: Shared identity, "we-ness", in-group belonging.

How it works in skills:

  • Collaborative language: "our codebase", "we're colleagues"
  • Shared goals: "we both want quality"

When to use:

  • Collaborative workflows
  • Establishing team culture
  • Non-hierarchical practices

Example:

✅ We're colleagues working together. I need your honest technical judgment.
❌ You should probably tell me if I'm wrong.
Raw lines 87 to 104
105### 6. Reciprocity
106**What it is:** Obligation to return benefits received.
108**How it works:**
109- Use sparingly - can feel manipulative
110- Rarely needed in skills
112**When to avoid:**
113- Almost always (other principles more effective)

6. Reciprocity

What it is: Obligation to return benefits received.

How it works:

  • Use sparingly - can feel manipulative
  • Rarely needed in skills

When to avoid:

  • Almost always (other principles more effective)
Raw lines 105 to 114
115### 7. Liking
116**What it is:** Preference for cooperating with those we like.
118**How it works:**
119- **DON'T USE for compliance**
120- Conflicts with honest feedback culture
121- Creates sycophancy
123**When to avoid:**
124- Always for discipline enforcement

7. Liking

What it is: Preference for cooperating with those we like.

How it works:

  • DON'T USE for compliance
  • Conflicts with honest feedback culture
  • Creates sycophancy

When to avoid:

  • Always for discipline enforcement
Raw lines 115 to 125
126## Principle Combinations by Skill Type
128| 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 |

Principle Combinations by Skill Type

Skill TypeUseAvoid
Discipline-enforcingAuthority + Commitment + Social ProofLiking, Reciprocity
Guidance/techniqueModerate Authority + UnityHeavy authority
CollaborativeUnity + CommitmentAuthority, Liking
ReferenceClarity onlyAll persuasion
Raw lines 126 to 134
135## Why This Works: The Psychology
137**Bright-line rules reduce rationalization:**
138- "YOU MUST" removes decision fatigue
139- Absolute language eliminates "is this an exception?" questions
140- Explicit anti-rationalization counters close specific loopholes
142**Implementation intentions create automatic behavior:**
143- Clear triggers + required actions = automatic execution
144- "When X, do Y" more effective than "generally do Y"
145- Reduces cognitive load on compliance
147**LLMs are parahuman:**
148- Trained on human text containing these patterns
149- Authority language precedes compliance in training data
150- Commitment sequences (statement → action) frequently modeled
151- Social proof patterns (everyone does X) establish norms

Why This Works: The Psychology

Bright-line rules reduce rationalization:

  • "YOU MUST" removes decision fatigue
  • Absolute language eliminates "is this an exception?" questions
  • Explicit anti-rationalization counters close specific loopholes

Implementation intentions create automatic behavior:

  • Clear triggers + required actions = automatic execution
  • "When X, do Y" more effective than "generally do Y"
  • Reduces cognitive load on compliance

LLMs are parahuman:

  • Trained on human text containing these patterns
  • Authority language precedes compliance in training data
  • Commitment sequences (statement → action) frequently modeled
  • Social proof patterns (everyone does X) establish norms
Raw lines 135 to 152
153## Ethical Use
155**Legitimate:**
156- Ensuring critical practices are followed
157- Creating effective documentation
158- Preventing predictable failures
160**Illegitimate:**
161- Manipulating for personal gain
162- Creating false urgency
163- Guilt-based compliance
165**The test:** Would this technique serve the user's genuine interests if they fully understood it?

Ethical Use

Legitimate:

  • Ensuring critical practices are followed
  • Creating effective documentation
  • Preventing predictable failures

Illegitimate:

  • Manipulating for personal gain
  • Creating false urgency
  • Guilt-based compliance

The test: Would this technique serve the user's genuine interests if they fully understood it?

Raw lines 153 to 166
167## Research Citations
169**Cialdini, R. B. (2021).** *Influence: The Psychology of Persuasion (New and Expanded).* Harper Business.
170- Seven principles of persuasion
171- Empirical foundation for influence research
173**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 conversations
175- Compliance increased 33% → 72% with persuasion techniques
176- Authority, commitment, scarcity most effective
177- Validates parahuman model of LLM behavior

Research Citations

Cialdini, R. B. (2021). Influence: The Psychology of Persuasion (New and Expanded). Harper Business.

  • Seven principles of persuasion
  • Empirical foundation for influence research

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.

  • Tested 7 principles with N=28,000 LLM conversations
  • Compliance increased 33% → 72% with persuasion techniques
  • Authority, commitment, scarcity most effective
  • Validates parahuman model of LLM behavior
Raw lines 167 to 178
179## Quick Reference
181When designing a skill, ask:
1831. **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?)

Quick Reference

When designing a skill, ask:

  1. What type is it? (Discipline vs. guidance vs. reference)
  2. What behavior am I trying to change?
  3. Which principle(s) apply? (Usually authority + commitment for discipline)
  4. Am I combining too many? (Don't use all seven)
  5. Is this ethical? (Serves user's genuine interests?)
Raw lines 179 to 187