[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70G84DTTDA0N0FF5F83Q8BG":3,"skill-same:01M70G84DTTDA0N0FF5F83Q8BG":66},{"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":18,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M70G84DTTDA0N0FF5F83Q8BG","investor-outreach",null,"Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising. Use when the user wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized, investor-facing messaging.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Finvestor-outreach\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"investor outreach","outreach","user","concise","draft","intro","use","strategic","emails","for","investors","fundraising","update","communications","when","cold","messaging","follow-ups","2026-11-10 10:12:30",false,"---\nname: investor-outreach\ndescription: Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising. Use when the user wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized, investor-facing messaging.\nmetadata:\n  origin: ECC\n---\n\n# Investor Outreach\n\nWrite investor communication that is short, concrete, and easy to act on.\n\n## When to Activate\n\n- writing a cold email to an investor\n- drafting a warm intro request\n- sending follow-ups after a meeting or no response\n- writing investor updates during a process\n- tailoring outreach based on fund thesis or partner fit\n\n## Core Rules\n\n1. Personalize every outbound message.\n2. Keep the ask low-friction.\n3. Use proof instead of adjectives.\n4. Stay concise.\n5. Never send copy that could go to any investor.\n\n## Voice Handling\n\nIf the user's voice matters, run `brand-voice` first and reuse its `VOICE PROFILE`.\nThis skill should keep the investor-specific structure and ask discipline, not recreate its own parallel voice system.\n\n## Hard Bans\n\nDelete and rewrite any of these:\n- \"I'd love to connect\"\n- \"excited to share\"\n- generic thesis praise without a real tie-in\n- vague founder adjectives\n- begging language\n- soft closing questions when a direct ask is clearer\n\n## Cold Email Structure\n\n1. subject line: short and specific\n2. opener: why this investor specifically\n3. pitch: what the company does, why now, and what proof matters\n4. ask: one concrete next step\n5. sign-off: name, role, and one credibility anchor if needed\n\n## Personalization Sources\n\nReference one or more of:\n- relevant portfolio companies\n- a public thesis, talk, post, or article\n- a mutual connection\n- a clear market or product fit with the investor's focus\n\nIf that context is missing, state that the draft still needs personalization instead of pretending it is finished.\n\n## Follow-Up Cadence\n\nDefault:\n- day 0: initial outbound\n- day 4 or 5: short follow-up with one new data point\n- day 10 to 12: final follow-up with a clean close\n\nDo not keep nudging after that unless the user wants a longer sequence.\n\n## Warm Intro Requests\n\nMake life easy for the connector:\n- explain why the intro is a fit\n- include a forwardable blurb\n- keep the forwardable blurb under 100 words\n\n## Post-Meeting Updates\n\nInclude:\n- the specific thing discussed\n- the answer or update promised\n- one new proof point if available\n- the next step\n\n## Quality Gate\n\nBefore delivering:\n- the message is genuinely personalized\n- the ask is explicit\n- the proof point is concrete\n- filler praise and softener language are gone\n- word count stays tight\n","# Investor Outreach\n\nWrite investor communication that is short, concrete, and easy to act on.\n\n## When to Activate\n\n- writing a cold email to an investor\n- drafting a warm intro request\n- sending follow-ups after a meeting or no response\n- writing investor updates during a process\n- tailoring outreach based on fund thesis or partner fit\n\n## Core Rules\n\n1. Personalize every outbound message.\n2. Keep the ask low-friction.\n3. Use proof instead of adjectives.\n4. Stay concise.\n5. Never send copy that could go to any investor.\n\n## Voice Handling\n\nIf the user's voice matters, run `brand-voice` first and reuse its `VOICE PROFILE`.\nThis skill should keep the investor-specific structure and ask discipline, not recreate its own parallel voice system.\n\n## Hard Bans\n\nDelete and rewrite any of these:\n- \"I'd love to connect\"\n- \"excited to share\"\n- generic thesis praise without a real tie-in\n- vague founder adjectives\n- begging language\n- soft closing questions when a direct ask is clearer\n\n## Cold Email Structure\n\n1. subject line: short and specific\n2. opener: why this investor specifically\n3. pitch: what the company does, why now, and what proof matters\n4. ask: one concrete next step\n5. sign-off: name, role, and one credibility anchor if needed\n\n## Personalization Sources\n\nReference one or more of:\n- relevant portfolio companies\n- a public thesis, talk, post, or article\n- a mutual connection\n- a clear market or product fit with the investor's focus\n\nIf that context is missing, state that the draft still needs personalization instead of pretending it is finished.\n\n## Follow-Up Cadence\n\nDefault:\n- day 0: initial outbound\n- day 4 or 5: short follow-up with one new data point\n- day 10 to 12: final follow-up with a clean close\n\nDo not keep nudging after that unless the user wants a longer sequence.\n\n## Warm Intro Requests\n\nMake life easy for the connector:\n- explain why the intro is a fit\n- include a forwardable blurb\n- keep the forwardable blurb under 100 words\n\n## Post-Meeting Updates\n\nInclude:\n- the specific thing discussed\n- the answer or update promised\n- one new proof point if available\n- the next step\n\n## Quality Gate\n\nBefore delivering:\n- the message is genuinely personalized\n- the ask is explicit\n- the proof point is concrete\n- filler praise and softener language are gone\n- word count stays tight\n",{"name":5,"metadata":42,"description":7},{"origin":43},"ECC","main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Finvestor-outreach",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill investor-outreach",{"tool":58,"command":59},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill investor-outreach",{"tool":61,"command":62},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill investor-outreach","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Finvestor-outreach\u002FSKILL.md",true,[],[67,75,83,90,97,104],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":74},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":82},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":82},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":82},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":82},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":82},"01M748721J3GKR2WS6K0QWFC35","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]