[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6G23E2Q99WBTXDF4E7MAPHT":3,"skill-same:01M6G23E2Q99WBTXDF4E7MAPHT":70},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M6G23E2Q99WBTXDF4E7MAPHT","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.","oabdelmaksoud\u002FAgention","oabdelmaksoud","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F50699149?v=4","01M6D5CVVN778ZCDP1WHS816SP","Omar Abdelmaksoud","01M6D8A4TE76V3DCSH3D94VG1V",2,"MIT","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002F.agents\u002Fskills\u002Finvestor-outreach\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"investor outreach","outreach","update","messaging","intro","user","use","draft","fundraising","emails","cold","communications","strategic","investors","concise","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.\norigin: ECC\n---\n\n# Investor Outreach\n\nWrite investor communication that is short, personalized, 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, not adjectives.\n4. Stay concise.\n5. Never send generic copy that could go to any investor.\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, what proof matters\n4. ask: one concrete next step\n5. sign-off: name, role, 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, ask for it or state that the draft is a template awaiting personalization.\n\n## Follow-Up Cadence\n\nDefault:\n- day 0: initial outbound\n- day 4-5: short follow-up with one new data point\n- day 10-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- message is personalized\n- the ask is explicit\n- there is no fluff or begging language\n- the proof point is concrete\n- word count stays tight\n","# Investor Outreach\n\nWrite investor communication that is short, personalized, 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, not adjectives.\n4. Stay concise.\n5. Never send generic copy that could go to any investor.\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, what proof matters\n4. ask: one concrete next step\n5. sign-off: name, role, 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, ask for it or state that the draft is a template awaiting personalization.\n\n## Follow-Up Cadence\n\nDefault:\n- day 0: initial outbound\n- day 4-5: short follow-up with one new data point\n- day 10-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- message is personalized\n- the ask is explicit\n- there is no fluff or begging language\n- the proof point is concrete\n- word count stays tight\n",{"name":5,"origin":40,"description":7},"ECC","main","a318f48de3c5718e8ea2e9f6fae7790e8a759e85","upstream-sync\u002Fwork\u002Fecc\u002F.agents\u002Fskills\u002Finvestor-outreach",0,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fo-abdelmaksoud\u002F","Full-Stack Engineer | AI Systems Architect | Building autonomous multi-agent systems","2026-03-08 21:23:03",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add oabdelmaksoud\u002FAgention --skill investor-outreach",{"tool":56,"command":57},"bunx","bunx skills add oabdelmaksoud\u002FAgention --skill investor-outreach",{"tool":59,"command":60},"pnpm","pnpm dlx skills add oabdelmaksoud\u002FAgention --skill investor-outreach","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002F.agents\u002Fskills\u002Finvestor-outreach\u002FSKILL.md",true,[64],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"agents\u002Fopenai.yaml","REFERENCE","参考文档",300,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002F.agents\u002Fskills\u002Finvestor-outreach\u002Fagents\u002Fopenai.yaml",[71,95,109,141,167,187],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":82,"publishedAt":35},"01M6G2QFCBNBYAJF2KTK85G9A6","visa-doc-translate","Translate visa application documents (images) to English and create a bilingual PDF with original and translation","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fvisa-doc-translate\u002FSKILL.md",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",[83,84,85,86,87,88,89,90,91,92,93,94],"translate","doc","visa doc translate","bilingual","with","english","application","PDF","translation","documents","create","images",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":35},"01M6G2QB09TSK6BY4ME5X20EVQ","verification-loop","A comprehensive verification system for Claude Code sessions.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[102,103,104,105,106,107,108],"verification","loop","verification loop","sessions","code","claude code sessions","system",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":126,"publishedAt":35},"01M6G2Q6V2F7G03VAAF27FXPJR","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[115,118,121],{"categoryNo":116,"categoryName":117,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":119,"categoryName":120,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":122,"categoryName":123,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[127,128,129,25,130,131,132,133,134,106,135,136,137,138,87,139,140],"workflow","tdd","tdd workflow","unit","coverage","refactoring","e2e","integration","development","e2e tests","tests","driven","test","writing",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":35},"01M6G2Q359YJRWAR2PFCEQAXF3","swiftui-patterns","SwiftUI architecture patterns, state management with @Observable, view composition, navigation, performance optimization, and modern iOS\u002FmacOS UI best practices.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fswiftui-patterns\u002FSKILL.md",[],[148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,87],"patterns","swiftui","swiftui patterns","architecture","macos","performance","state management","best practices","state","ui","Optimization","ios","architecture patterns","Composition","performance optimization","view","management","swiftui architecture","navigation",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":174,"publishedAt":35},"01M6G2PY8B2FWZTWPZ84H83Y7C","swift-protocol-di-testing","Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using focused protocols and Swift Testing.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fswift-protocol-di-testing\u002FSKILL.md",[173],{"categoryNo":116,"categoryName":117,"taxonomyType":80,"taxonomyTypeDesc":81},[175,176,177,178,106,179,180,181,182,108,183,184,185,186],"swift protocol di testing","protocol","swift","testing","protocols","file","network","injection","dependency","swift testing","dependency injection","mock",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":193,"publishedAt":35},"01M6G2PSCN2GXV9FFZDRRRWVB6","swift-concurrency-6-2","Swift 6.2 Approachable Concurrency — single-threaded by default, @concurrent for explicit background offloading, isolated conformances for main actor types.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fswift-concurrency-6-2\u002FSKILL.md",[],[194,195,196,177,197,41,198],"concurrency","swift concurrency","swift concurrency 6 2","default","types"]