Systems Lab

Agent skill

list-is-the-message

Build segments where the "why" is so clear that messaging writes itself (Jordan Crawford)

activeReaches the webInstructions only715 words

Filed under Positioning and messaging.

From jurjen-gtm-engineer/gtmskills · 55 skill entries · 0 · pushed 2026-10-04

What it does when it runs

Build segments where the "why" is so clear that messaging writes itself (Jordan Crawford)

Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
  • blueprintgtm.com
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about list-is-the-message

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
git clone --depth 1 --filter=blob:none --sparse https://github.com/jurjen-gtm-engineer/gtmskills.git /tmp/gtmskills
git -C /tmp/gtmskills sparse-checkout set "skills/list-is-the-message"
mkdir -p ~/.claude/skills/list-is-the-message
cp -R "/tmp/gtmskills/skills/list-is-the-message/." ~/.claude/skills/list-is-the-message/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Reproduced in full from jurjen-gtm-engineer/gtmskills/blob/77dc0b3112dbf6cf906dfc3d526b6f7031bf964c/skills/list-is-the-message/SKILL.md, which is licensed MIT (repository). 715 words, 14 headings.

List Is the Message

You are applying Jordan Crawford's "List Is the Message" methodology, building segments where knowing WHY someone is on the list makes the messaging self-evident.

Core Philosophy

By understanding 'why' a lead is on the list, messaging becomes self-evident and deeply personalized.

Traditional approach: Build list → Write generic messaging → Try to personalize List Is the Message: Define tension → Build list around it → Messaging is obvious

Input

User provides:

  • Target segment or ICP
  • Pain point or opportunity to address
  • Available data sources

Process

  1. Define the Tension

    Prompt Pattern:

    For this segment: [DESCRIPTION]
    And this pain point: [PAIN]
    
    What specific, detectable event or situation would indicate this pain is ACTIVE right now?
    
    The tension must be:
    - Specific enough that we know exactly why they qualify
    - Detectable through data/research
    - Directly tied to the problem we solve
    
  2. Build the List Criteria

    Now define the list:
    
    WHO: [Base firmographic criteria]
    PLUS: [Tension signal 1]
    PLUS: [Tension signal 2]
    
    This combination means everyone on the list is experiencing [specific pain] because [specific reason].
    
  3. Extract the Self-Evident Message

    For someone on this list, complete this sentence:
    
    "We're reaching out because we noticed [tension signal], which usually means [pain they're experiencing]. [Value prop]..."
    
    The message should feel like it writes itself because the "why" is so clear.
    
  4. Output Format

    ## List Is the Message: [Segment Name]
    
    ### The Tension
    
    [Specific event/situation being targeted]
    
    ### List Criteria
    
    **Base:** [Firmographics]
    **Tension Signals:**
    - [Signal 1] - indicates [pain]
    - [Signal 2] - indicates [pain]
    
    ### The Self-Evident Message
    
    Because we know WHY they're on this list, the opening writes itself:
    
    "[Opening that directly addresses the tension]"
    
    ### Why This Works
    
    - Personalization is substantive, not cosmetic
    - The "why you, why now" is obvious
    - No AI invention needed, just adaptation
    
    ### Channel Adaptations
    
    **Email:** [Version]
    **LinkedIn:** [Version]
    **Cold call opener:** [Version]
    

Example

Input: "We sell compliance automation. Target is SaaS companies that just got enterprise customers and now face SOC 2 requirements."

Output:

## List Is the Message: First Enterprise Customer

### The Tension

SaaS companies that recently closed their first enterprise deal and are now facing compliance requirements they've never dealt with before.

### List Criteria

**Base:** SaaS company, 50-500 employees, B2B
**Tension Signals:**
- Added enterprise logo to website in last 90 days
- Posted SOC 2 or compliance-related job opening
- No CISO or security leader on LinkedIn

### The Self-Evident Message

Because we know WHY they're on this list, the opening writes itself:

"Congrats on landing [Enterprise Customer], I'm guessing the security questionnaire was a wake-up call. Most teams at your stage scramble to get SOC 2 ready while trying not to slow down product..."

### Why This Works

- We know the EXACT trigger (enterprise customer)
- We know the EXACT pain (compliance requirements)
- We know the EXACT timing (it's happening now)

### Channel Adaptations

**Email:** "Congrats on landing [Customer], I'm guessing their security questionnaire was a wake-up call..."

**LinkedIn:** "Saw you just added [Customer] to your customer page. Big milestone! Curious how you're handling the compliance requirements that usually come with enterprise deals..."

**Cold call:** "Hi [Name], I noticed [Company] just landed [Customer], congrats. Quick question: are you handling the SOC 2 requirements in-house or looking for help?"

Key Principles

  1. The Why Must Be Specific: "Growing companies" is not a tension. "Just raised Series B and has 15 open engineering roles" is.

  2. Messaging Is Adaptation, Not Invention: AI's role is to reformat the message for channels, not create the core insight.

  3. Every List Member Gets the Same Core Message: Because they share the same tension, the core message applies to all, only details change.

Related Skills

  • /pain-qualified-segment - Define the tension heuristics
  • /data-point-research - Find detectable signals
  • /permissionless-value-proposition - Lead with value
  • /email-opening-line - Channel adaptation

Credits

"The list is the message" is Jordan Crawford (Blueprint GTM)'s idea. The prompts and wording here are ours.


Examples are illustrative. Company names, prices and numbers in them are placeholders or may be out of date, so check the live source before you rely on any detail.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what list-is-the-message does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.