sequence-psychologist – skill Marketing & SEO cho agent AI

Use a marketing planning and audience-research lens. Your task is to design email nurture sequences and multi-touch communication flows using psychological principles of curiosity loops, reciprocity, commitment, and emotional pacing.

When to Use

• Use when an email, onboarding, or sales sequence needs a better step-by-step persuasion arc.
• Use when each touchpoint should prepare the next instead of repeating the same appeal.

Evidence and scope

Use observed audience research and verified product facts. Psychological interpretations and the author-year references below are inherited conceptual context, not validated evidence for this exact workflow or a guaranteed conversion effect. Before using a scientific claim externally, verify the actual publication, method and applicability; omit unsupported claims. This is marketing planning, not clinical diagnosis. Do not infer sensitive traits or exploit vulnerabilities.

Original contribution: [PR 451](https://github.com/sickn33/agentic-awesome-skills/pull/451) by MMEHDI0606; [immutable source snapshot](https://github.com/MMEHDI0606/antigravity-awesome-skills/blob/9c61357e3e6bb167946036f52ac1e28fc82e04d0/skills/sequence-psychologist/SKILL.md). This identifies the contributed instructions, not scientific validation or a new upstream endorsement.

CONTEXT GATHERING

Before designing a sequence, establish:

1. The Target Human - psychographic profile, awareness stage, and trust stage.

2. The Objective - the conversion or relationship milestone.

3. The Output - email sequence architecture or nurture flow.

4. Constraints - channel, cadence, and ethical limits.

If the sequence goal is unclear, ask before proceeding.

PSYCHOLOGICAL FRAMEWORK: COMMITMENT-PACING SEQUENCE

Mechanism

People move when messages create a manageable emotional arc: curiosity, recognition, trust, small commitments, then a larger ask. Email sequences work when they respect autonomy, use reciprocity carefully, and let the reader feel progressive momentum rather than pressure (Cialdini; Zeigarnik effect; mere exposure; Stawarz et al., 2015; Gillison et al., 2019; Sheeran et al., 2020).

Execution Steps

Step 1 - Define the emotional arc

Map each email to a single emotional objective.

*Planning hypothesis (verify before presenting as research): persuasive sequences work better when they pace emotion and cognition instead of repeating the same ask (Cialdini; narrative sequence research).*

Step 2 - Open the loop

Create a curiosity gap or unresolved question the next email will answer.

*Planning hypothesis (verify before presenting as research): open loops increase attention when the promised payoff is real (Zeigarnik effect; curiosity research).*

Step 3 - Give before asking

Use useful content, insight, or relief before the ask.

*Planning hypothesis (verify before presenting as research): reciprocity and liking increase receptivity when the audience has already received value (Cialdini).*

Step 4 - Escalate commitment gradually

Move from low-friction responses to higher-friction decisions.

*Planning hypothesis (verify before presenting as research): foot-in-the-door and consistency effects increase compliance when the steps are coherent (Cialdini; behavioral change research).*

Step 5 - End with a clean decision

Make the final email simple, concrete, and autonomy-preserving.

*Planning hypothesis (verify before presenting as research): choice clarity reduces avoidance and supports follow-through (Fogg; Lavoie & Quick, 2013).*

DECISION MATRIX

Variable: sequence length

• If short -> use a compact 3-5 email arc.
• If medium -> use education, proof, objection handling, then ask.
• If long -> use a staged relationship arc with repeated value delivery.

Variable: audience readiness

• If cold -> lead with relevance and low-pressure value.
• If warm -> blend proof with identity and urgency.
• If hot -> move quickly to the decision.

Variable: trust stage

• If low -> keep asks small and proof high.
• If moderate -> alternate value and ask.
• If high -> compress and simplify.

FAILURE MODES - DO NOT DO THESE

Failure Mode 1

• Agents typically: send sales-only emails.
• Why it fails psychologically: the sequence feels extractive.
• Instead: give value before asking.

Failure Mode 2

• Agents typically: make every email try to close.
• Why it fails psychologically: constant pressure produces fatigue.
• Instead: assign one emotional job per email.

Failure Mode 3

• Agents typically: let open loops drag on too long.
• Why it fails psychologically: curiosity turns into annoyance.
• Instead: resolve the loop on schedule.

ETHICAL GUARDRAILS

This skill must:

• Respect consent and unsubscribe norms.
• Avoid manipulative spam tactics.
• Preserve autonomy throughout the sequence.

The line between persuasion and manipulation is pacing a real relationship toward a real decision versus pressuring people through endless unresolved suspense and hidden agendas. Never cross it.

SKILL CHAINING

Optional context from related skills (equivalent supplied research is sufficient; do not create a prerequisite cycle):

• [ ] @customer-psychographic-profiler
• [ ] @awareness-stage-mapper
• [ ] @objection-preemptor

This skill's output feeds into:

• [ ] @subject-line-psychologist
• [ ] @copywriting-psychologist
• [ ] @pitch-psychologist

OUTPUT QUALITY CHECK

Before finalizing output, the agent asks:

• [ ] Did I assign one emotional job per email?
• [ ] Did I pace commitment gradually?
• [ ] Did I give value before asking?
• [ ] Did I resolve open loops on time?
• [ ] Does the sequence feel respectful and useful?

Example

User request:

> Rewrite this email sequence with a clearer step-by-step persuasion arc and credible transitions.

Illustrative output: Draft three opt-in messages: useful explanation, verified example and optional next step; record consent/stop conditions and do not send anything as part of planning.

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.