[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7342WRPZEVCD2SSA1DMH17P":3,"skill-same:01M7342WRPZEVCD2SSA1DMH17P":44},{"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":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":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7342WRPZEVCD2SSA1DMH17P","organic-reach-gtm",null,"Run an organic content-to-pipeline engine — a 3-pillar weekly posting mix (authority, personal, lead-magnet), five post-type skeletons, lead-magnet posts with comment-keyword CTAs, a 3-person content team on a Friday-ready production cycle, authority positioning built from a signature framework and a real proof library, a 4-channel distribution flywheel, and Instagram as a B2B top-of-funnel. Use for \"organic reach\", \"content engine\", \"lead magnet posts\", \"build a content team\", \"authority positioning\", or \"Instagram for B2B\".","LiamVisionary\u002Fhivemindos","LiamVisionary","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F102138294?v=4","01M73379NZZ99TT4ZS17XR3Q9D","01M73379PX6AKQNWN05VNSYRXW",13,"MIT","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fpackaged-skills\u002Foptional\u002Fgtm\u002Fhivemindos\u002Forganic-reach-gtm\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: organic-reach-gtm\ndescription: Run an organic content-to-pipeline engine — a 3-pillar weekly posting mix (authority, personal, lead-magnet), five post-type skeletons, lead-magnet posts with comment-keyword CTAs, a 3-person content team on a Friday-ready production cycle, authority positioning built from a signature framework and a real proof library, a 4-channel distribution flywheel, and Instagram as a B2B top-of-funnel. Use for \"organic reach\", \"content engine\", \"lead magnet posts\", \"build a content team\", \"authority positioning\", or \"Instagram for B2B\".\n---\n\n# Organic Reach GTM\n\nA content engine that converts attention into pipeline instead of likes. Three moving parts: a weekly posting system with conversion built in, a small team that keeps it running without the founder writing everything, and a positioning layer (signature framework + proof library) that makes every post compound toward authority.\n\n**Hard rules:** proof is never fabricated — no invented results, testimonials, or screenshots; real proof or no post. Every comment-keyword CTA creates a DM obligation that a human (or human-approved draft) actually fulfils. Schedule through the platform's native scheduler only — third-party schedulers risk account restrictions. Impression and conversion figures circulating for systems like this are vendor claims, not guarantees.\n\n## The weekly content system\n\n**Three pillars, one week:** authority posts (2–3×: case studies, frameworks, genuinely-held contrarian takes) build credibility; personal posts (1–2×: specific mistakes and what they cost) build trust; lead-magnet posts (1–3×) convert. Five post-type skeletons with slot templates live in this repository's `workflows\u002Fgtm\u002Forganic-reach\u002Ftemplates.json` bank, along with six viral \"wrapper\" shapes (results test, tool list, controversial opinion, case-study breakdown, before\u002Fafter story, system breakdown).\n\n**The lead-magnet post** is the highest-converting type: a bold, real result claim → 3–5 specific components of what's inside → optional social proof → \"comment [KEYWORD] and I'll DM it.\" Hooks trigger desire, curiosity, or fear. Preview media (a sped-up workflow GIF, a blurred screenshot, a results dashboard) raises conversion.\n\n**Writing bar:** 8th-grade reading level, 12–15-word sentences, one idea per line, no AI-tell phrases. The specificity test decides every line: \"we improved our outreach\" fails; \"we went from 6% to 22% reply rates by adding one line about their recent hire\" passes.\n\n**Cadence:** 5 posts\u002Fweek · 10 meaningful comments\u002Fday (5 on ICP posts, 3 on aspirational accounts, 2 on peers — 2–3 sentences referencing a specific point) · reply to every comment on your own posts within ~2 hours.\n\n## The content team\n\nThree roles run it: a **GTM copywriter** (20–30 h\u002Fwk — a strategist who writes: ideation from positioning and real results, all copy, asset briefs, scheduling), a **DM setter\u002FSDR** (15–20 h\u002Fwk — every DM and comment reply, ICP commenting, lead-magnet follow-up, qualification, booking), and a **designer** (10–15 h\u002Fwk — preview media, lead-magnet visuals, 24–48h turnaround). Hire each with a small paid test against your real positioning and results. The production cycle is rolling with one hard deadline: everything for next week written, designed, reviewed, and scheduled by end of Friday; async in comments, one 30-minute weekly sync for performance and positioning only. Add a second account only after 3+ months of 5×\u002Fweek consistency, steady qualified conversations, and a 20+ source-doc backlog — each account gets its own positioning angle.\n\n## Authority positioning\n\nAuthority = specificity + proof + distribution. Own a micro-category via the 4-part formula: a specific **who** (ICP with size and role), a measurable **what** (transformation with numbers and timeframe), a named **how** (your method), and real **proof**. Compress it into one positioning statement and place it everywhere: headline, homepage hero, About, signature, every lead-magnet intro.\n\nBuild a **signature framework** — one memorable 2–4-word name, 3–5 components, a diagram, a before\u002Fafter, real attached proof — and reference it in every post and sales conversation until it *is* the positioning. Underneath it, maintain a **proof library**: 10+ real client results, your own metrics and dashboards, real workflow examples, and 3–5 deep case studies.\n\n**Distribution flywheel:** LinkedIn (core engine) → newsletter (owned weekly deep-dive) → collaborations (guest posts, podcasts, co-created lead magnets) → a repurposing stack that cuts one weekly source document into every other channel. **Metrics that matter:** qualified DM conversations, calls booked, subscribers, clients — with one north star: revenue from inbound. Track proof output too (2–3 new case studies a quarter).\n\n## Instagram as B2B top-of-funnel (bonus channel)\n\nRun the fit test first: Instagram works for low-friction PLG tools, visually-provable services aimed at SMBs and founders, and info products — not for enterprise cycles, demo-led products, or committee purchases. Its job is strictly top-of-funnel: attention → problem awareness → one micro-conversion. Every post teaches one tactical thing completely in under 90 seconds, creates a gap, and points to a lead magnet (caption CTA + bio link, zero-friction download). Never sell directly — intercept with value, then move people to a buying environment. Downloads pre-qualify by topic: what someone grabs tells you their pain, their stack, and that they act. For cold traffic, free trials outperform demos: instant access, zero friction, self-qualification.\n\n## The source-content system (write once, distribute everywhere)\n\nA tighter repurposing discipline: write **one deep source piece a week** (a full case study, a step-by-step breakdown, a contrarian take with evidence, or a real framework — 30–60 minutes once), then break it into a **7-day run** (contrarian hook, step-by-step, mistake post, proof post, thread version, carousel, long newsletter) and repurpose across LinkedIn, threads, short-form video, newsletter, and community. Roughly one source becomes seven-plus pieces; four sources a month is twenty-eight-plus posts on about four hours of creation, the rest distribution.\n\nThree **convert-buckets** frame what to post: proof & results (build authority — real case studies, screenshots, permissioned wins, before\u002Fafter, dashboards), education (demonstrate expertise — how-tos, applicable frameworks, tool tutorials), and identity & beliefs (create movement — genuinely-held opinions, what you stand against, reasoned predictions). Run a **60-minute daily rhythm**: a ~45-minute morning block (post, reply to every comment for 45 minutes, clear DMs, engage 5–10 ICP posts) and a ~15-minute evening block (engage more ICP posts, DM 2nd-degree ICP connections who engaged, save winners to a swipe file). A workable **weekly schedule**: Monday framework, Tuesday case study, Wednesday lead magnet, Thursday contrarian truth, Friday proof, weekend optional personal — posting windows around 8–9am, 12–1pm, and 5–6pm local to test.\n\n**Content becomes pipeline** when you treat engagement on your own posts as a warm signal: filter likers and commenters for ICP fit and route matches to a human-approved DM; deliver lead-magnet resources and follow up in about 48 hours. Capture only through platform-native surfaces or manual review with human-approved DMs — third-party engager-scrapers and fully-automated mass-DM tools violate platform terms and are never used. Bank rows: `sourceContentMethod`, `convertBuckets`, `dailyRhythm`, `ctaByGoal`, `weeklySchedule`, `contentToPipeline`.\n\nCompanions: `linkedin-gtm` (hooks, warming, outreach core, the same buyer-signal capture as a full-funnel layer), `b2b-social-gtm` (voice files and repurposing), `reddit-gtm` and `x-warm-outreach-gtm` (the warm-before-ask channels).\n","# Organic Reach GTM\n\nA content engine that converts attention into pipeline instead of likes. Three moving parts: a weekly posting system with conversion built in, a small team that keeps it running without the founder writing everything, and a positioning layer (signature framework + proof library) that makes every post compound toward authority.\n\n**Hard rules:** proof is never fabricated — no invented results, testimonials, or screenshots; real proof or no post. Every comment-keyword CTA creates a DM obligation that a human (or human-approved draft) actually fulfils. Schedule through the platform's native scheduler only — third-party schedulers risk account restrictions. Impression and conversion figures circulating for systems like this are vendor claims, not guarantees.\n\n## The weekly content system\n\n**Three pillars, one week:** authority posts (2–3×: case studies, frameworks, genuinely-held contrarian takes) build credibility; personal posts (1–2×: specific mistakes and what they cost) build trust; lead-magnet posts (1–3×) convert. Five post-type skeletons with slot templates live in this repository's `workflows\u002Fgtm\u002Forganic-reach\u002Ftemplates.json` bank, along with six viral \"wrapper\" shapes (results test, tool list, controversial opinion, case-study breakdown, before\u002Fafter story, system breakdown).\n\n**The lead-magnet post** is the highest-converting type: a bold, real result claim → 3–5 specific components of what's inside → optional social proof → \"comment [KEYWORD] and I'll DM it.\" Hooks trigger desire, curiosity, or fear. Preview media (a sped-up workflow GIF, a blurred screenshot, a results dashboard) raises conversion.\n\n**Writing bar:** 8th-grade reading level, 12–15-word sentences, one idea per line, no AI-tell phrases. The specificity test decides every line: \"we improved our outreach\" fails; \"we went from 6% to 22% reply rates by adding one line about their recent hire\" passes.\n\n**Cadence:** 5 posts\u002Fweek · 10 meaningful comments\u002Fday (5 on ICP posts, 3 on aspirational accounts, 2 on peers — 2–3 sentences referencing a specific point) · reply to every comment on your own posts within ~2 hours.\n\n## The content team\n\nThree roles run it: a **GTM copywriter** (20–30 h\u002Fwk — a strategist who writes: ideation from positioning and real results, all copy, asset briefs, scheduling), a **DM setter\u002FSDR** (15–20 h\u002Fwk — every DM and comment reply, ICP commenting, lead-magnet follow-up, qualification, booking), and a **designer** (10–15 h\u002Fwk — preview media, lead-magnet visuals, 24–48h turnaround). Hire each with a small paid test against your real positioning and results. The production cycle is rolling with one hard deadline: everything for next week written, designed, reviewed, and scheduled by end of Friday; async in comments, one 30-minute weekly sync for performance and positioning only. Add a second account only after 3+ months of 5×\u002Fweek consistency, steady qualified conversations, and a 20+ source-doc backlog — each account gets its own positioning angle.\n\n## Authority positioning\n\nAuthority = specificity + proof + distribution. Own a micro-category via the 4-part formula: a specific **who** (ICP with size and role), a measurable **what** (transformation with numbers and timeframe), a named **how** (your method), and real **proof**. Compress it into one positioning statement and place it everywhere: headline, homepage hero, About, signature, every lead-magnet intro.\n\nBuild a **signature framework** — one memorable 2–4-word name, 3–5 components, a diagram, a before\u002Fafter, real attached proof — and reference it in every post and sales conversation until it *is* the positioning. Underneath it, maintain a **proof library**: 10+ real client results, your own metrics and dashboards, real workflow examples, and 3–5 deep case studies.\n\n**Distribution flywheel:** LinkedIn (core engine) → newsletter (owned weekly deep-dive) → collaborations (guest posts, podcasts, co-created lead magnets) → a repurposing stack that cuts one weekly source document into every other channel. **Metrics that matter:** qualified DM conversations, calls booked, subscribers, clients — with one north star: revenue from inbound. Track proof output too (2–3 new case studies a quarter).\n\n## Instagram as B2B top-of-funnel (bonus channel)\n\nRun the fit test first: Instagram works for low-friction PLG tools, visually-provable services aimed at SMBs and founders, and info products — not for enterprise cycles, demo-led products, or committee purchases. Its job is strictly top-of-funnel: attention → problem awareness → one micro-conversion. Every post teaches one tactical thing completely in under 90 seconds, creates a gap, and points to a lead magnet (caption CTA + bio link, zero-friction download). Never sell directly — intercept with value, then move people to a buying environment. Downloads pre-qualify by topic: what someone grabs tells you their pain, their stack, and that they act. For cold traffic, free trials outperform demos: instant access, zero friction, self-qualification.\n\n## The source-content system (write once, distribute everywhere)\n\nA tighter repurposing discipline: write **one deep source piece a week** (a full case study, a step-by-step breakdown, a contrarian take with evidence, or a real framework — 30–60 minutes once), then break it into a **7-day run** (contrarian hook, step-by-step, mistake post, proof post, thread version, carousel, long newsletter) and repurpose across LinkedIn, threads, short-form video, newsletter, and community. Roughly one source becomes seven-plus pieces; four sources a month is twenty-eight-plus posts on about four hours of creation, the rest distribution.\n\nThree **convert-buckets** frame what to post: proof & results (build authority — real case studies, screenshots, permissioned wins, before\u002Fafter, dashboards), education (demonstrate expertise — how-tos, applicable frameworks, tool tutorials), and identity & beliefs (create movement — genuinely-held opinions, what you stand against, reasoned predictions). Run a **60-minute daily rhythm**: a ~45-minute morning block (post, reply to every comment for 45 minutes, clear DMs, engage 5–10 ICP posts) and a ~15-minute evening block (engage more ICP posts, DM 2nd-degree ICP connections who engaged, save winners to a swipe file). A workable **weekly schedule**: Monday framework, Tuesday case study, Wednesday lead magnet, Thursday contrarian truth, Friday proof, weekend optional personal — posting windows around 8–9am, 12–1pm, and 5–6pm local to test.\n\n**Content becomes pipeline** when you treat engagement on your own posts as a warm signal: filter likers and commenters for ICP fit and route matches to a human-approved DM; deliver lead-magnet resources and follow up in about 48 hours. Capture only through platform-native surfaces or manual review with human-approved DMs — third-party engager-scrapers and fully-automated mass-DM tools violate platform terms and are never used. Bank rows: `sourceContentMethod`, `convertBuckets`, `dailyRhythm`, `ctaByGoal`, `weeklySchedule`, `contentToPipeline`.\n\nCompanions: `linkedin-gtm` (hooks, warming, outreach core, the same buyer-signal capture as a full-funnel layer), `b2b-social-gtm` (voice files and repurposing), `reddit-gtm` and `x-warm-outreach-gtm` (the warm-before-ask channels).\n",{"name":5,"description":7},"main","f270c4ae4f9d09c4e5da9cfa8adab7e89ae1f53e","packaged-skills\u002Foptional\u002Fgtm\u002Fhivemindos\u002Forganic-reach-gtm",4,"https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos","https:\u002F\u002Fgithub.com\u002FLiamVisionary","2026-11-10 21:48:41",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add LiamVisionary\u002Fhivemindos --skill organic-reach-gtm",{"tool":36,"command":37},"bunx","bunx skills add LiamVisionary\u002Fhivemindos --skill organic-reach-gtm",{"tool":39,"command":40},"pnpm","pnpm dlx skills add LiamVisionary\u002Fhivemindos --skill organic-reach-gtm","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fpackaged-skills\u002Foptional\u002Fgtm\u002Fhivemindos\u002Forganic-reach-gtm\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M734AA85KQEXDQXQJ3T7769M","tailscale-generation-skill-authoring","This skill should be used when the user asks to \"create a Tailscale generation skill\", \"add a local generation skill\", \"document a generation endpoint\", \"add an image generation provider\", \"add a TTS provider\", \"add video generation\", \"add 3D generation\", or needs guidance on where HivemindOS Tailscale or local generation providers belong in the shared skills shelf.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fskills\u002Ftailscale-generation-skill-authoring\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M734A7VD69PRA0C0EV5EFY9T","localtts","This skill should be used when the user asks to \"generate local TTS\", \"use local text to speech\", \"use remote TTS over Tailscale\", \"make speech audio\", \"add a TTS provider\", \"use Qwen3-TTS\", or needs TTS endpoint setup through local or HivemindOS Tailscale routes.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fskills\u002Flocaltts\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M734A4K2Z0F74QZP7V7WBFRY","karpathy-guidelines","Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fskills\u002Fkarpathy-guidelines\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M734A1HMVYVJX3YJGNQ6KF6C","comfyui-image-generation","This skill should be used when the user asks to \"generate images\", \"generate images with ComfyUI\", \"use local ComfyUI\", \"use remote ComfyUI\", \"use Z-Image\", \"add an image generation provider\", or needs image-generation endpoint setup through local or HivemindOS Tailscale routes.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fskills\u002Fcomfyui-image-generation\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M7349Y684Q676DNNHZPSC8W1","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fskills\u002Fcloudflare\u002Fwrangler\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7349V3WCBF835QP74SA9Q8C","workers-best-practices","Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fskills\u002Fcloudflare\u002Fworkers-best-practices\u002FSKILL.md",[],[]]