MCP HubMCP Hub
SKILL·A3384F

influence-psychology

wondelai
Mis à jour 20 days ago
7 vues
2,065
213
2,065
Voir sur GitHub
Testswordtestingdesign

À propos

Cette compétence offre un cadre pour appliquer les sept principes de persuasion éthique de Cialdini à la conception de produits et aux textes marketing. Elle s'active lorsque les utilisateurs ont besoin d'améliorer les conversions, les signaux de confiance ou les messages persuasifs, comme lors de la rédaction de témoignages ou de l'élaboration de tactiques d'urgence. Les conseils couvrent quand utiliser chaque principe et ses limites éthiques.

Installation rapide

Claude Code

Recommandé
Principal
npx skills add wondelai/skills -a claude-code
Commande PluginAlternatif
/plugin add https://github.com/wondelai/skills
Git CloneAlternatif
git clone https://github.com/wondelai/skills.git ~/.claude/skills/influence-psychology

Copiez et collez cette commande dans Claude Code pour installer cette compétence

Documentation

Influence Psychology Framework

Apply six decades of persuasion science — Cialdini's research into why people say "yes" — to product, copy, and sales, ethically.

Core Principle

People don't make decisions rationally — they use mental shortcuts (heuristics) that can be triggered to influence behavior. These shortcuts evolved because they're usually reliable, but they can also be exploited. Understanding them lets you design products, messaging, and experiences that align with how people actually decide.

Scoring

Goal: 10/10. When reviewing or creating persuasive elements (features, copy, flows, campaigns), run the Quick Diagnostic, then score against the bands below and apply the ethics gate. Always report the current score and the specific change needed to reach 10/10.

  • 9-10 — Multiple principles deliberately layered; every claim truthful; users can reverse the decision; passes the transparency test (still works if the user knows the strategy); safe for vulnerable users.
  • 7-8 — Principles deliberately layered and honest, but one gap (e.g. weak reversibility, or a single principle where layering was possible).
  • 5-6 — One principle present but generic, or leverage left on the table.
  • <=3 — No principle deliberately designed (relying on luck), OR any tactic is deceptive/coercive. Any fabricated proof, fake scarcity, or hidden-cost dark pattern caps the score at 3 regardless of other strengths.

The Seven Principles of Influence

1. Reciprocity

Core concept: People feel obligated to give back to those who have given to them first.

Why it works: Humans are wired to avoid being indebted — the obligation to repay can overpower personal preference, and the return favor often exceeds the original gift.

Key insights:

  • The gift must come first (before the request)
  • Unexpected, personalized gifts beat expected, generic ones
  • Even small gifts create obligation

Product applications:

ContextReciprocity TriggerExample
Free trialsFull access first, then ask to paySpotify Premium trial → subscription
Content marketingValue upfront (guides, tools)HubSpot free CRM → paid tools
Referral programsReward both referrer and refereeDropbox: both get extra storage

Copy patterns:

  • "Here's a gift for you..." (before asking)
  • "As a thank you for signing up..."
  • "We noticed you needed help with X, so we..."

See references/reciprocity.md when building free trials, lead magnets, or referral rewards — gift tiers, email templates, day-by-day reciprocity-stacking, and A/B variables.

2. Commitment & Consistency

Core concept: People want to be consistent with their past statements, beliefs, and actions.

Why it works: Inconsistency is psychologically uncomfortable; once we take a stand, personal and interpersonal pressure pushes us to behave consistently with it.

Key insights:

  • Small initial commitments lead to larger ones (foot-in-the-door)
  • Public > private; written > verbal; active (user-generated) > passive
  • Self-perception: we infer our attitudes from our behavior

Product applications:

ContextCommitment TriggerExample
OnboardingEasy yes, then larger asksDuolingo: "Can you commit to 5 min/day?"
Goal settingUser publicly states a goalStrava: "I want to run 50km this month"
Habit formationTrack streaks publiclySnapchat streaks, GitHub contributions

Copy patterns:

  • "What's your biggest challenge with X?" (commitment to a problem)
  • "How much would you like to save per month?" (numerical commitment)
  • "You said you wanted to achieve X. Let's start with..."

Onboarding sequence: micro-commitment ("What brings you here?") → small action (click, choice) → public/written commitment (goal) → reinforce ("Based on what you told us...").

Ethical boundary: Make every commitment freely chosen and easily reversible — no trick opt-ins or locked-in defaults the user can't undo.

See references/commitment-consistency.md when designing onboarding or goal-setting flows — foot-in-the-door sequences and public-commitment tactics.

3. Social Proof

Core concept: People determine what's correct by finding out what others think is correct.

Why it works: When uncertain, we use others' behavior as a guide — "if everyone's doing it, it must be right."

Key insights:

  • Most powerful when observers are uncertain; similar others = stronger proof
  • Negative social proof backfires ("9 out of 10 don't...")
  • Specific numbers beat vague claims ("2,347 users" > "thousands")

Types of social proof:

TypeDefinitionExample
Wisdom of crowdsMany people use/buy"Join 50,000+ marketers"
Wisdom of friendsPeople you know use it"3 of your friends use Notion"
ExpertAuthorities endorse"Recommended by Y Combinator"
CelebrityFamous people use it"Used by Elon Musk"
CertificationThird-party validation"SOC 2 compliant", "App of the Year"
UserSimilar people succeeded"Startups like yours grew 10x"

Product applications:

ContextSocial Proof ImplementationExample
Landing pagesUser count, reviews, logos"Trusted by 10,000+ companies"
Signup flowLive signups, popular plans"23 people signed up in the last hour"
Feature adoptionShow usage by others"85% of teams use this feature"

Copy patterns:

  • "[X number] of [similar people] are already..."
  • "[Name/Company] increased [metric] by [%]"
  • "Don't take our word for it. Here's what [users] say..."

Ethical boundary: Disclose when proof is curated or cherry-picked (e.g. "selected reviews") rather than presenting it as representative.

See references/social-proof.md when building testimonial sections or trust bars — proof types and implementation patterns.

4. Authority

Core concept: People follow the lead of credible, knowledgeable experts.

Why it works: Obedience to authority is deeply ingrained — following experts is an efficient shortcut when we lack expertise ourselves.

Key insights:

  • Titles, credentials, even symbols (lab coats, official-looking design) trigger automatic compliance
  • Admitting a weakness paradoxically increases authority (trustworthiness) — lead with it before strengths
  • Expertise doesn't transfer across domains, but people assume it does

Sources of authority:

TypeSignalExample
CredentialsDegrees, certifications"Built by Stanford PhDs"
ExperienceYears in field, track record"20 years in cybersecurity"
AssociationTrusted partners, investors"Backed by Y Combinator"
ContentThought leadership, research"Based on research with 10,000 users"
TransparencyHonest about limitations"Works best for teams of 10-50"

Product applications:

ContextAuthority TriggerExample
About pageFounder and team expertise"Built by ex-Google engineers"
ContentOriginal research, citations"State of [Industry] 2026 Report"
PartnershipsSecurity certs, integration badges"SOC 2 Type II", "GDPR compliant"

Copy patterns:

  • "Trusted by [authority figure/company]"
  • "Research shows that [cite source]..."
  • "Our team includes [credentials]"

See references/authority.md when writing About pages, bylines, or trust badges — credential framing and thought-leadership strategies.

5. Liking

Core concept: People prefer to say yes to those they like.

Why it works: Each liking factor (similarity, compliments, cooperation) is a separate lever that independently lowers a person's resistance to a request — they stack.

Factors that increase liking:

FactorMechanismExample
AttractivenessHalo effect: attractive = goodProfessional headshots, polished design
SimilarityWe like people like us"I'm a founder just like you"
ComplimentsFlattery works (even when obvious)"You have great taste in tools"
CooperationWorking toward shared goals"Let's build this together"
FamiliarityRepeated exposure increases likingConsistent brand, retargeting
AssociationLinked to positive thingsPlacement with aspirational lifestyles

Product applications:

ContextLiking TriggerExample
Brand voiceFriendly, conversational, humanMailchimp's playful copy
Team pagesReal people, personalityPersonal bios, hobbies, photos
SupportWarm, empathetic responses"I totally understand that frustration..."

Copy patterns:

  • "We're [similar trait] just like you"
  • "We built this because we were frustrated with..."
  • Casual, warm language ("Hey", "Awesome!", "We got you")

See references/liking.md when setting brand voice or writing support replies — liking factors and tone guidelines. For ready-to-adapt persuasive copy across all seven principles, see references/copywriting.md.

6. Scarcity

Core concept: People want more of what they can't have or what's running out.

Why it works: Loss aversion is stronger than gain seeking — FOMO triggers urgency, and psychological reactance makes us want what threatens to become unavailable.

Key insights:

  • Scarcity of time > scarcity of quantity; newly scarce > always scarce (loss framing)
  • Competition increases value — if others want it, I want it
  • Exclusive access is more valuable than open access

Types of scarcity:

TypeMechanismExample
Limited quantityFinite supply"Only 5 seats left"
Limited timeDeadline pressure"Offer ends Friday"
Exclusive accessNot everyone can have it"Invite-only beta"
CompetitionOthers competing for it"12 people viewing this"

Product applications:

ContextScarcity TriggerExample
PricingLimited-time discount"Early bird pricing ends in 3 days"
FeaturesBeta access, waitlist"Join 5,000 on the waitlist"
InventoryStock levels"2 left in stock"

Copy patterns:

  • "Limited to the first [X] customers"
  • "Offer expires [specific date]"
  • "[X] people are viewing this right now"

Ethical boundary: Ethical scarcity reflects real constraints (true inventory counts, genuine deadlines, legitimate capacity limits). Unethical: invented limits, countdown timers that reset, "Only 2 left!" shown daily, pressuring vulnerable users.

See references/scarcity.md when adding urgency or waitlists — five scarcity types, each with an "ethical when" line and the dark patterns to avoid.

7. Unity

Core concept: People say yes to those they consider part of "us" (shared identity).

Why it works: Tribal identity is fundamental — we make sacrifices for in-group members we wouldn't make for strangers.

Unity vs. Liking: Liking = "this person is like me" (similarity); Unity = "this person is me" (shared identity).

Sources of unity:

TypeMechanismExample
PlaceHometown, region, nationality"Built in San Francisco, for founders"
ExperienceShared hardship or triumph"We've all struggled with bad CRMs"
ValuesDeep beliefs, mission alignment"For people who value privacy"
TribeCo-creation, movement"Join the indie maker community"

Product applications:

ContextUnity TriggerExample
Brand positioningDefine the tribe"For remote-first teams"
Messaging"We" language, shared struggle"We believe work should be flexible"
CommunityFacilitate co-creationUser-generated content, forums

Copy patterns:

  • "For [identity group]" ("For designers", "For bootstrappers")
  • "Join [X] others who believe..."
  • "We're building this together"

Ethical boundary: Build the in-group by what it stands for, not by vilifying an out-group — define "us" without manufacturing a "them" to resent.

See references/unity.md when defining a brand tribe or community — identity-marketing and co-creation strategies.

Combining Principles

The most powerful persuasion layers multiple principles:

SaaS landing page: authority ("Built by ex-Stripe engineers") + social proof ("Trusted by 5,000+ companies") + liking (warm copy) + scarcity ("Join the beta—limited spots") + reciprocity ("Start free, no credit card") + unity ("For founders who move fast").

Referral program: reciprocity (reward both parties) + social proof ("X friends already joined") + unity ("Invite your team") + commitment (ask after a good experience).

See references/case-studies.md for full worked teardowns of multi-principle stacks across industries.

The Ethical Line

Persuasion helps people see value they'd appreciate anyway; manipulation tricks people into choices against their interests. The deciding tests are in the Quick Diagnostic below — run every persuasive element through them before shipping.

See references/ethics.md when a tactic feels borderline or you ship to vulnerable users — the persuasion-vs-manipulation decision tree, the regulatory landscape (FTC, GDPR, DSA, dark-patterns law), vulnerable-population safeguards, and audit templates.

Common Mistakes

MistakeWhy It FailsFix
Fake social proofDestroys trust when discoveredUse real data or don't use it
Overuse of scarcityBecomes noise, loses powerReserve for genuine urgency
Inconsistent authorityUndermines credibilityDon't claim expertise you lack
Forced reciprocityFeels transactional, not genuineGive without immediate ask
Generic unity"Everyone" is not a tribeDefine specific shared identity

Quick Diagnostic

Audit any persuasive element:

QuestionIf NoAction
Which principle(s) am I using?You're relying on luckExplicitly design for influence
Am I combining principles?Missing leverageLayer multiple principles
Is this claim/tactic truthful?You're manipulatingRemove or replace with truth
Does it help the user (not just convert)?You're exploiting, not persuadingRealign the tactic with the user's goal
Would it still work if the user knew the strategy?The tactic relies on deceptionReplace with a transparent version
Can users easily reverse the decision?Ethical concernAdd clear opt-outs
Safe for vulnerable users (children, elderly, distressed)?Heightened-harm riskApply ethics.md safeguards or exclude them

Further Reading

Based on Robert Cialdini's research and books:

About the Author

Robert B. Cialdini, PhD is Regents' Professor Emeritus of Psychology and Marketing at Arizona State University. Influence, the foundational text on persuasion science, has sold over 5 million copies worldwide, and he has consulted for Fortune 500 companies, government agencies, and nonprofits on ethical influence.

Dépôt GitHub

wondelai/skills
Chemin: plugins/sales-influence/skills/influence-psychology
0
agent-skillsai-skillsbusinessclaude-codeclaude-code-marketplaceclaude-code-plugin
FAQ

Questions fréquentes

Qu’est-ce que le Skill influence-psychology ?

influence-psychology est un Skill Claude créé par wondelai. Un Skill regroupe des instructions et des ressources que Claude charge à la demande pour effectuer des tâches liées à influence-psychology sans consigne supplémentaire.

Comment installer influence-psychology ?

Utilisez les commandes d’installation de cette page : ajoutez influence-psychology à Claude Code comme plugin ou clonez son dépôt dans votre dossier skills, puis redémarrez Claude pour charger le Skill.

À quelle catégorie appartient influence-psychology ?

influence-psychology appartient à la catégorie Tests.

influence-psychology est-il gratuit ?

Oui. influence-psychology est référencé sur AIMCP et son installation est gratuite.

Compétences associées

evaluating-llms-harness
Tests

Cette compétence Claude exécute le lm-evaluation-harness pour évaluer les modèles de langage sur plus de 60 tâches académiques standardisées telles que MMLU et GSM8K. Elle est conçue pour permettre aux développeurs de comparer la qualité des modèles, de suivre les progrès de l'entraînement ou de rapporter des résultats académiques. L'outil prend en charge différents backends, incluant les modèles HuggingFace et vLLM.

Voir la compétence
cloudflare-cron-triggers
Tests

Cette compétence fournit une connaissance complète pour la mise en œuvre de Déclencheurs Cron Cloudflare afin de planifier des Workers à l'aide d'expressions cron. Elle couvre la configuration de tâches périodiques, de travaux de maintenance et de flux de travail automatisés, tout en traitant des problèmes courants tels que les expressions cron non valides et les problèmes de fuseau horaire. Les développeurs peuvent l'utiliser pour configurer des gestionnaires planifiés, tester des déclencheurs cron et intégrer avec Workflows et Green Compute.

Voir la compétence
webapp-testing
Tests

Cette Compétence Claude fournit une boîte à outils basée sur Playwright pour tester des applications web locales via des scripts Python. Elle permet la vérification frontend, le débogage d'interface utilisateur, la capture d'écrans et la consultation des journaux, tout en gérant les cycles de vie du serveur. Utilisez-la pour les tâches d'automatisation de navigateur, mais exécutez les scripts directement plutôt que de lire leur code source pour éviter la pollution du contexte.

Voir la compétence
finishing-a-development-branch
Tests

Cette compétence aide les développeurs à finaliser leur travail en vérifiant que les tests passent, puis en présentant des options d'intégration structurées. Elle guide le processus de fusion, de création de PRs ou de nettoyage des branches une fois l'implémentation terminée. Utilisez-la lorsque votre code est prêt et testé pour finaliser systématiquement le cycle de développement.

Voir la compétence