SkillsAdd

lvtd-llc/skills

customer-conversation-access

Find and frame customer conversations through warm intros, communities, casual chats, events, advisors, landing-page replies, and meeting requests.

First seen Jun 21, 2026

Installation

$ npx skills add lvtd-llc/skills --skill customer-conversation-access
View on skills.sh ↗ GitHub repository ↗

Summary

  • Find and frame customer conversations through warm intros, communities, casual chats, events, advisors, landing-page replies, and meeting requests.
  • Use when a team needs people to interview, cold outreach is failing, a meeting ask sounds needy or pitchy, or customer discovery needs a credible reason to talk.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

remembering-conversations Similar name
obra/episodic-memory

You MUST invoke this skill before saying "I don't know," guessing, or treating any topic as new…

9.2K installs
difficult-workplace-conversations Similar name
softaworks/agent-toolkit

Structured approach to workplace conflicts, performance discussions, and challenging feedback u…

3.9K installs
implementing-ui-bundle-agentforce-conversation-client Similar name
forcedotcom/sf-skills

Use this skill when the user asks to add, embed, integrate, configure, style, or remove an agen…

3.6K installs
having-difficult-conversations Similar name
refoundai/lenny-skills

Help users navigate tough feedback, performance conversations, and conflict. Use when someone n…

1.6K installs
conversation-memory Similar name
sickn33/agentic-awesome-skills

Persistent memory systems for LLM conversations including short-term, long-term, and entity-bas…

1.5K installs
conversation-memory Similar name
davila7/claude-code-templates

Persistent memory systems for LLM conversations including short-term, long-term, and entity-bas…

1.1K installs

Also in this package

Other skills from lvtd-llc/skills · top by installs.

npx skills add lvtd-llc/skills
game-balance-economy 119 django-htmx 78 game-mechanics-design 74 calibredb 71 alpinejs-django 68 game-playtest-planning 67 game-story-world-character 67 book-toc-lab 66 b2b-sales-constraint-diagnosis 63 make-product-viral 63

Browse all from lvtd-llc/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version0.1.3
LicenseMIT
CompatibilityCodex, Claude Code, and other Agent Skills-compatible clients.
Declared agents claude-code codex
More metadata
version
0.1.3
displayName
Customer Conversation Access
category
Marketing
tags
customer-discovery,outreach,startups,interviews,research

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,197 B
  • docs SUMMARY.md 345 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 57 installs

SKILL.md

Customer Conversation Access

Use this skill to help teams get into useful customer conversations without turning every interaction into a formal interview or sales pitch. The best access path depends on where the target segment already spends time and who can credibly introduce the team.

Source Traceability

Primary source: The Mom Test by Rob Fitzpatrick, especially chapters 4, 6, and

  1. Guidance is paraphrased for this MIT repo; authoring notes used converted

EPUB lines 2176-2362 and 2791-3610.

Access Paths

Path Use When Watch For
Warm intros Someone credible can introduce the team Make the ask easy and specific
Existing communities Customers gather in events, forums, meetups, Slack, Discord, or associations Participate before extracting value
Casual chats The context naturally touches the problem Keep the idea out until needed
Teaching or office hours The team has a useful point of view Do not disguise a sales pitch as education
Landing-page replies People opted into the topic Follow up personally, not only with metrics
Advisors Industry structure is unclear Advisors should create learning, not just status

Meeting Framing

When a formal ask is required, include:

  1. Vision: the broad problem or better world.
  2. Stage: where the team is now.
  3. Weakness: what the team does not understand yet.
  4. Pedestal: why this person can help.
  5. Ask: the specific, easy-to-forward conversation request.

Keep the framing short. Do not ask for opinions on the idea. Ask for help understanding a domain, problem, workflow, or decision process. Prefer a short, specific conversation over a broad "pick your brain" request.

Output Format

# Customer Conversation Access Plan

## Segment
[Who we need to talk to.]

## Best Access Paths
| Path | Why It Fits | First Action | Risk |
|------|-------------|--------------|------|

## Warm Intro Or Meeting Ask
- Vision:
- Stage:
- Weakness:
- Why them:
- Ask:

## Follow-Up
- Target number of conversations:
- Next source if this fails:
- What to track:

Workflow

Use workflows/frame-warm-intro.md when drafting an intro request, meeting request, or conversation opener.

Quality Bar

  • Do not default to cold outreach if a warmer path is plausible.
  • Do not hide a sales pitch inside a request for advice.
  • Do not ask for a formal meeting when a casual conversation would learn enough.
  • Do not measure access only by response rate. The goal is useful

conversations with the right people.