[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AEW70WENEM1ZPASE8D1SE4":3,"skill-same:01M7AEW70WENEM1ZPASE8D1SE4":45},{"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7AEW70WENEM1ZPASE8D1SE4","go-to-market",null,"Plan how the company reaches its first or next customers - who exactly, why they would choose it, what to say, where to find them, what to charge, and a first month of measured experiments. Use for a launch, a new audience or a stalled channel; do not use to run campaigns or spend money (that needs the owner's approval, per action).","BlueprintLabIO\u002Frestless-core","BlueprintLabIO","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F222796351?v=4","01M7AETKD0TZXRAGH2WAKGNYE6","01M7AETKE63A80017SD5ZWAEF4",12,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Fgo-to-market\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: go-to-market\ndescription: Plan how the company reaches its first or next customers - who exactly, why they would choose it, what to say, where to find them, what to charge, and a first month of measured experiments. Use for a launch, a new audience or a stalled channel; do not use to run campaigns or spend money (that needs the owner's approval, per action).\n---\n\n# Go to market\n\nA plan is a set of bets about who will buy and why, cheap to test before anything is spent. Build it\nfrom what the company already knows, test the riskiest bet first, and keep everything that leaves\nthe company in the owner's hands.\n\n## 1. Gather what is known\n\nRead the charter, Brand & voice and Goals (`restless charter show`, `restless identity show`,\n`restless goal list`). If there is no competitor research for this market from the last few months,\nrun the competitor-research skill first. Note what the owner already tried and what happened.\n\n## 2. Who, exactly\n\nDescribe the best-fit customer so a stranger could find ten of them:\n\n- who they are (role, kind of business or household, size, place);\n- the trigger that makes them look now (a new job, a failure, a season, a rule change);\n- what they use today instead, and what annoys them about it;\n- where they already spend attention (communities, searches, events, publications).\n\nName the two or three groups worth testing; do not try to reach everyone.\n\n## 3. Why us: positioning\n\nWork it out in this order, each in a sentence, from evidence:\n\n1. **The alternatives** the customer would otherwise use (from the competitor research).\n2. **What only we have** compared with those alternatives.\n3. **The value** that gives the customer, in their terms (time, money, risk, status).\n4. **Who cares most** about that value (the best-fit customer above).\n5. **The category** that makes the value obvious (\"a mobile bike mechanic\", not \"a platform\").\n\nThen the message: a headline, a one-line explanation, and three proof points, in the company's\nvoice. Offer two or three alternative headlines for the owner to choose between.\n\n## 4. Where and how much\n\n- **Channels:** list candidates, then rank them by how fast they give a signal, effort, cost and\n  fit with where the customer already is. Pick two to test first.\n- **Price:** a hypothesis anchored on the alternatives' prices and the value, with the cheapest\n  way to test it (a pricing page, a pre-order, three sales conversations). Say what would change\n  it.\n\n## 5. Launch and a first month of experiments\n\n- **Launch plan:** the assets needed (a landing page, a deck, an announcement, a listing), in\n  order, with who makes each. Hand assets to the landing-page-design and presentation-deck skills.\n- **Experiments:** a sheet (`restless sheet create \"Go-to-market experiments\"`) with one row per\n  bet, added with an `import_csv` action (`restless sheet edit \u003Csheet> @rows.json`). Columns:\n  hypothesis, action, metric, success threshold, cost, effort, owner, start and end. Order by the\n  riskiest assumption first. Five to eight is enough for a month.\n- **Measure:** propose one to three Goals for the month (`restless goal add` only once the owner\n  agrees), each with an observable finish line.\n\n## 6. Write it up\n\nPublish a Library document (`restless document create --kind plan`):\n\n1. **The plan in five lines:** who, why us, the message, the two channels, the price to test.\n2. **Customer, positioning, message** with the evidence behind each.\n3. **Channels and price** with the ranking and its reasons.\n4. **Launch and experiments** linking the sheet.\n5. **Risks and what we will learn first.**\n6. **Sources.**\n\nAsk the owner to choose the headline and confirm the two channels and the price to test, with\nthose as quick replies.\n\n## Rules\n\n- Draft, never send. Posts, emails, outreach, ads, listings, sign-ups and any spend go through the\n  owner's approval for each action, by the company's normal authority path.\n- No claims the company cannot back up, no fake reviews or testimonials, no buying followers or\n  contact lists, no messaging people who did not ask, and respect each platform's rules.\n- Facts about markets and competitors follow the research skill's sourcing rules.\n- The company's voice applies to every line a customer will read (`restless identity show`).\n\nCredits: the positioning steps follow the widely used order of alternatives, unique attributes,\nvalue, best-fit customers and market category (as popularised by April Dunford's \"Obviously\nAwesome\"), written in our own words.\n","# Go to market\n\nA plan is a set of bets about who will buy and why, cheap to test before anything is spent. Build it\nfrom what the company already knows, test the riskiest bet first, and keep everything that leaves\nthe company in the owner's hands.\n\n## 1. Gather what is known\n\nRead the charter, Brand & voice and Goals (`restless charter show`, `restless identity show`,\n`restless goal list`). If there is no competitor research for this market from the last few months,\nrun the competitor-research skill first. Note what the owner already tried and what happened.\n\n## 2. Who, exactly\n\nDescribe the best-fit customer so a stranger could find ten of them:\n\n- who they are (role, kind of business or household, size, place);\n- the trigger that makes them look now (a new job, a failure, a season, a rule change);\n- what they use today instead, and what annoys them about it;\n- where they already spend attention (communities, searches, events, publications).\n\nName the two or three groups worth testing; do not try to reach everyone.\n\n## 3. Why us: positioning\n\nWork it out in this order, each in a sentence, from evidence:\n\n1. **The alternatives** the customer would otherwise use (from the competitor research).\n2. **What only we have** compared with those alternatives.\n3. **The value** that gives the customer, in their terms (time, money, risk, status).\n4. **Who cares most** about that value (the best-fit customer above).\n5. **The category** that makes the value obvious (\"a mobile bike mechanic\", not \"a platform\").\n\nThen the message: a headline, a one-line explanation, and three proof points, in the company's\nvoice. Offer two or three alternative headlines for the owner to choose between.\n\n## 4. Where and how much\n\n- **Channels:** list candidates, then rank them by how fast they give a signal, effort, cost and\n  fit with where the customer already is. Pick two to test first.\n- **Price:** a hypothesis anchored on the alternatives' prices and the value, with the cheapest\n  way to test it (a pricing page, a pre-order, three sales conversations). Say what would change\n  it.\n\n## 5. Launch and a first month of experiments\n\n- **Launch plan:** the assets needed (a landing page, a deck, an announcement, a listing), in\n  order, with who makes each. Hand assets to the landing-page-design and presentation-deck skills.\n- **Experiments:** a sheet (`restless sheet create \"Go-to-market experiments\"`) with one row per\n  bet, added with an `import_csv` action (`restless sheet edit \u003Csheet> @rows.json`). Columns:\n  hypothesis, action, metric, success threshold, cost, effort, owner, start and end. Order by the\n  riskiest assumption first. Five to eight is enough for a month.\n- **Measure:** propose one to three Goals for the month (`restless goal add` only once the owner\n  agrees), each with an observable finish line.\n\n## 6. Write it up\n\nPublish a Library document (`restless document create --kind plan`):\n\n1. **The plan in five lines:** who, why us, the message, the two channels, the price to test.\n2. **Customer, positioning, message** with the evidence behind each.\n3. **Channels and price** with the ranking and its reasons.\n4. **Launch and experiments** linking the sheet.\n5. **Risks and what we will learn first.**\n6. **Sources.**\n\nAsk the owner to choose the headline and confirm the two channels and the price to test, with\nthose as quick replies.\n\n## Rules\n\n- Draft, never send. Posts, emails, outreach, ads, listings, sign-ups and any spend go through the\n  owner's approval for each action, by the company's normal authority path.\n- No claims the company cannot back up, no fake reviews or testimonials, no buying followers or\n  contact lists, no messaging people who did not ask, and respect each platform's rules.\n- Facts about markets and competitors follow the research skill's sourcing rules.\n- The company's voice applies to every line a customer will read (`restless identity show`).\n\nCredits: the positioning steps follow the widely used order of alternatives, unique attributes,\nvalue, best-fit customers and market category (as popularised by April Dunford's \"Obviously\nAwesome\"), written in our own words.\n",{"name":5,"description":7},"main","74448c875ccc3d826c90b46381cc63698ba769aa","infra\u002Fcompany-image\u002Fskills\u002Fgo-to-market",1,"https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core","https:\u002F\u002Frestless.run","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO","2026-11-14 10:29:34",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add BlueprintLabIO\u002Frestless-core --skill go-to-market",{"tool":37,"command":38},"bunx","bunx skills add BlueprintLabIO\u002Frestless-core --skill go-to-market",{"tool":40,"command":41},"pnpm","pnpm dlx skills add BlueprintLabIO\u002Frestless-core --skill go-to-market","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Fgo-to-market\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7AEXHE6CPB3TMHWKEMDWYM7","fixture-note-etiquette","How the company writes a Fixture Notes message. Used only by the connections smoke.","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Ftools\u002Ffixture-mcp-provider\u002Ffixtures\u002Fplugin\u002Fskills\u002Ffixture-note-etiquette\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7AEXC9H7TTENFY1S87TQZF5","web-native-review","Prepare or independently review a rendered website against its outcome contract and a mature ground-truth reference. Use for landing pages, product sites, blogs, documentation sites, or other browser-native outcomes; do not use to judge source code alone or turn mechanical layout facts into a taste score.","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Fweb-native-review\u002FSKILL.md",[],[],{"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":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7AEX8KTGCGTDHKMKRMV25AS","scenario-evidence","Run a versioned Runtime scenario, probe its real capabilities, preserve compact evidence, and prepare its native review target. Use for a project outcome that benefits from repeatable setup\u002Frun\u002Fassertion\u002Fevidence—not to choose a plan, team, or business verdict.","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Fscenario-evidence\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7AEX433AM2YZ08ST66G3FF5","research","Answer a question the company needs to decide on with a sourced brief - market facts, a technology, a regulation, an audience, a price, a supplier. Use when an answer must be found and checked on the web or in documents before acting; do not use for a quick lookup a single source settles, or for competitor landscapes (use competitor-research).","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7AEWYCTNC5VF57C9PQF1X4W","reference-led-reset","Reset a rejected or repeatedly drifting outcome into a genuinely fresh Work Attempt grounded in ordered authoritative references. Use when the owner asks to start over, when qualitative defects survive revision, or when a mechanically valid result conflicts with the product or brand source of truth. Do not use for an ordinary bounded repair that should preserve the current candidate.","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Freference-led-reset\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7AEWV2KP5JM50T3S7VD7HR9","publish-git","Safely reconcile, verify, and publish Git refs through the governed Restless effect path. Use for pushes or deployments driven by a Git push; do not use for read-only fetches, local Git work, or provider API administration.","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Fpublish-git\u002FSKILL.md",[],[]]