---
name: understand-customers
description: Builds a buyer-psychology research brief covering customer pains, switching triggers, objections, inner monologue, and verbatim phrasing before writing a word of copy. Use when researching an ICP before landing page or ad copy, or when the user mentions "understand customers", "empathy engine", or "customer pain points".
metadata:
  version: 1.0.0
  author: illyism
  source: https://il.ly/skills/understand-customers
title: understand-customers
canonical_url: https://skilld.dev/gh/illyism/seo-skills/understand-customers
last_updated: 2026-11-12T14:05:13.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install illyism/seo-skills/understand-customers`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/understand-customers`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/illyism/seo-skills/understand-customers) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/understand-customers`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/understand-customers --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/understand-customers --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

For my product/service, [Briefly describe your product/service, e.g., "an AI-powered link building tool"], help me create Blitz Copy by first deeply understanding my ideal user. Answer these questions:

1.  **Core Identity & Role:**
    *   Who are they *really* (e.g., "ambitious SaaS founder," "overwhelmed marketing manager," "freelancer struggling to scale")?
    *   What's their primary goal related to the problem my product solves?

2.  **Deepest Pains & Frustrations (The "Nightmare Scenario"):**
    *   What is their current biggest, most visceral nightmare related to [the problem your product solves, e.g., "link building," "content creation," "sales outreach"]?
    *   What specific words or phrases do *they* use to describe this pain?
    *   What deep inner thoughts or inner monologue is driving them?
    *   What have they tried before that failed or disappointed them? Why?
    *   What are the emotional consequences of this pain (e.g., "feeling stuck," "wasting money," "falling behind competitors," "imposter syndrome")?

3.  **Unspoken Desires & Aspirations (The "Magic Wand" Outcome):**
    *   If they could wave a magic wand, what's the ultimate, almost "too good to be true" outcome they dream of regarding [the problem area]?
    *   Beyond the functional benefit (e.g., "more backlinks"), what does this outcome *mean* for them emotionally or in terms of status (e.g., "market leader," "peace of mind," "industry recognition," "freedom")?
    *   What would make them feel like they've found a "cheat code" or an "unfair advantage"?

4.  **Language & Worldview:**
    *   What specific jargon, tools, or influencers are part of their world?
    *   What's a core belief they hold about [the problem area] that my product can affirm or satisfyingly challenge?

Based on these insights, let's brainstorm initial Blitz Copy angles (Identity Triggers, Emotional Hooks, Pattern Interrupts, Dopamine-Driven Payoffs).
