[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77SKW91HHV3FS42G13CSNPF":3,"skill-same:01M77SKW91HHV3FS42G13CSNPF":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":13,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M77SKW91HHV3FS42G13CSNPF","customer-conversation-access",null,"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.","ConcertoNotes\u002Fcodex-plugins","ConcertoNotes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F249301288?v=4","01M77NJ0BK2KN5YW0D8RHD99TB","01M77NJ0CCEDPATAY3JTXEWNK5",0,"MIT","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fcustomer-conversation-access\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: customer-conversation-access\ndescription: 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.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.3\"\n  displayName: Customer Conversation Access\n  category: Marketing\n  tags: customer-discovery,outreach,startups,interviews,research\n---\n\n# Customer Conversation Access\n\nUse this skill to help teams get into useful customer conversations without\nturning every interaction into a formal interview or sales pitch. The best\naccess path depends on where the target segment already spends time and who can\ncredibly introduce the team.\n\n## Source Traceability\n\nPrimary source: The Mom Test by Rob Fitzpatrick, especially chapters 4, 6, and\n7. Guidance is paraphrased for this MIT repo; authoring notes used converted\nEPUB lines 2176-2362 and 2791-3610.\n\n## Access Paths\n\n| Path | Use When | Watch For |\n|------|----------|-----------|\n| Warm intros | Someone credible can introduce the team | Make the ask easy and specific |\n| Existing communities | Customers gather in events, forums, meetups, Slack, Discord, or associations | Participate before extracting value |\n| Casual chats | The context naturally touches the problem | Keep the idea out until needed |\n| Teaching or office hours | The team has a useful point of view | Do not disguise a sales pitch as education |\n| Landing-page replies | People opted into the topic | Follow up personally, not only with metrics |\n| Advisors | Industry structure is unclear | Advisors should create learning, not just status |\n\n## Meeting Framing\n\nWhen a formal ask is required, include:\n\n1. Vision: the broad problem or better world.\n2. Stage: where the team is now.\n3. Weakness: what the team does not understand yet.\n4. Pedestal: why this person can help.\n5. Ask: the specific, easy-to-forward conversation request.\n\nKeep the framing short. Do not ask for opinions on the idea. Ask for help\nunderstanding a domain, problem, workflow, or decision process. Prefer a short,\nspecific conversation over a broad \"pick your brain\" request.\n\n## Output Format\n\n```markdown\n# Customer Conversation Access Plan\n\n## Segment\n[Who we need to talk to.]\n\n## Best Access Paths\n| Path | Why It Fits | First Action | Risk |\n|------|-------------|--------------|------|\n\n## Warm Intro Or Meeting Ask\n- Vision:\n- Stage:\n- Weakness:\n- Why them:\n- Ask:\n\n## Follow-Up\n- Target number of conversations:\n- Next source if this fails:\n- What to track:\n```\n\n## Workflow\n\nUse `workflows\u002Fframe-warm-intro.md` when drafting an intro request, meeting\nrequest, or conversation opener.\n\n## Quality Bar\n\n- Do not default to cold outreach if a warmer path is plausible.\n- Do not hide a sales pitch inside a request for advice.\n- Do not ask for a formal meeting when a casual conversation would learn enough.\n- Do not measure access only by response rate. The goal is useful\n  conversations with the right people.\n","# Customer Conversation Access\n\nUse this skill to help teams get into useful customer conversations without\nturning every interaction into a formal interview or sales pitch. The best\naccess path depends on where the target segment already spends time and who can\ncredibly introduce the team.\n\n## Source Traceability\n\nPrimary source: The Mom Test by Rob Fitzpatrick, especially chapters 4, 6, and\n7. Guidance is paraphrased for this MIT repo; authoring notes used converted\nEPUB lines 2176-2362 and 2791-3610.\n\n## Access Paths\n\n| Path | Use When | Watch For |\n|------|----------|-----------|\n| Warm intros | Someone credible can introduce the team | Make the ask easy and specific |\n| Existing communities | Customers gather in events, forums, meetups, Slack, Discord, or associations | Participate before extracting value |\n| Casual chats | The context naturally touches the problem | Keep the idea out until needed |\n| Teaching or office hours | The team has a useful point of view | Do not disguise a sales pitch as education |\n| Landing-page replies | People opted into the topic | Follow up personally, not only with metrics |\n| Advisors | Industry structure is unclear | Advisors should create learning, not just status |\n\n## Meeting Framing\n\nWhen a formal ask is required, include:\n\n1. Vision: the broad problem or better world.\n2. Stage: where the team is now.\n3. Weakness: what the team does not understand yet.\n4. Pedestal: why this person can help.\n5. Ask: the specific, easy-to-forward conversation request.\n\nKeep the framing short. Do not ask for opinions on the idea. Ask for help\nunderstanding a domain, problem, workflow, or decision process. Prefer a short,\nspecific conversation over a broad \"pick your brain\" request.\n\n## Output Format\n\n```markdown\n# Customer Conversation Access Plan\n\n## Segment\n[Who we need to talk to.]\n\n## Best Access Paths\n| Path | Why It Fits | First Action | Risk |\n|------|-------------|--------------|------|\n\n## Warm Intro Or Meeting Ask\n- Vision:\n- Stage:\n- Weakness:\n- Why them:\n- Ask:\n\n## Follow-Up\n- Target number of conversations:\n- Next source if this fails:\n- What to track:\n```\n\n## Workflow\n\nUse `workflows\u002Fframe-warm-intro.md` when drafting an intro request, meeting\nrequest, or conversation opener.\n\n## Quality Bar\n\n- Do not default to cold outreach if a warmer path is plausible.\n- Do not hide a sales pitch inside a request for advice.\n- Do not ask for a formal meeting when a casual conversation would learn enough.\n- Do not measure access only by response rate. The goal is useful\n  conversations with the right people.\n",{"name":5,"license":14,"metadata":23,"description":7,"compatibility":28},{"tags":24,"version":25,"category":26,"displayName":27},"customer-discovery,outreach,startups,interviews,research","0.1.3","Marketing","Customer Conversation Access","Codex, Claude Code, and other Agent Skills-compatible clients.","main","9ba3c9fadff1092395837bf1502e1b8a7f98b1e1","plugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fcustomer-conversation-access","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins","https:\u002F\u002Fgithub.com\u002FConcertoNotes","2026-06-26 10:13:54",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add ConcertoNotes\u002Fcodex-plugins --skill customer-conversation-access",{"tool":41,"command":42},"bunx","bunx skills add ConcertoNotes\u002Fcodex-plugins --skill customer-conversation-access",{"tool":44,"command":45},"pnpm","pnpm dlx skills add ConcertoNotes\u002Fcodex-plugins --skill customer-conversation-access","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fcustomer-conversation-access\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"agents\u002Fopenai.yaml","REFERENCE","参考文档",223,"https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fcustomer-conversation-access\u002Fagents\u002Fopenai.yaml",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"workflows\u002Fframe-warm-intro.md",1118,"https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fcustomer-conversation-access\u002Fworkflows\u002Fframe-warm-intro.md",[60,69,76,84,91,98],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":64,"licenseFileUrl":65,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M77YB7WW36DS9AERTWP673E0","android-emulator-qa","Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M77Y7AA8N45G6NM0WJSS2W9C","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.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsupabase\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":64,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M77Y2W5H5YGSW7MYWEJ8HYXD","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`.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsentry\u002Fskills\u002Fsentry\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsentry\u002Fskills\u002Fsentry\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M77Y06GV1DAME7PN9KBFHWRX","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.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-workflows\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M77Y01A6RJA8VYT7CZ2TVETF","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.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-web-services\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":18},"01M77XZW1AZ6B6NZTWWFVY72T3","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\u002FVue\u002FHugo\u002FGatsby 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.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-static-sites\u002FSKILL.md",[],[]]