Skip to content
cccskills
FreePublished on GitHub

awareness-stage-mapper

Plan campaign messages around what customers already know about a problem, available solutions, and a product. Use audience research to assign an awareness stage, then choose suitable language, supporting evidence, and a sequence of messages.

OriginalShow the original description

Map audience awareness stages to messaging strategy when planning a campaign, offer, or persuasion sequence.

See how to install

Good for

  • Identify audience awareness before writing campaign copy
  • Adapt proposal language to customer knowledge
  • Plan a sequence from education to product comparison
  • Choose evidence that addresses purchase hesitation

Files included (1)

  • SKILL.md7.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Use a marketing planning and audience-research lens. Your task is to diagnose precisely where a customer sits on the awareness ladder and calibrate the psychological approach, language register, and persuasion strategy accordingly.

When to Use

  • Use when you need to identify how aware an audience already is before writing messaging or offers.
  • Use when a campaign needs stage-specific language, sequencing, or persuasion strategy.

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 by MMEHDI0606; immutable source snapshot. This identifies the contributed instructions, not scientific validation or a new upstream endorsement.

CONTEXT GATHERING

Before diagnosing awareness, establish:

  1. The Target Human - use the psychographic profile and JTBD map.
  2. The Objective - what action or belief change is needed.
  3. The Output - a stage diagnosis plus messaging strategy.
  4. Constraints - channel, length, trust level, and ethical limits.

If the audience, offer, or channel is unclear, ask before proceeding.

PSYCHOLOGICAL FRAMEWORK: ELM-STAGED BELIEF CHANGE

Mechanism

Awareness determines whether the audience can process central arguments or will rely on peripheral cues, heuristics, and familiarity. The wrong stage match creates resistance, confusion, or boredom. Use the awareness ladder to choose the route that best fits motivation, ability, and prior belief structure (ELM research; Quick et al., 2018; Zhang et al., 2024; Lavoie & Quick, 2013).

Execution Steps

Step 1 - Classify the awareness stage Label the audience as unaware, problem aware, solution aware, product aware, or most aware. Planning hypothesis (verify before presenting as research): message processing differs sharply by prior knowledge and perceived relevance (ELM; Zhang et al., 2024).

Step 2 - Assess motivation and ability Use observable evidence of interest and familiarity: questions prospects actually asked, concepts they can explain, and the time/format available. If that evidence is absent, record motivation and familiarity as unknown and propose a simple message test. Do not infer intelligence or mental capacity from demographic labels. Planning hypothesis (verify before presenting as research): the central route works when involvement and ability are high; otherwise peripheral cues dominate (Quick et al., 2018; SanJose-Cabezudo et al., 2009).

Step 3 - Select the persuasion route Choose educational framing for unaware/problem aware audiences and comparative proof for later-stage audiences. Planning hypothesis (verify before presenting as research): premature solution pitching can trigger reactance and weak processing (Lavoie & Quick, 2013; Grandpre et al., 2003).

Step 4 - Calibrate language register Match vocabulary depth, jargon, and specificity to the stage. Planning hypothesis (verify before presenting as research): familiarity and self-relevance shape attention and acceptance (Zhang et al., 2024; Moyer-Gusé et al., 2022).

Step 5 - Choose the entry point Recommend the best first touchpoint for downstream content: education, proof, demo, comparison, or direct offer. Planning hypothesis (verify before presenting as research): stage-appropriate sequencing improves narrative transportation and belief change (Green & Brock, 2000; Chen & Bell, 2022).

DECISION MATRIX

Variable: awareness stage

  • If unaware -> lead with the problem and its lived consequences.
  • If problem aware -> clarify the cost of staying stuck and define the problem precisely.
  • If solution aware -> compare approaches and explain why this solution fits.
  • If product aware -> remove hesitation with proof, differentiation, and specificity.
  • If most aware -> make the next step obvious and low friction.

Variable: audience motivation

  • If motivation is low -> use simple cues, concrete outcomes, and short pathways.
  • If motivation is moderate -> mix explanation with proof.
  • If motivation is high -> use detailed evidence and direct comparison.

Variable: resistance risk

  • If reactance risk is high -> avoid commanding language and overclaiming.
  • If reactance risk is moderate -> use choice-preserving language.
  • If reactance risk is low -> use more direct conversion language.

FAILURE MODES - DO NOT DO THESE

Failure Mode 1

  • Agents typically: pitch the solution to an audience that has not yet named the problem.
  • Why it fails psychologically: the message asks for action before the audience has mental permission.
  • Instead: start with the problem, not the product.

Failure Mode 2

  • Agents typically: use central arguments when the audience is not ready to process them.
  • Why it fails psychologically: low ability or motivation leads to shallow processing.
  • Instead: simplify, sequence, and reduce cognitive load.

Failure Mode 3

  • Agents typically: treat all audiences as equally skeptical.
  • Why it fails psychologically: stage and context determine how much proof is needed.
  • Instead: calibrate the amount and type of proof to the stage.

ETHICAL GUARDRAILS

This skill must:

  • Respect the audience's current knowledge.
  • Avoid pretending people are more aware than they are.
  • Preserve autonomy and informed choice.

The line between persuasion and manipulation is using stage-appropriate language versus hiding the real intent or pushing a premature commitment. Never cross it.

SKILL CHAINING

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

  • @customer-psychographic-profiler
  • @jobs-to-be-done-analyst

This skill's output feeds into:

  • @copywriting-psychologist
  • @headline-psychologist
  • @sequence-psychologist
  • @pitch-psychologist
  • @subject-line-psychologist

OUTPUT QUALITY CHECK

Before finalizing output, the agent asks:

  • Did I classify the audience at the right awareness stage?
  • Did I choose the correct persuasion route for that stage?
  • Did I calibrate language to the audience's knowledge?
  • Did I avoid premature solution pitching?
  • Does the strategy preserve autonomy and trust?

Example

User request:

Identify how aware an audience already is before writing messaging or offers.

Illustrative output: Given an interview where buyers name the problem but no solution, label problem-aware as a provisional inference; propose an explanatory message and list what evidence would change the classification.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Assess a new or existing AI project by examining its code, goals, and constraints. Recommend skills confirmed to exist in the available registry, then outline tasks and implementation phases with dependencies, completion criteria, and checks.

  • Planning the first steps of a new AI project
  • Assessing technical issues in an existing project
  • Selecting relevant skills from an available registry
sickn33/agentic-awesome-skills48.4KUpdated Oct 23, 2026

007

FreeSummary

Review code and infrastructure for security risks, map potential threats, and plan stronger defenses. The skill covers OWASP checks, attack and defense exercises, and incident response, with validation required for each environment.

  • Reviewing code and infrastructure security
  • Mapping threats with STRIDE or PASTA
  • Planning stronger security settings
sickn33/agentic-awesome-skills48.4KUpdated Oct 23, 2026

Turn a repeatable task into an Andru.ia skill with clear inputs, outputs, examples, and limits. Draft SKILL.md, check the folder structure and required validations, and prepare a pull request describing the changes for review.

  • Creating a skill for a repeatable task
  • Improving an existing skill’s examples and limits
  • Validating skill files and preparing a pull request
sickn33/agentic-awesome-skills48.4KUpdated Oct 23, 2026

Prepare an industry briefing once a project's sector is defined. It covers sector context, potentially applicable regulations, familiar interface patterns, technology choices, and risks, while separating verified evidence from hypotheses and questions requiring further review.

  • Researching industry requirements before product design
  • Checking regulations for a project's jurisdiction
  • Choosing interface patterns familiar to target users
sickn33/agentic-awesome-skills48.4KUpdated Oct 23, 2026

Create presentation drafts from text, outlines, or documents through the 2slides API. Match a reference image's style, choose themes, add AI voice narration, and export slide images or audio for review and use.

  • Create a presentation from text or an outline
  • Summarize a document into slides
  • Match slide styling to a reference image
sickn33/agentic-awesome-skills48.4KUpdated Oct 23, 2026

Plan a 360-degree or peer feedback process and create empty response templates from confirmed requirements. Produces consistent CSV, SQL, JSON Schema, or Notion property mappings while keeping visibility choices and scoring configuration separate.

  • Plan an anonymous peer feedback process
  • Create a CSV template for feedback responses
  • Align feedback fields across SQL and JSON Schema
sickn33/agentic-awesome-skills48.4KUpdated Oct 23, 2026

See all skills by sickn33

Report a problem with this skill