[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MBZ1MDZ569RZ5M88CS6EVA":3,"skill-same:01M6MBZ1MDZ569RZ5M88CS6EVA":91},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":62,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M6MBZ1MDZ569RZ5M88CS6EVA","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.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1559,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fcustomer-conversation-access\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"access","customer conversation access","conversation","customer","communities","failing","when","conversations","interviews","customer-discovery","cold","people","events","customer discovery","startups","customer conversations","interview","ask","page","marketing","team","code","2026-11-10 10:12:30",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":15,"metadata":51,"description":7,"compatibility":56},{"tags":52,"version":53,"category":54,"displayName":55},"customer-discovery,outreach,startups,interviews,research","0.1.3","Marketing","Customer Conversation Access","Codex, Claude Code, and other Agent Skills-compatible clients.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fcustomer-conversation-access",474,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-11 14:40:14",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill customer-conversation-access",{"tool":73,"command":74},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill customer-conversation-access",{"tool":76,"command":77},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill customer-conversation-access","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fcustomer-conversation-access\u002FSKILL.md",true,[81,87],{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"agents\u002Fopenai.yaml","REFERENCE","参考文档",223,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fcustomer-conversation-access\u002Fagents\u002Fopenai.yaml",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"workflows\u002Fframe-warm-intro.md",1118,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fcustomer-conversation-access\u002Fworkflows\u002Fframe-warm-intro.md",[92,101,108,115,141,166],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":100},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":100},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":100},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":46},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[122,123,124,125,126,127,128,129,130,131,132,30,133,134,135,136,137,138,139,140],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":46},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[148,149,150,136,151,152,153,154,155,156,157,158,159,160,127,161,162,163,164,165],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":179,"publishedAt":46},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[172,175,176],{"categoryNo":173,"categoryName":174,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":177,"categoryName":178,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[168,180,181,182,183,184,185,162,186,128,187,188,189,190,30,191,192,193,194,195],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]