[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CEMSFSPSJS9Y7G4WZV8722":3,"skill-same:01M7CEMSFSPSJS9Y7G4WZV8722":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":5,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7CEMSFSPSJS9Y7G4WZV8722","bourgoin-why-we-buy",null,"Turn buyer stories into evidence-based messages, offers, and small growth tests using Katelyn Bourgoin's public buyer psychology method. Use for positioning, landing pages, ads, emails, and campaigns that need to resonate with real buyers.","getedgehq\u002Fskills","getedgehq","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F327350993?v=4","01M7CEH5YJQYF1PB3MDG9PA5HX","01M7CEH5ZAPY8TX4H3E04KM875",5,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fbourgoin-why-we-buy\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fbourgoin-why-we-buy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bourgoin-why-we-buy\ndescription: \"Turn buyer stories into evidence-based messages, offers, and small growth tests using Katelyn Bourgoin's public buyer psychology method. Use for positioning, landing pages, ads, emails, and campaigns that need to resonate with real buyers.\"\n---\n\n# Why We Buy: buyer stories to trigger tests\n\nBased on Katelyn Bourgoin's public method. Not affiliated with or endorsed by Katelyn Bourgoin.\n\n## When to use\n\nUse this skill to improve marketing by explaining why a buyer started looking, what progress they wanted, and what made a purchase believable. It produces a buyer-insight and trigger-test brief with usable copy and one recommended experiment. Suitable requests include positioning, offers, landing pages, ads, emails, and acquisition campaigns. Begin with behavior and context, then choose a psychological presentation that fits the evidence. [S1][S2]\n\nUse the full loop when interviews or buying stories are available. With reviews, support notes, or sales conversations alone, use a provisional version and identify the missing evidence. For a narrow copy revision, apply the relevant insight and messaging checks without expanding the assignment into a research program. These scope adaptations are package conventions, not additional claims about Bourgoin's framework.\n\nA finished brief must distinguish buyer evidence, interpretation, and a hypothesis awaiting testing. Do not manufacture buyer quotations, emotional motives, endorsements, urgency, or results to fill empty fields. The method generates useful possibilities from stories; it does not establish that a single story represents a whole market. See [references\u002Fmethod.md](references\u002Fmethod.md) for the evidence rules and exceptions.\n\n## Procedure\n\n1. **Define the decision.** Record the requested deliverable, one growth objective, the intended buyer, and available evidence. Establish the existing metric if known. Use the scope and objective rules in [references\u002Fmethod.md](references\u002Fmethod.md), then open [templates\u002Foutput-template.md](templates\u002Foutput-template.md) as the working brief.\n\n2. **Select a useful informant.** Prefer a recent, best-fit purchaser who obtained value. Before launch, use a recent competitor buyer or someone currently buying a solution. Demographic similarity is insufficient. Follow the recruitment and timing rules in [references\u002Fmethod.md](references\u002Fmethod.md). [S1][S2]\n\n3. **Recover the buying sequence.** Trace the purchase back to the first struggling moment, then reconstruct searches, conversations, alternatives, and decisions. Ask what happened rather than what someone might do. Use the interview prompts in [references\u002Fmethod.md](references\u002Fmethod.md). [S1][S2]\n\n4. **Build an evidence ledger.** Attach a source and timing to each observation. Mark interpretation, unknowns, and contradictions separately. Keep actual buyer wording apart from proposed copy. Follow the ledger guidance in [templates\u002Foutput-template.md](templates\u002Foutput-template.md).\n\n5. **Extract four cornerstone insights.** Name the trigger, job, pains with other solutions, and personal desire. Choose the primary job that best explains the purchase, preserving emotional and social context where supported. Use the extraction rules in [references\u002Fmethod.md](references\u002Fmethod.md). [S1]\n\n6. **Check the buyer's competitive reality.** Include actual workarounds, doing nothing, and category outsiders. Identify what made the existing approach tolerable and what changed. Use the alternatives and edge-case guidance in [references\u002Fmethod.md](references\u002Fmethod.md). [S8]\n\n7. **Choose a fitting psychological move.** Decide whether the key barrier is attention, credibility, belief conflict, or anxiety. Select the relevant presentation rather than stacking fashionable effects. Follow the decision table and explicit warnings in [references\u002Fmethod.md](references\u002Fmethod.md). [S4][S5][S6][S7][S8]\n\n8. **Draft the message and offer.** Express the buyer's situation, desired progress, relevant proof, and next action. Use distinctive buyer language without changing its meaning. Consult [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md) for the transformation from generic claims to focused copy. [S3]\n\n9. **Design and compare trigger tests.** Connect each idea to a buyer, reachable moment, channel, promise, and action. For a team presentation, shortlist three options; recommend one feasible first test. Use the candidate fields in [templates\u002Foutput-template.md](templates\u002Foutput-template.md). [S1]\n\n10. **Make the first test reviewable.** Specify implementation, primary measure, comparison, observation period, constraints, and next learning question. Treat missing baselines and small samples honestly. Follow the experiment rules in [references\u002Fmethod.md](references\u002Fmethod.md); execution remains within the user's authorized scope.\n\n11. **Review, deliver, and learn.** Apply [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md), repair failures, and present the buying story before the recommendation. When results exist, compare behavior with the hypothesis and update the brief. Check attribution against [references\u002Fsources.md](references\u002Fsources.md).\n\n## Files in this skill\n\n- [SKILL.md](SKILL.md): Entry point, use cases, scope, and the main agent loop.\n- [references\u002Fmethod.md](references\u002Fmethod.md): Detailed principles, decision rules, interview prompts, warnings, and edge cases.\n- [references\u002Fsources.md](references\u002Fsources.md): Numbered public sources actually fetched, with their contributions.\n- [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md): Two invented illustrations with weak drafts, improved outputs, and rule notes.\n- [templates\u002Foutput-template.md](templates\u002Foutput-template.md): Fill-in buyer-insight and trigger-test brief with field guidance.\n- [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md): Pass\u002Ffail review criteria, frequent failure modes, and repairs.\n","# Why We Buy: buyer stories to trigger tests\n\nBased on Katelyn Bourgoin's public method. Not affiliated with or endorsed by Katelyn Bourgoin.\n\n## When to use\n\nUse this skill to improve marketing by explaining why a buyer started looking, what progress they wanted, and what made a purchase believable. It produces a buyer-insight and trigger-test brief with usable copy and one recommended experiment. Suitable requests include positioning, offers, landing pages, ads, emails, and acquisition campaigns. Begin with behavior and context, then choose a psychological presentation that fits the evidence. [S1][S2]\n\nUse the full loop when interviews or buying stories are available. With reviews, support notes, or sales conversations alone, use a provisional version and identify the missing evidence. For a narrow copy revision, apply the relevant insight and messaging checks without expanding the assignment into a research program. These scope adaptations are package conventions, not additional claims about Bourgoin's framework.\n\nA finished brief must distinguish buyer evidence, interpretation, and a hypothesis awaiting testing. Do not manufacture buyer quotations, emotional motives, endorsements, urgency, or results to fill empty fields. The method generates useful possibilities from stories; it does not establish that a single story represents a whole market. See [references\u002Fmethod.md](references\u002Fmethod.md) for the evidence rules and exceptions.\n\n## Procedure\n\n1. **Define the decision.** Record the requested deliverable, one growth objective, the intended buyer, and available evidence. Establish the existing metric if known. Use the scope and objective rules in [references\u002Fmethod.md](references\u002Fmethod.md), then open [templates\u002Foutput-template.md](templates\u002Foutput-template.md) as the working brief.\n\n2. **Select a useful informant.** Prefer a recent, best-fit purchaser who obtained value. Before launch, use a recent competitor buyer or someone currently buying a solution. Demographic similarity is insufficient. Follow the recruitment and timing rules in [references\u002Fmethod.md](references\u002Fmethod.md). [S1][S2]\n\n3. **Recover the buying sequence.** Trace the purchase back to the first struggling moment, then reconstruct searches, conversations, alternatives, and decisions. Ask what happened rather than what someone might do. Use the interview prompts in [references\u002Fmethod.md](references\u002Fmethod.md). [S1][S2]\n\n4. **Build an evidence ledger.** Attach a source and timing to each observation. Mark interpretation, unknowns, and contradictions separately. Keep actual buyer wording apart from proposed copy. Follow the ledger guidance in [templates\u002Foutput-template.md](templates\u002Foutput-template.md).\n\n5. **Extract four cornerstone insights.** Name the trigger, job, pains with other solutions, and personal desire. Choose the primary job that best explains the purchase, preserving emotional and social context where supported. Use the extraction rules in [references\u002Fmethod.md](references\u002Fmethod.md). [S1]\n\n6. **Check the buyer's competitive reality.** Include actual workarounds, doing nothing, and category outsiders. Identify what made the existing approach tolerable and what changed. Use the alternatives and edge-case guidance in [references\u002Fmethod.md](references\u002Fmethod.md). [S8]\n\n7. **Choose a fitting psychological move.** Decide whether the key barrier is attention, credibility, belief conflict, or anxiety. Select the relevant presentation rather than stacking fashionable effects. Follow the decision table and explicit warnings in [references\u002Fmethod.md](references\u002Fmethod.md). [S4][S5][S6][S7][S8]\n\n8. **Draft the message and offer.** Express the buyer's situation, desired progress, relevant proof, and next action. Use distinctive buyer language without changing its meaning. Consult [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md) for the transformation from generic claims to focused copy. [S3]\n\n9. **Design and compare trigger tests.** Connect each idea to a buyer, reachable moment, channel, promise, and action. For a team presentation, shortlist three options; recommend one feasible first test. Use the candidate fields in [templates\u002Foutput-template.md](templates\u002Foutput-template.md). [S1]\n\n10. **Make the first test reviewable.** Specify implementation, primary measure, comparison, observation period, constraints, and next learning question. Treat missing baselines and small samples honestly. Follow the experiment rules in [references\u002Fmethod.md](references\u002Fmethod.md); execution remains within the user's authorized scope.\n\n11. **Review, deliver, and learn.** Apply [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md), repair failures, and present the buying story before the recommendation. When results exist, compare behavior with the hypothesis and update the brief. Check attribution against [references\u002Fsources.md](references\u002Fsources.md).\n\n## Files in this skill\n\n- [SKILL.md](SKILL.md): Entry point, use cases, scope, and the main agent loop.\n- [references\u002Fmethod.md](references\u002Fmethod.md): Detailed principles, decision rules, interview prompts, warnings, and edge cases.\n- [references\u002Fsources.md](references\u002Fsources.md): Numbered public sources actually fetched, with their contributions.\n- [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md): Two invented illustrations with weak drafts, improved outputs, and rule notes.\n- [templates\u002Foutput-template.md](templates\u002Foutput-template.md): Fill-in buyer-insight and trigger-test brief with field guidance.\n- [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md): Pass\u002Ffail review criteria, frequent failure modes, and repairs.\n",{"name":5,"description":7},"main","01960aeb08909dbd0c1a2d4f219cdb300099b8b9",0,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills","https:\u002F\u002Fgetedge.cc","https:\u002F\u002Fgithub.com\u002Fgetedgehq","2026-11-12 10:05:02",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add getedgehq\u002Fskills --skill bourgoin-why-we-buy",{"tool":37,"command":38},"bunx","bunx skills add getedgehq\u002Fskills --skill bourgoin-why-we-buy",{"tool":40,"command":41},"pnpm","pnpm dlx skills add getedgehq\u002Fskills --skill bourgoin-why-we-buy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fbourgoin-why-we-buy\u002FSKILL.md",true,[45,51,55,59,63,67,71],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"checklists\u002Freview-checklist.md","REFERENCE","参考文档",5716,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fbourgoin-why-we-buy\u002Fchecklists\u002Freview-checklist.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"DERIVATION.json",2437,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fbourgoin-why-we-buy\u002FDERIVATION.json",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"examples\u002Fworked-examples.md",8552,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fbourgoin-why-we-buy\u002Fexamples\u002Fworked-examples.md",{"path":60,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":15},"LICENSE","许可证",10756,{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fmethod.md",14839,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fbourgoin-why-we-buy\u002Freferences\u002Fmethod.md",{"path":68,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fsources.md",2412,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fbourgoin-why-we-buy\u002Freferences\u002Fsources.md",{"path":72,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":73,"sourceHtmlUrl":74},"templates\u002Foutput-template.md",6092,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fbourgoin-why-we-buy\u002Ftemplates\u002Foutput-template.md",[76,84,92,99,106,114],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7CFVPC1P7JN60J5AN9AZZ5G","zero-downtime-cloud-move","Runbook for moving a live app from one cloud to another (Google Cloud to AWS, AWS to Google Cloud, a PaaS to your own account, or one storage provider to another) without downtime. The agent inventories what is really running, builds the new stack next to the old one, keeps a one-line rollback for every phase, proves the new stack with real workloads before any traffic moves, cuts over with a checklist, watches a fixed window after the switch, copies data with an idempotent job whose second pass must report 0 left, and deletes the old cloud last. Use when someone asks to migrate, move or replatform a production app, switch cloud providers, move a backend, database files or object storage, plan a DNS cutover, or decommission an old cloud account.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzero-downtime-cloud-move\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzero-downtime-cloud-move\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CFVH8VN6G2KE8PBFD1CRMN","zayats-ceo-branding","Build an evidence-based CEO positioning paper, Personal Branding Roadmap, and editorial workflow using Marina Zayats's public method. Use for executive branding, LinkedIn ghostwriting briefs, profile strategy, and recurring CEO-approved content planning.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzayats-ceo-branding\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzayats-ceo-branding\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7CFV9BB7G8K8CX9RKZ3GECX","yc-app-roast","YC App Roast: roast a YC or a16z Speedrun application. Use when a founder wants their YC or Speedrun answers scored, asks \"what would a YC partner think\", wants the weak answers found or rewritten, or wants their draft checked before they submit. Scores every answer 0-10 against public advice from YC and Speedrun partners, names the top issue with the exact words that cost points, and writes a rewrite from the founder's own facts. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fyc-app-roast\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7CFV11Z1HB9EEWFQ6PCJ98X","yc-app-review","YC App Review: get a YC or a16z Speedrun application reviewed by people you trust. Use when a founder wants friends, mentors or alumni to review their YC or Speedrun application, or asks to share their draft for feedback. Builds a shareable review page (one HTML file, application-portal look) where reviewers leave notes per question and press \"Send my notes\" to send them back as text, then parses the notes into proposed rewrites. Optional tracked private links per reviewer. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fyc-app-review\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7CFTSVJV7XCSW62W39MX8CZ","x-growth-playbook","X Growth Playbook. Analyse a person's own X (Twitter) posts and tell them what to post next, with the numbers behind every claim. Compares quote posts vs originals, links vs no links, short vs long, time of day in their timezone, media vs text and the topics they name, reports medians with n, then writes a 10-step plan and the next 7 posts in their voice. Use when the user says \"analyse my X posts\", \"what works on my Twitter\", \"how do I grow on X\", \"what should I post next on X\", \"audit my X account\", or shares an X data archive, X API export or a list of their posts. Runs on the user's computer.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fx-growth-playbook\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fx-growth-playbook\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M7CFTK101S3P00MQ129G5YNH","workplan","Create, update, or close work plans for multi-step tasks. Use when starting refactors, bug lists, feature work, migrations, or any task with 2+ steps. Also use after auto-compaction to re-orient. Triggers: \"workplan\", \"work plan\", \"create a plan\", \"what's the plan\", \"where was I\", or when Claude detects a multi-step task that needs tracking.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fworkplan\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fworkplan\u002FSKILL.md",[],[]]