[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73DBWVAVBQDGSXCC8JPR64G":3,"skill-same:01M73DBWVAVBQDGSXCC8JPR64G":49},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M73DBWVAVBQDGSXCC8JPR64G","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.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Finvestor-outreach\u002FSKILL.md",[],[],"2026-11-11 15:11:14",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, 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,"origin":24,"description":7},"ECC","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Finvestor-outreach",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill investor-outreach",{"tool":41,"command":42},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill investor-outreach",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill investor-outreach","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Finvestor-outreach\u002FSKILL.md",true,[],[50,58,65,73,81,89],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":54,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":69,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]