[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P0MQ9G2Z13PYTR9AFY8REH":3,"skill-same:01M6P0MQ9G2Z13PYTR9AFY8REH":68},{"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":23,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":14,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6P0MQ9G2Z13PYTR9AFY8REH","cold-email-writer",null,"Write personalized cold outreach emails to hiring managers and founders — specific, human, not a pitch deck","shreyasbhakta\u002FCareerReboot","shreyasbhakta","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F55823227?v=4","01M6P0DV5QY0C5FEMNYKBD4YFJ","Shreyas Bhakta","01M6P0DV9YG9JPTG0VVGG866PP",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Fcold-email-writer\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"email","cold email","email writer","writer","cold email writer","cold","managers","founders","pitch","pitch deck","outreach","emails","human","cold outreach","deck","write","Hiring","2026-11-10 10:12:30",false,"---\nname: cold-email-writer\ndescription: Write personalized cold outreach emails to hiring managers and founders — specific, human, not a pitch deck\n---\n\n# Cold Email Writer\n\n## When to Use This Skill\n\nUse this skill when the user wants to:\n- Write a cold outreach email to a hiring manager, founder, or recruiter\n- Reach out about a job opening they weren't referred to\n- Introduce themselves to a company they want to work at\n- Mentions: \"cold email\", \"reach out\", \"intro email\", \"outreach\", \"contact hiring manager\"\n\n## Core Principle\n\nCold emails fail because they sound like cover letters. The goal is to sound like a smart person who genuinely noticed something specific about the company — not a candidate broadcasting their credentials.\n\n**The email should feel like:** A colleague mentioning something interesting they read, not a sales pitch.\n\n## The Template Structure\n\n### Subject\n```\nQuick intro — [First Name Last Name]\n```\nSimple. No clickbait. No role title. Just a name.\n\n### Opening — The Hook (2-3 sentences)\nStart with what genuinely pulled the candidate in. Must be specific to this company — not a generic compliment.\n\n```\nI just came across [Company] and ended up spending more time on it than I expected.\n[One specific thing that caught their attention — a stat, a product decision, a market insight from the JD or website]\n```\n\n**What makes a good hook:**\n- A specific number or stat from the company's materials (\"only 5% of the market is online\")\n- A product decision that shows you understand the domain (\"you're building from scratch alongside underwriters, not just distribution\")\n- A technical insight from the JD (\"improving the data infrastructure for LLM usage, not just the model layer\")\n\n**What makes a bad hook:**\n- Generic: \"I love what you're building\"\n- Vague: \"Your mission resonates with me\"\n- Flattering: \"You're one of the most exciting companies in the space\"\n\n### Location Disclosure (if international)\nIf the candidate is in a different country from the company, disclose it early and casually:\n\n```\nBefore you read further, I should mention I'm based in [country]. But if we both\nfeel there's a strong fit, I'd be open to figuring things out.\n```\n\n### Experience Gap (if applicable)\nIf the role lists more years than the candidate has, acknowledge it briefly and redirect:\n\n```\nThe role mentions [X] years of experience — I'm at [Y], but the work I've\nshipped is production-facing and I'd rather you judge that directly.\n```\n\n### The Body — Who They Are (3-5 sentences)\nCurrent role → relevant past → one or two projects. Keep it contextual, not a list.\n\n```\nA bit about me: I currently work at [Company], [one line on what the company does],\nwhere I [what they actually do there — not a job title]. Before that I worked\nwith teams in [region], mostly around [relevant domain].\n\nOn the side I've been building [Project] ([link if applicable]) — [one line: what\nit is and one proof point like \"got to paying clients\" or \"20K downloads\"].\n```\n\n**Rules:**\n- Mention work as context, not as proof of greatness\n- No achievement listings (\"I increased X by Y%\") — let the project speak\n- If current company is remote with a European\u002Finternational team, say so explicitly\n- Keep project mentions to one or two max — the most relevant ones only\n\n### The Connection (1-2 sentences)\nBridge between their background and the specific role. Should feel like an observation, not a claim.\n\n```\nI think you're looking for [what the role actually wants] — that's the kind of\nwork I've been doing, and honestly I feel like I'd be a strong fit.\n```\n\nOr more specific:\n```\nMy stack maps naturally to yours — [specific tech overlap]. But more than the\nstack, it's the [domain\u002Fproblem] that I'm genuinely interested in.\n```\n\n### Portfolio Link\n```\nMore about me: [portfolio URL]\n```\n\nOne line. No elaboration.\n\n### Closing\nEnd with low-pressure, confident energy. Not desperate, not corporate.\n\n```\nI'm currently at [Company] and open to what's next. I think my experience lends\nnicely to what you're building — so I think we'd both get something out of a\nconversation.\n\n[First Name]\n[email]\n```\n\n**Avoid:**\n- \"I look forward to hearing from you\"\n- \"Please find attached my resume\"\n- \"I would love the opportunity to...\"\n- \"I am excited to potentially join...\"\n\n## Research Before Writing\n\nBefore writing the email, gather:\n1. **Company angle** — read their website, JD, or About page. Find one specific thing worth mentioning.\n2. **Recipient name** — LinkedIn, team page, or AngelList. \"Hi [Name]\" beats \"Hi Hiring Manager\" every time.\n3. **Relevant projects** — match the candidate's most relevant work to the role domain.\n4. **Stack overlap** — mention it only if there's a genuine match.\n\nIf the user provides a JD but no company website, ask for it or fetch it before writing.\n\n## Length Guidelines\n\n- **Ideal:** 200–300 words\n- **Maximum:** 400 words\n- **Minimum:** 150 words (don't strip out substance for brevity)\n\nLonger is fine if every sentence earns its place. Cut anything that could apply to any company.\n\n## Output Format\n\nAlways wrap the final email in a plain code block for clean copy-paste:\n\n```\nSubject: Quick intro — [Name]\n\nHi [Name],\n\n[Email body]\n\n[First Name]\n[email]\n```\n\n## Common Mistakes to Avoid\n\n**Too confident:**\n❌ \"I would be an exceptional addition to your team\"\n❌ \"My background uniquely positions me for this role\"\n✅ \"I feel like I'd be a strong fit\" — states a belief, doesn't claim certainty\n\n**Too humble:**\n❌ \"I know I may not have all the experience you're looking for, but...\"\n❌ \"I'm just reaching out on the off chance...\"\n✅ Acknowledge gaps directly and move on — don't apologize\n\n**Too long:**\n❌ Three paragraphs listing every achievement\n✅ One paragraph on background, one on the connection\n\n**Too generic:**\n❌ Opening with \"I am writing to express my interest in...\"\n✅ Opening with what specifically pulled them to this company\n\n**No research:**\n❌ \"I love your product and mission\"\n✅ \"The 5% stat — only 5% of a $25B market online — doesn't feel like a feature gap, it feels like an entire industry that hasn't digitised\"\n\n## Example Email\n\n```\nSubject: Quick intro — Sarah Chen\n\nHi Marcus,\n\nI just came across Meridian and spent more time on your site than I planned.\nWhat pulled me in was the framing around your data infrastructure — you're not\njust building an LLM layer on top of existing records, you're rethinking how\nclinical data flows through the system in the first place. That's a harder\nproblem and a more interesting one.\n\nI'm based in India, flagging that upfront. Happy to figure out the rest if\nthere's a real fit.\n\nI currently work at Lune, a London-based climate intelligence company, where I\nbuild event-driven data pipelines and agentic AI workflows for emissions\ncompliance — regulated, data-intensive systems where reliability isn't optional.\nI also built Memos, a RAG system from scratch: hybrid retrieval, reranking,\nChromaDB, FastAPI. And InframetAI, an SDK for LLM cost and latency\nobservability that came out of seeing what breaks when the data layer isn't\ndesigned around how models actually work.\n\nI think you're looking for engineers who've actually built AI systems end to\nend, not just wrapped APIs. That's the work I've been doing.\n\nMore about me: yourportfolio.com\u002Fabout\n\nI'm currently at Lune and open to what's next. I think my experience maps\nclosely to what you're building — so I think we'd both get something out of\na conversation.\n\nSarah\nsarah@email.com\n```\n","# Cold Email Writer\n\n## When to Use This Skill\n\nUse this skill when the user wants to:\n- Write a cold outreach email to a hiring manager, founder, or recruiter\n- Reach out about a job opening they weren't referred to\n- Introduce themselves to a company they want to work at\n- Mentions: \"cold email\", \"reach out\", \"intro email\", \"outreach\", \"contact hiring manager\"\n\n## Core Principle\n\nCold emails fail because they sound like cover letters. The goal is to sound like a smart person who genuinely noticed something specific about the company — not a candidate broadcasting their credentials.\n\n**The email should feel like:** A colleague mentioning something interesting they read, not a sales pitch.\n\n## The Template Structure\n\n### Subject\n```\nQuick intro — [First Name Last Name]\n```\nSimple. No clickbait. No role title. Just a name.\n\n### Opening — The Hook (2-3 sentences)\nStart with what genuinely pulled the candidate in. Must be specific to this company — not a generic compliment.\n\n```\nI just came across [Company] and ended up spending more time on it than I expected.\n[One specific thing that caught their attention — a stat, a product decision, a market insight from the JD or website]\n```\n\n**What makes a good hook:**\n- A specific number or stat from the company's materials (\"only 5% of the market is online\")\n- A product decision that shows you understand the domain (\"you're building from scratch alongside underwriters, not just distribution\")\n- A technical insight from the JD (\"improving the data infrastructure for LLM usage, not just the model layer\")\n\n**What makes a bad hook:**\n- Generic: \"I love what you're building\"\n- Vague: \"Your mission resonates with me\"\n- Flattering: \"You're one of the most exciting companies in the space\"\n\n### Location Disclosure (if international)\nIf the candidate is in a different country from the company, disclose it early and casually:\n\n```\nBefore you read further, I should mention I'm based in [country]. But if we both\nfeel there's a strong fit, I'd be open to figuring things out.\n```\n\n### Experience Gap (if applicable)\nIf the role lists more years than the candidate has, acknowledge it briefly and redirect:\n\n```\nThe role mentions [X] years of experience — I'm at [Y], but the work I've\nshipped is production-facing and I'd rather you judge that directly.\n```\n\n### The Body — Who They Are (3-5 sentences)\nCurrent role → relevant past → one or two projects. Keep it contextual, not a list.\n\n```\nA bit about me: I currently work at [Company], [one line on what the company does],\nwhere I [what they actually do there — not a job title]. Before that I worked\nwith teams in [region], mostly around [relevant domain].\n\nOn the side I've been building [Project] ([link if applicable]) — [one line: what\nit is and one proof point like \"got to paying clients\" or \"20K downloads\"].\n```\n\n**Rules:**\n- Mention work as context, not as proof of greatness\n- No achievement listings (\"I increased X by Y%\") — let the project speak\n- If current company is remote with a European\u002Finternational team, say so explicitly\n- Keep project mentions to one or two max — the most relevant ones only\n\n### The Connection (1-2 sentences)\nBridge between their background and the specific role. Should feel like an observation, not a claim.\n\n```\nI think you're looking for [what the role actually wants] — that's the kind of\nwork I've been doing, and honestly I feel like I'd be a strong fit.\n```\n\nOr more specific:\n```\nMy stack maps naturally to yours — [specific tech overlap]. But more than the\nstack, it's the [domain\u002Fproblem] that I'm genuinely interested in.\n```\n\n### Portfolio Link\n```\nMore about me: [portfolio URL]\n```\n\nOne line. No elaboration.\n\n### Closing\nEnd with low-pressure, confident energy. Not desperate, not corporate.\n\n```\nI'm currently at [Company] and open to what's next. I think my experience lends\nnicely to what you're building — so I think we'd both get something out of a\nconversation.\n\n[First Name]\n[email]\n```\n\n**Avoid:**\n- \"I look forward to hearing from you\"\n- \"Please find attached my resume\"\n- \"I would love the opportunity to...\"\n- \"I am excited to potentially join...\"\n\n## Research Before Writing\n\nBefore writing the email, gather:\n1. **Company angle** — read their website, JD, or About page. Find one specific thing worth mentioning.\n2. **Recipient name** — LinkedIn, team page, or AngelList. \"Hi [Name]\" beats \"Hi Hiring Manager\" every time.\n3. **Relevant projects** — match the candidate's most relevant work to the role domain.\n4. **Stack overlap** — mention it only if there's a genuine match.\n\nIf the user provides a JD but no company website, ask for it or fetch it before writing.\n\n## Length Guidelines\n\n- **Ideal:** 200–300 words\n- **Maximum:** 400 words\n- **Minimum:** 150 words (don't strip out substance for brevity)\n\nLonger is fine if every sentence earns its place. Cut anything that could apply to any company.\n\n## Output Format\n\nAlways wrap the final email in a plain code block for clean copy-paste:\n\n```\nSubject: Quick intro — [Name]\n\nHi [Name],\n\n[Email body]\n\n[First Name]\n[email]\n```\n\n## Common Mistakes to Avoid\n\n**Too confident:**\n❌ \"I would be an exceptional addition to your team\"\n❌ \"My background uniquely positions me for this role\"\n✅ \"I feel like I'd be a strong fit\" — states a belief, doesn't claim certainty\n\n**Too humble:**\n❌ \"I know I may not have all the experience you're looking for, but...\"\n❌ \"I'm just reaching out on the off chance...\"\n✅ Acknowledge gaps directly and move on — don't apologize\n\n**Too long:**\n❌ Three paragraphs listing every achievement\n✅ One paragraph on background, one on the connection\n\n**Too generic:**\n❌ Opening with \"I am writing to express my interest in...\"\n✅ Opening with what specifically pulled them to this company\n\n**No research:**\n❌ \"I love your product and mission\"\n✅ \"The 5% stat — only 5% of a $25B market online — doesn't feel like a feature gap, it feels like an entire industry that hasn't digitised\"\n\n## Example Email\n\n```\nSubject: Quick intro — Sarah Chen\n\nHi Marcus,\n\nI just came across Meridian and spent more time on your site than I planned.\nWhat pulled me in was the framing around your data infrastructure — you're not\njust building an LLM layer on top of existing records, you're rethinking how\nclinical data flows through the system in the first place. That's a harder\nproblem and a more interesting one.\n\nI'm based in India, flagging that upfront. Happy to figure out the rest if\nthere's a real fit.\n\nI currently work at Lune, a London-based climate intelligence company, where I\nbuild event-driven data pipelines and agentic AI workflows for emissions\ncompliance — regulated, data-intensive systems where reliability isn't optional.\nI also built Memos, a RAG system from scratch: hybrid retrieval, reranking,\nChromaDB, FastAPI. And InframetAI, an SDK for LLM cost and latency\nobservability that came out of seeing what breaks when the data layer isn't\ndesigned around how models actually work.\n\nI think you're looking for engineers who've actually built AI systems end to\nend, not just wrapped APIs. That's the work I've been doing.\n\nMore about me: yourportfolio.com\u002Fabout\n\nI'm currently at Lune and open to what's next. I think my experience maps\nclosely to what you're building — so I think we'd both get something out of\na conversation.\n\nSarah\nsarah@email.com\n```\n",{"name":5,"description":7},"main","466b9f58403b6b473023097f5b9f3f094ebeb493","skills\u002Fresume-skills\u002Fskills\u002Fcold-email-writer","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta","shreyasbhakta.dev","Software Engineer | Backend & Distributed Systems | Java, Spring Boot, Kafka, Python | Agentic AI, LangGraph, RAG | Ex-Vymo, Ex-SIXT | Cybersecurity Enthusiast","2026-10-17 04:01:42",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add shreyasbhakta\u002FCareerReboot --skill cold-email-writer",{"tool":60,"command":61},"bunx","bunx skills add shreyasbhakta\u002FCareerReboot --skill cold-email-writer",{"tool":63,"command":64},"pnpm","pnpm dlx skills add shreyasbhakta\u002FCareerReboot --skill cold-email-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Fcold-email-writer\u002FSKILL.md",true,[],[69,94,114,129,139,150],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":80,"publishedAt":41},"01M6P0SGCMXDZ5DH19S9RS4PZZ","tech-resume-optimizer","Optimize resumes for software engineering, PM, and technical roles","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Ftech-resume-optimizer\u002FSKILL.md",[75],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[81,82,83,84,85,86,87,88,89,90,91,92,93],"tech resume optimizer","resume","resume optimizer","optimizer","tech","software engineering","for","engineering","technical","optimize","pm","roles","software",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":103,"publishedAt":41},"01M6P0SC37HWQ8CTWA37SVPAA3","salary-negotiation-prep","Research market rates, build negotiation strategy, and create counter-offer scripts","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Fsalary-negotiation-prep\u002FSKILL.md",[100],{"categoryNo":101,"categoryName":102,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[104,105,106,107,108,109,110,111,112,113],"negotiation prep","prep","negotiation","salary negotiation prep","build","scripts","Market","research","create","strategy",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":121,"publishedAt":41},"01M6P0RSXGGR789TX42ZXNR09N","resume-version-manager","Track different resume versions, maintain master resume, manage tailored versions","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Fresume-version-manager\u002FSKILL.md",[120],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},[122,82,123,124,125,126,127,128],"manager","version","resume version manager","master","manage","maintain","track",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":136,"publishedAt":41},"01M6P0RK6FX16FYCC01T2HA2MA","resume-tailor","Customize resume for specific job postings while maintaining truthfulness","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Fresume-tailor\u002FSKILL.md",[135],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},[82,137,87,138],"resume tailor","customize",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":146,"publishedAt":41},"01M6P0R57S7ASRV6VAYQ4K2J9Y","resume-section-builder","Create targeted resume sections optimized for different experience levels and roles","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Fresume-section-builder\u002FSKILL.md",[145],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},[147,148,82,149,112,92,87],"section","builder","resume section builder",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":157,"publishedAt":41},"01M6P0R0TVRRDSTTM047HWXNCD","resume-quantifier","Find opportunities to add metrics and estimate numbers when exact data unavailable","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Fresume-quantifier\u002FSKILL.md",[156],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},[82,158,159,160,161,162,163],"resume quantifier","metrics","data","find","add","estimate"]