Expand to Career Arsenal: 8 AI-powered career skills collection
- Restructured repo from single skill to skills collection - Added 7 new skills: Resume Architect, Cover Letter Craft, Interview Commander, Salary Negotiator, Career GPS, LinkedIn Optimizer, Job Switch Advisor - Rewrote README as collection hub with pipeline diagram, integration map, and usage-by-stage guides Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
208
skills/cover-letter-craft.md
Normal file
208
skills/cover-letter-craft.md
Normal file
@@ -0,0 +1,208 @@
|
||||
# Cover Letter Craft
|
||||
**Generate persuasive, role-specific cover letters that get read — not recycled.**
|
||||
Most cover letters are generic fluff. This skill writes letters that prove you did your homework.
|
||||
|
||||
## Philosophy
|
||||
A cover letter has one purpose: make the reader WANT to look at your resume.
|
||||
|
||||
It's not about you. It's about **what you can do for them**, proven by what you've already done.
|
||||
|
||||
The formula:
|
||||
1. **Hook** — Show you know who they are and what they need
|
||||
2. **Proof** — Demonstrate you've solved their exact problem before
|
||||
3. **Value** — Paint a picture of what you'll deliver in the first 90 days
|
||||
4. **Close** — Make the next step effortless for them
|
||||
|
||||
## Input Required
|
||||
- Target job posting (URL or text)
|
||||
- Your resume or career summary
|
||||
- Company research notes (from jobhunter-master Phase 1)
|
||||
- Hiring manager name (if known)
|
||||
|
||||
## Workflow
|
||||
|
||||
### Phase 1: Research Synthesis
|
||||
```
|
||||
Gather company intelligence:
|
||||
- Recent product launches or feature updates
|
||||
- Company mission/values language
|
||||
- Tech blog posts or engineering challenges
|
||||
- Recent funding or growth news
|
||||
- Glassdoor culture themes
|
||||
- Hiring manager's background (LinkedIn)
|
||||
```
|
||||
|
||||
**Output:** 3-5 specific hooks unique to this company.
|
||||
|
||||
### Phase 2: Pain Point Mapping
|
||||
```
|
||||
From job post, identify:
|
||||
- What problem does this role solve?
|
||||
- Why is this position open? (growth, backfill, new initiative)
|
||||
- What's the urgency signal?
|
||||
- What would success look like in 6 months?
|
||||
```
|
||||
|
||||
**Output:** The problem statement this letter addresses.
|
||||
|
||||
### Phase 3: Story Selection
|
||||
```
|
||||
From your experience, pick 1-2 stories that:
|
||||
- Directly solve their stated problem
|
||||
- Use the same technologies they mentioned
|
||||
- Show measurable impact (numbers, percentages)
|
||||
- Demonstrate cultural fit signals
|
||||
```
|
||||
|
||||
### Phase 4: Letter Assembly
|
||||
|
||||
**Paragraph 1 — The Hook (2-3 sentences)**
|
||||
```
|
||||
Opening options (pick one):
|
||||
|
||||
Option A (Product-led):
|
||||
"I've been following [Company]'s work on [specific product/feature], and I was excited to see the [Role] position open up. [Specific observation about their product/challenge]."
|
||||
|
||||
Option B (Mission-led):
|
||||
"[Company]'s mission to [specific mission language from their site] resonates deeply with me. [Brief personal connection to the mission]. When I saw the [Role] position, I knew I had to reach out."
|
||||
|
||||
Option C (News-led):
|
||||
"Congratulations on [recent funding/product launch/news]. [Specific thought showing you understand the implications]. This is exactly why the [Role] position caught my eye."
|
||||
|
||||
Option D (Referral/Warm):
|
||||
"[Mutual connection] mentioned [Company] is looking for a [Role]. After looking at [specific thing], I'm convinced I can contribute from day one."
|
||||
```
|
||||
|
||||
**Paragraph 2 — The Proof (3-4 sentences)**
|
||||
```
|
||||
Template:
|
||||
"At [Previous Company], I [specific action] that [specific result with metric]. I achieved this by [method/technology relevant to target role]. This experience is directly applicable to [Company]'s need for [specific need from job post]."
|
||||
|
||||
Rules:
|
||||
- One concrete example, not a laundry list
|
||||
- Include at least one number
|
||||
- Mirror their language and tech stack
|
||||
- Connect YOUR past to THEIR future
|
||||
```
|
||||
|
||||
**Paragraph 3 — The Value (2-3 sentences)**
|
||||
```
|
||||
Template:
|
||||
"In my first 90 days at [Company], I would [specific, realistic contribution]. I'm particularly excited about [specific challenge or opportunity] because [why you're uniquely qualified]."
|
||||
|
||||
Rules:
|
||||
- Be specific, not aspirational
|
||||
- Show you understand their current stage
|
||||
- Reference something they're actively working on
|
||||
```
|
||||
|
||||
**Paragraph 4 — The Close (2 sentences)**
|
||||
```
|
||||
Template:
|
||||
"I'd love to discuss how my experience with [relevant skill] can help [Company] [specific goal]. Are you available for a 15-minute call [specific time suggestion]?"
|
||||
|
||||
Rules:
|
||||
- Make it easy to say yes
|
||||
- Suggest a specific next step
|
||||
- Don't beg or grovel
|
||||
```
|
||||
|
||||
### Phase 5: Tone Calibration
|
||||
```
|
||||
Match tone to company type:
|
||||
|
||||
Startup (Seed-Series B):
|
||||
- Casual but competent
|
||||
- Use "I" not "we" for achievements
|
||||
- Show scrappiness and ownership
|
||||
- Mention specific product features
|
||||
|
||||
Scale-up (Series C+):
|
||||
- Balance scrappiness with scale thinking
|
||||
- Reference growth metrics
|
||||
- Show you can build for 10x current size
|
||||
- Data-driven language
|
||||
|
||||
Enterprise:
|
||||
- Formal and structured
|
||||
- Emphasize process and reliability
|
||||
- Reference compliance, security, governance
|
||||
- Team-oriented achievements
|
||||
|
||||
Agency/Consultancy:
|
||||
- Client-facing language
|
||||
- Emphasize adaptability
|
||||
- Reference diverse project experience
|
||||
- Show business impact for clients
|
||||
```
|
||||
|
||||
## Templates
|
||||
|
||||
### Software Engineer
|
||||
```
|
||||
Hi [Name],
|
||||
|
||||
I've been using [Company]'s [product] for [context], and I'm impressed by [specific thing]. When I saw the [Role] position, it felt like the perfect intersection of my skills and your mission.
|
||||
|
||||
At [Current Company], I [built/shipped/led] [specific thing] that [metric — reduced latency 40%, scaled to 1M users, etc.]. I did this using [tech from their stack], which I noticed is central to your engineering approach. I'm particularly drawn to [Company] because [specific challenge they're facing that matches your expertise].
|
||||
|
||||
In my first quarter, I'd focus on [specific, realistic contribution]. I've been thinking about [relevant technical topic] and would love to bring that perspective to your team.
|
||||
|
||||
Would you have 15 minutes this week to chat? I'm available [specific times].
|
||||
|
||||
Best,
|
||||
[Name]
|
||||
[LinkedIn] | [GitHub]
|
||||
```
|
||||
|
||||
### Career Changer
|
||||
```
|
||||
Hi [Name],
|
||||
|
||||
[Hook showing genuine passion for the new field]. While my background is in [previous field], I've spent the last [timeframe] [building/shipping/learning] in [new field].
|
||||
|
||||
[Specific project or achievement in new field with metric]. This taught me that [transferable skill] translates directly — in fact, my experience with [previous domain] gives me a unique angle on [their challenge].
|
||||
|
||||
I know transitioning fields requires proving yourself twice. That's why I've [concrete step: built a portfolio project, earned certification, contributed to open source]. I'm ready to hit the ground running.
|
||||
|
||||
I'd love to discuss how my unconventional background can be an asset to [Company]. Free for a quick call anytime this week.
|
||||
|
||||
Best,
|
||||
[Name]
|
||||
```
|
||||
|
||||
### Senior/Leadership
|
||||
```
|
||||
Hi [Name],
|
||||
|
||||
After [X] years building [domain] teams and systems, I'm drawn to [Company] because [specific strategic reason — not generic].
|
||||
|
||||
Most recently at [Company], I [leadership achievement with org-level metric]. The key insight: [strategic lesson applicable to their challenge]. I see parallels with what [Target Company] is tackling in [area].
|
||||
|
||||
I build teams that [specific culture/outcome]. My approach: [1-2 sentence leadership philosophy relevant to their stage]. I believe this aligns with [something from their values/culture page].
|
||||
|
||||
I'd appreciate the chance to discuss the [Role] and how I can contribute to [Company]'s next chapter. Would [specific time] work for a conversation?
|
||||
|
||||
Best,
|
||||
[Name]
|
||||
[LinkedIn]
|
||||
```
|
||||
|
||||
## Anti-Patterns (Never Do These)
|
||||
- "I am writing to apply for..." (wastes the first sentence)
|
||||
- "I believe I would be a great fit because..." (show, don't tell)
|
||||
- Repeating your resume in paragraph form
|
||||
- Generic compliments ("great company", "innovative team")
|
||||
- More than 4 paragraphs or 300 words
|
||||
- "Please find attached my resume" (they know)
|
||||
- BCC-ing multiple companies
|
||||
|
||||
## Integration with Other Skills
|
||||
- **resume-architect**: Shares job fingerprint for keyword consistency
|
||||
- **jobhunter-master**: Receives company research and hiring manager data
|
||||
- **nano-pdf**: Final formatted output
|
||||
- **gog**: Direct email sending
|
||||
|
||||
## Files
|
||||
- `memory/cover-letters/[company]-[role].md` — Per-application letters
|
||||
- `memory/company-research/[company].md` — Research notes feeding into letters
|
||||
Reference in New Issue
Block a user