AGENT SKILL

customer-conversation-access

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.

License 许可
MIT
最近更新
2026-06-26
Stars
★ 0
Forks
0

01 前言 Front Matter

name
customer-conversation-access
license
MIT
metadata
{ "tags": "customer-discovery,outreach,startups,interviews,research", "version": "0.1.3", "category": "Marketing", "displayName": "Customer Conversation Access" }
description
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.
compatibility
Codex, Claude Code, and other Agent Skills-compatible clients.

02 资源文件 2

03 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 7. 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.

04 同仓库更多 Skills

ConcertoNotes
ConcertoNotes/codex-plugins

android-emulator-qa

Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.

★ 0
ConcertoNotes
ConcertoNotes/codex-plugins

supabase-postgres-best-practices

Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.

★ 0
ConcertoNotes
ConcertoNotes/codex-plugins

sentry

Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.

★ 0
ConcertoNotes
ConcertoNotes/codex-plugins

render-workflows

Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.

★ 0
ConcertoNotes
ConcertoNotes/codex-plugins

render-web-services

Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.

★ 0
ConcertoNotes
ConcertoNotes/codex-plugins

render-static-sites

Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React/Vue/Hugo/Gatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.

★ 0