[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CFGAYM8MKNTWJM9WKN1V4F":3,"skill-same:01M7CFGAYM8MKNTWJM9WKN1V4F":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},"01M7CFGAYM8MKNTWJM9WKN1V4F","poyar-growth-unhinged",null,"Build evidence-based B2B software growth and monetization playbooks using Kyle Poyar's public approach. Use to diagnose growth bottlenecks, connect PLG with sales, redesign pricing and packaging, or plan account expansion.","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\u002Fpoyar-growth-unhinged\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fpoyar-growth-unhinged\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: poyar-growth-unhinged\ndescription: \"Build evidence-based B2B software growth and monetization playbooks using Kyle Poyar's public approach. Use to diagnose growth bottlenecks, connect PLG with sales, redesign pricing and packaging, or plan account expansion.\"\n---\n\n# Growth Unhinged GTM and Monetization Playbooks\n\nBased on Kyle Poyar's public method. Not affiliated with or endorsed by Kyle Poyar.\n\n## When to use\n\nUse this skill when a B2B software team needs a decision about growth, pricing, packaging, product-led sales, or expansion. Produce a practical decision memo that connects customer value, account progression, payment, and business economics. Begin with the customer journey rather than choosing a sales tactic or pricing model in advance. Product can drive acquisition, conversion, and expansion. [S1]\n\nThis package synthesizes public writing and interviews, including practitioner cases published by Poyar. He did not publish this exact combined framework. Only public previews of subscription articles informed the method. Historical company examples illustrate mechanisms, not current benchmarks. Distinguish direct advice, interviewee practices, and this package's operational suggestions using [references\u002Fmethod.md](references\u002Fmethod.md) and [references\u002Fsources.md](references\u002Fsources.md).\n\nFor a narrow request, complete the relevant analysis and mark other memo fields as outside scope. Do not expand a pricing-page review into an unsolicited company-wide redesign. When evidence is thin, deliver a provisional diagnosis and the next learning action. Recommend live experiments or changes within the user's scope; the skill itself does not authorize publishing prices or contacting customers.\n\n## Procedure\n\n1. **Frame the decision and evidence.** Read the evidence boundaries in [references\u002Fmethod.md](references\u002Fmethod.md#evidence-and-attribution). Capture the product, target customer, existing motion, requested decision, constraints, and available data. Separate observed facts, customer statements, calculated results, and assumptions. Start the decision memo in [templates\u002Foutput-template.md](templates\u002Foutput-template.md).\n\n2. **Locate the limiting journey stage.** Follow [references\u002Fmethod.md](references\u002Fmethod.md#1-diagnose-the-customer-journey). Map discover, start, activate, convert, and scale with cohort denominators and time windows. Identify where customers fail to realize or extend value. Choose one primary bottleneck and explain competing explanations rather than treating every low conversion rate as a sales problem. [S1]\n\n3. **Select accounts worth winning.** Use [references\u002Fmethod.md](references\u002Fmethod.md#2-focus-on-best-fit-accounts) to compare segments on product fit, win probability, deal size, sales cycle, retention, and expansion. Connect contacts, usage, buying progress, and revenue at account level. Measure progression among best-fit accounts; lead counts and attribution credit are insufficient evidence of effectiveness. [S6]\n\n4. **Define the adoption bridge.** Apply [references\u002Fmethod.md](references\u002Fmethod.md#3-move-from-individual-value-to-team-value). State the meaningful activation behavior and how an individual becomes a team champion. Check whether collaboration, invitations, or billing gates block wider adoption. Treat Figma's first-week collaboration example as a case, not a universal threshold. [S2] [S5]\n\n5. **Choose the chargeable metric.** Use [references\u002Fmethod.md](references\u002Fmethod.md#4-select-the-pricing-unit). Compare plausible units against customer value, easy entry, expansion, predictability, and measurement feasibility. Calculate illustrative new, expanding, and mature customer bills. Keep seats when they fit; do not select consumption merely because usage pricing is fashionable. [S7] [S8]\n\n6. **Design packages and graduation triggers.** Follow [references\u002Fmethod.md](references\u002Fmethod.md#5-build-packages-with-jobs). Start with good, better, best unless context supports another structure. Give each package a customer, buying reason, and expansion trigger. Test candidate add-ons against separate demand, buyer, timing, alternatives, and delivery cost. [S3]\n\n7. **Place sales where it helps.** Apply [references\u002Fmethod.md](references\u002Fmethod.md#6-make-sales-incremental-and-reach-the-buyer). Specify the account signal, customer problem, assistance, champion, economic buyer, and intended incremental result. Preserve useful self-service. Plan a comparison that distinguishes sales contribution from purchases that would happen anyway. [S4] [S5]\n\n8. **Resolve purchasing and billing friction.** Use [references\u002Fmethod.md](references\u002Fmethod.md#7-balance-flexibility-and-predictability). Explain the landing offer and pricing page in customer language. For consumption models, state allowances, commitments, overages, underuse, seasonality, and spend controls. Match predictability to customer needs without forcing an oversized initial purchase. [S7] [S8] [S9]\n\n9. **Build a bounded learning plan.** Follow [references\u002Fmethod.md](references\u002Fmethod.md#8-research-and-pilot-before-rollout). Begin with independent win-loss evidence, then choose package research, usability testing, or a limited pricing pilot. Record owner, cohort, duration, comparison, success criteria, stop criteria, and bias. Proposed thresholds are local decisions, not expert benchmarks. [S7] [S8]\n\n10. **Check economics and incentives.** Apply [references\u002Fmethod.md](references\u002Fmethod.md#9-evaluate-economics-and-incentives). Link usage forecasts, retention, recognized revenue, acquisition costs, and service costs. Distinguish cash collection from economic payback. Check whether seller incentives reward customer success or simply discounted commitments. [S9]\n\n11. **Review and deliver the decision.** Complete [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md), using [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md) to calibrate specificity. Revise failed checks, label unresolved evidence, and deliver the memo with the recommended next action. Revisit pricing as the product and customers evolve; one successful pilot does not establish a permanent optimum. [S8]\n\n## Files in this skill\n\n- [SKILL.md](SKILL.md): Entry point, use cases, evidence boundaries, and the agent's main loop.\n- [references\u002Fmethod.md](references\u002Fmethod.md): Detailed principles, decision rules, warnings, and edge cases.\n- [references\u002Fsources.md](references\u002Fsources.md): Nine fetched public sources and their contributions.\n- [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md): Two invented before-and-after decision memos with rule notes.\n- [templates\u002Foutput-template.md](templates\u002Foutput-template.md): Fill-in decision memo with field-by-field guidance.\n- [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md): Pass\u002Ffail review criteria and common failure repairs.\n","# Growth Unhinged GTM and Monetization Playbooks\n\nBased on Kyle Poyar's public method. Not affiliated with or endorsed by Kyle Poyar.\n\n## When to use\n\nUse this skill when a B2B software team needs a decision about growth, pricing, packaging, product-led sales, or expansion. Produce a practical decision memo that connects customer value, account progression, payment, and business economics. Begin with the customer journey rather than choosing a sales tactic or pricing model in advance. Product can drive acquisition, conversion, and expansion. [S1]\n\nThis package synthesizes public writing and interviews, including practitioner cases published by Poyar. He did not publish this exact combined framework. Only public previews of subscription articles informed the method. Historical company examples illustrate mechanisms, not current benchmarks. Distinguish direct advice, interviewee practices, and this package's operational suggestions using [references\u002Fmethod.md](references\u002Fmethod.md) and [references\u002Fsources.md](references\u002Fsources.md).\n\nFor a narrow request, complete the relevant analysis and mark other memo fields as outside scope. Do not expand a pricing-page review into an unsolicited company-wide redesign. When evidence is thin, deliver a provisional diagnosis and the next learning action. Recommend live experiments or changes within the user's scope; the skill itself does not authorize publishing prices or contacting customers.\n\n## Procedure\n\n1. **Frame the decision and evidence.** Read the evidence boundaries in [references\u002Fmethod.md](references\u002Fmethod.md#evidence-and-attribution). Capture the product, target customer, existing motion, requested decision, constraints, and available data. Separate observed facts, customer statements, calculated results, and assumptions. Start the decision memo in [templates\u002Foutput-template.md](templates\u002Foutput-template.md).\n\n2. **Locate the limiting journey stage.** Follow [references\u002Fmethod.md](references\u002Fmethod.md#1-diagnose-the-customer-journey). Map discover, start, activate, convert, and scale with cohort denominators and time windows. Identify where customers fail to realize or extend value. Choose one primary bottleneck and explain competing explanations rather than treating every low conversion rate as a sales problem. [S1]\n\n3. **Select accounts worth winning.** Use [references\u002Fmethod.md](references\u002Fmethod.md#2-focus-on-best-fit-accounts) to compare segments on product fit, win probability, deal size, sales cycle, retention, and expansion. Connect contacts, usage, buying progress, and revenue at account level. Measure progression among best-fit accounts; lead counts and attribution credit are insufficient evidence of effectiveness. [S6]\n\n4. **Define the adoption bridge.** Apply [references\u002Fmethod.md](references\u002Fmethod.md#3-move-from-individual-value-to-team-value). State the meaningful activation behavior and how an individual becomes a team champion. Check whether collaboration, invitations, or billing gates block wider adoption. Treat Figma's first-week collaboration example as a case, not a universal threshold. [S2] [S5]\n\n5. **Choose the chargeable metric.** Use [references\u002Fmethod.md](references\u002Fmethod.md#4-select-the-pricing-unit). Compare plausible units against customer value, easy entry, expansion, predictability, and measurement feasibility. Calculate illustrative new, expanding, and mature customer bills. Keep seats when they fit; do not select consumption merely because usage pricing is fashionable. [S7] [S8]\n\n6. **Design packages and graduation triggers.** Follow [references\u002Fmethod.md](references\u002Fmethod.md#5-build-packages-with-jobs). Start with good, better, best unless context supports another structure. Give each package a customer, buying reason, and expansion trigger. Test candidate add-ons against separate demand, buyer, timing, alternatives, and delivery cost. [S3]\n\n7. **Place sales where it helps.** Apply [references\u002Fmethod.md](references\u002Fmethod.md#6-make-sales-incremental-and-reach-the-buyer). Specify the account signal, customer problem, assistance, champion, economic buyer, and intended incremental result. Preserve useful self-service. Plan a comparison that distinguishes sales contribution from purchases that would happen anyway. [S4] [S5]\n\n8. **Resolve purchasing and billing friction.** Use [references\u002Fmethod.md](references\u002Fmethod.md#7-balance-flexibility-and-predictability). Explain the landing offer and pricing page in customer language. For consumption models, state allowances, commitments, overages, underuse, seasonality, and spend controls. Match predictability to customer needs without forcing an oversized initial purchase. [S7] [S8] [S9]\n\n9. **Build a bounded learning plan.** Follow [references\u002Fmethod.md](references\u002Fmethod.md#8-research-and-pilot-before-rollout). Begin with independent win-loss evidence, then choose package research, usability testing, or a limited pricing pilot. Record owner, cohort, duration, comparison, success criteria, stop criteria, and bias. Proposed thresholds are local decisions, not expert benchmarks. [S7] [S8]\n\n10. **Check economics and incentives.** Apply [references\u002Fmethod.md](references\u002Fmethod.md#9-evaluate-economics-and-incentives). Link usage forecasts, retention, recognized revenue, acquisition costs, and service costs. Distinguish cash collection from economic payback. Check whether seller incentives reward customer success or simply discounted commitments. [S9]\n\n11. **Review and deliver the decision.** Complete [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md), using [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md) to calibrate specificity. Revise failed checks, label unresolved evidence, and deliver the memo with the recommended next action. Revisit pricing as the product and customers evolve; one successful pilot does not establish a permanent optimum. [S8]\n\n## Files in this skill\n\n- [SKILL.md](SKILL.md): Entry point, use cases, evidence boundaries, and the agent's main loop.\n- [references\u002Fmethod.md](references\u002Fmethod.md): Detailed principles, decision rules, warnings, and edge cases.\n- [references\u002Fsources.md](references\u002Fsources.md): Nine fetched public sources and their contributions.\n- [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md): Two invented before-and-after decision memos with rule notes.\n- [templates\u002Foutput-template.md](templates\u002Foutput-template.md): Fill-in decision memo with field-by-field guidance.\n- [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md): Pass\u002Ffail review criteria and common failure 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 poyar-growth-unhinged",{"tool":37,"command":38},"bunx","bunx skills add getedgehq\u002Fskills --skill poyar-growth-unhinged",{"tool":40,"command":41},"pnpm","pnpm dlx skills add getedgehq\u002Fskills --skill poyar-growth-unhinged","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fpoyar-growth-unhinged\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","参考文档",6968,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fpoyar-growth-unhinged\u002Fchecklists\u002Freview-checklist.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"DERIVATION.json",2605,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fpoyar-growth-unhinged\u002FDERIVATION.json",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"examples\u002Fworked-examples.md",10367,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fpoyar-growth-unhinged\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",17930,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fpoyar-growth-unhinged\u002Freferences\u002Fmethod.md",{"path":68,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fsources.md",3233,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fpoyar-growth-unhinged\u002Freferences\u002Fsources.md",{"path":72,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":73,"sourceHtmlUrl":74},"templates\u002Foutput-template.md",7466,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fpoyar-growth-unhinged\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",[],[]]