[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE4ESJP0KH7GK1KMYAYPHG":3,"skill-same:01M6AE4ESJP0KH7GK1KMYAYPHG":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":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M6AE4ESJP0KH7GK1KMYAYPHG","job-description-analyzer",null,"Analyze job postings, calculate match scores, identify gaps, and create an application strategy. Use when the user shares a job description or asks to evaluate fit, match score, or gaps against a posting.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Fjob-description-analyzer\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"job description analyzer","job description","analyzer","create","analyze","calculate","strategy","user","use","application","posting","fit","match","evaluate","gaps","when","2026-11-10 10:12:30",false,"---\nname: job-description-analyzer\ndescription: Analyze job postings, calculate match scores, identify gaps, and create an application strategy. Use when the user shares a job description or asks to evaluate fit, match score, or gaps against a posting.\n---\n\n# Job Description Analyzer\n\n## When to Use This Skill\n\nUse this skill when the user:\n- Wants to analyze a job posting\n- Asks \"should I apply to this job?\"\n- Wants to know their match percentage for a role\n- Needs help understanding job requirements\n- Wants to tailor their resume for a specific position\n- Mentions: \"analyze this job\", \"am I qualified\", \"match score\", \"should I apply\"\n\nUse this BEFORE resume tailoring to ensure effort is worth it.\n\n## Core Capabilities\n\n- Extract and categorize job requirements (must-have vs nice-to-have)\n- Calculate match score between user's experience and job requirements\n- Identify skill gaps and strengths\n- Detect red flags in job postings\n- Prioritize which experiences to highlight\n- Generate resume tailoring strategy\n- Create cover letter talking points\n- Assess company culture fit indicators\n\n## The Strategic Problem\n\nMost job seekers waste time on:\n- Jobs they're under-qualified for (\u003C60% match)\n- Jobs they're over-qualified for (flight risk)\n- Jobs with red flags (high turnover, toxic culture)\n- Applying to 50+ jobs blindly hoping something sticks\n\nBetter approach:\n- Apply to 10-15 jobs strategically\n- Target 70-90% match jobs\n- Customize deeply for each\n- Higher response rate, less burnout\n\n## Analysis Process\n\n### Step 1: Extract Requirements\n\nBreak job description into categories:\n\n**Required (Must-Have)**\n- Education requirements\n- Years of experience\n- Specific technical skills\n- Certifications\u002Flicenses\n- Industry experience\n\n**Preferred (Nice-to-Have)**\n- \"Bonus\" skills\n- Advanced certifications\n- Domain expertise\n- Specific tool experience\n\n**Soft Skills\u002FCulture**\n- Communication style\n- Work environment\n- Team structure\n- Company values\n\n### Step 2: Keyword Extraction\n\nIdentify three types:\n\n**Hard Skills** (Technical abilities)\n- Tools: Salesforce, Python, AWS, Excel\n- Methodologies: Agile, Six Sigma, SDLC\n- Certifications: PMP, CPA, AWS Certified\n\n**Soft Skills** (Interpersonal)\n- Leadership, collaboration, communication\n- Problem-solving, critical thinking\n- Adaptability, initiative\n\n**Industry\u002FDomain Knowledge**\n- B2B SaaS, healthcare, fintech\n- Enterprise vs SMB\n- Regulatory knowledge (HIPAA, SOX, GDPR)\n\n### Step 3: Calculate Match Score\n\n```\nMATCH CALCULATION:\n\nRequired Skills:\n- User has 8 out of 10 required = 80%\n\nPreferred Skills:\n- User has 3 out of 5 preferred = 60%\n\nOverall Match:\n- Weight required 70%, preferred 30%\n- (80% × 0.7) + (60% × 0.3) = 74%\n\nINTERPRETATION:\n90-100% = Overqualified (may be flight risk)\n75-89% = Excellent fit (apply immediately)\n60-74% = Good fit (apply with strong cover letter)\n50-59% = Stretch role (apply if passionate)\n\u003C50% = Under-qualified (skip unless dream job)\n```\n\n### Step 4: Gap Analysis\n\nFor each missing requirement:\n- **Critical gap**: Deal-breaker (don't apply)\n- **Major gap**: Significant but addressable (mention in cover letter)\n- **Minor gap**: Easy to learn (downplay or emphasize related skills)\n\n### Step 5: Red Flag Detection\n\nScan for warning signs:\n\n**Workload Red Flags:**\n- \"Wear many hats\"\n- \"Fast-paced environment\"\n- \"Hit the ground running\"\n- \"Self-starter in ambiguous situations\"\n\n**Culture Red Flags:**\n- \"Rockstar\u002FNinja\u002FGuru\"\n- \"We work hard, play hard\"\n- \"Unlimited vacation\"\n- \"Like a family\"\n\n**Compensation Red Flags:**\n- \"Competitive salary\" (won't tell you range)\n- \"Equity-heavy\" (low cash compensation)\n- \"Commission-based\" (no base salary)\n- \"DOE\" with no range\n\n## Match Score Output Format\n\n```markdown\n# JOB ANALYSIS REPORT\n\n**Position:** Senior Product Manager\n**Company:** TechCorp Inc.\n**Location:** San Francisco, CA (Hybrid)\n**Salary Range:** $140K-$180K + equity\n\n═══════════════════════════════════════════\n\n## OVERALL MATCH SCORE: 78% ✅\n\n**Recommendation:** STRONG FIT - Apply within 48 hours\n\n**Application Priority:** HIGH\n**Estimated Competition:** Medium (Posted 2 days ago)\n**Time to Tailor Resume:** 30-45 minutes\n\n═══════════════════════════════════════════\n\n## REQUIREMENTS BREAKDOWN\n\n### Required Skills - 8\u002F10 ✅\n\n✅ 5+ years product management (You have: 6 years)\n✅ B2B SaaS experience (You have: 4 years)\n✅ Agile\u002FScrum (You have: 5 years)\n✅ Cross-functional leadership (You have: Strong experience)\n✅ Data-driven decision making (You have: 3 years analytics)\n✅ API products (You have: 2 years)\n✅ Roadmap planning (You have: Extensive)\n✅ User research (You have: 2 years)\n❌ SQL\u002Fdata analysis (You have: Basic Excel only) ⚠️\n❌ Mobile product experience (You don't have) ⚠️\n\n### Preferred Skills - 4\u002F6 ✅\n\n✅ MBA or equivalent (You have: MBA from UC Berkeley)\n✅ Developer tools experience (You have: 2 years)\n✅ Payment systems (You have: 1 year)\n✅ International markets (You have: Worked with EU teams)\n❌ E-commerce background (You don't have)\n❌ Machine learning products (You don't have)\n\n### Soft Skills - 5\u002F5 ✅\n\n✅ Stakeholder management (Strong mentions in your resume)\n✅ Communication (You present regularly)\n✅ Strategic thinking (MBA + senior experience)\n✅ Influence without authority (You've done this)\n✅ Customer empathy (User research experience)\n\n═══════════════════════════════════════════\n\n## STRENGTHS TO EMPHASIZE\n\n**Your Top 3 Selling Points:**\n\n1. **B2B SaaS PM Experience**\n   - 4 years in SaaS, exactly what they want\n   - Lead with this in resume summary\n\n2. **API Product Background**\n   - Your developer tools experience is highly relevant\n   - This differentiates you from other candidates\n\n3. **Data-Driven Approach**\n   - Your analytics background addresses their need\n   - Emphasize metrics and data in every bullet\n\n═══════════════════════════════════════════\n\n## GAPS TO ADDRESS\n\n**Critical Gaps:** None ✅\n\n**Major Gaps:**\n⚠️ **SQL\u002FData Analysis**\n- They mention this 5x in job description\n- They want PM who can query data independently\n\n**Strategy:**\n- Don't avoid this gap\n- Address in cover letter: \"While my primary analytics work has been in Excel and BI tools, I'm actively learning SQL through DataCamp and can currently write basic queries\"\n- Emphasize your data-driven mindset and collaboration with data team\n\n**Minor Gaps:**\n- Mobile product experience (mentioned 2x)\n- Not a dealbreaker - they want \"any product,\" mobile just a plus\n\n**Strategy:**\n- Don't mention this gap\n- If asked in interview, pivot to \"transferable product skills\"\n\n═══════════════════════════════════════════\n\n## RESUME CUSTOMIZATION STRATEGY\n\n### Priority 1: Lead with Most Relevant Experience\n\n**Current Resume Order:**\n1. Company ABC - General PM work\n2. Company XYZ - Your developer tools role\n3. Company 123 - Early career\n\n**Recommended Order:**\n1. Company XYZ - Developer tools role (MOST RELEVANT)\n2. Company ABC - B2B SaaS work\n3. Company 123 - Only if space allows\n\n### Priority 2: Keyword Integration\n\n**Add These Exact Phrases:**\n- \"SQL and data analysis\" (mentioned 5x in JD)\n- \"API product management\" (mentioned 4x)\n- \"Developer-focused products\" (mentioned 3x)\n- \"Stakeholder alignment\" (mentioned 3x)\n\n**Where to Add:**\n- Professional Summary: Mention \"API products\" and \"data-driven\"\n- Skills Section: Add \"SQL (basic), Data Analysis, API Design\"\n- Experience: Weave into existing bullets\n\n### Priority 3: Quantify Everything\n\nThey mention \"metrics\" and \"KPIs\" 7 times total.\n\n**Enhance These Bullets:**\n\nCurrent: \"Led product roadmap\"\nBetter: \"Defined product roadmap based on analysis of 50+ customer interviews and usage data from 100K+ users\"\n\nCurrent: \"Launched new features\"\nBetter: \"Launched 8 features in 12 months, increasing user engagement by 35% and reducing churn by 20%\"\n\n═══════════════════════════════════════════\n\n## COVER LETTER TALKING POINTS\n\n### Opening Hook (Choose One):\n\n**Option 1 - Specific Company Knowledge:**\n\"I noticed TechCorp recently launched your API marketplace - I've spent the last 2 years as PM for a developer tools platform, and I'm excited about the opportunity to bring that experience to your growing API ecosystem.\"\n\n**Option 2 - Mutual Connection:**\n\"[Name] on your product team mentioned you're looking for a PM to lead the API product line - my 2 years in developer tools and B2B SaaS background would be a strong fit.\"\n\n**Option 3 - Problem-Solver:**\n\"Your JD mentions challenges in stakeholder alignment across technical teams - I've navigated this exact challenge at my current role, aligning engineering, design, and sales teams across 6 concurrent product initiatives.\"\n\n### Body - Address the Match:\n- \"Your requirement for B2B SaaS experience: I have 4 years with...\" \n- \"Your focus on data-driven decisions: In my current role, I...\"\n- \"Your need for API product expertise: At [Company], I...\"\n\n### Addressing SQL Gap (Optional):\n\"While my data analysis has primarily been in Excel and Tableau, I'm expanding my SQL skills and can currently write basic queries. More importantly, I've built strong partnerships with data teams and consistently use data to inform product decisions.\"\n\n═══════════════════════════════════════════\n\n## RED FLAGS ANALYSIS\n\n### Potential Concerns: ⚠️ MINOR\n\n**Flag 1:** \"Fast-paced environment\"\n- Appears 2x in description\n- Interpretation: Likely startup or high-growth\n- May mean: Long hours, ambiguity, rapid changes\n\n**Flag 2:** Salary range is wide ($140K-$180K)\n- 29% spread\n- May indicate: Experience range is flexible, or negotiation room\n\n### Positive Signals: ✅\n\n**Signal 1:** Detailed job description\n- Shows company knows what they want\n- Well-organized role\n\n**Signal 2:** Mentions specific tools (JIRA, Amplitude)\n- Shows operational maturity\n\n**Signal 3:** Hybrid flexibility mentioned\n- Modern workplace practices\n\n### Company Research Needed:\n\nBefore applying, check:\n- Glassdoor reviews (look for patterns in 1-2 star reviews)\n- Recent funding\u002Fnews (layoffs? growth?)\n- LinkedIn: Check how long people stay (high turnover?)\n- Levels.fyi: Verify salary range is accurate\n\n═══════════════════════════════════════════\n\n## APPLICATION TIMELINE\n\n**✅ Day 1 (Today):**\n- Customize resume (30-45 minutes)\n- Write cover letter (30 minutes)\n\n**✅ Day 1-2:**\n- Submit application\n- Connect with 2-3 current employees on LinkedIn\n- Research company more deeply\n\n**✅ Week 1:**\n- Follow up if no response after 7 days\n\n**? Expected Response Time:** 1-2 weeks\n\n**? Interview Process (from job posting):**\n1. Recruiter screen (30 min)\n2. Hiring manager (1 hour)\n3. Product case study (take-home)\n4. Team interviews (3-4 hours)\n5. Executive interview (1 hour)\n\n═══════════════════════════════════════════\n\n## DECISION FACTORS\n\n### Reasons to Apply ✅\n\n1. Strong match (78%) - You meet most requirements\n2. Role aligns with career goals\n3. Salary range is appropriate for your experience\n4. Company stage fits your preferences\n5. You have unique relevant experience (developer tools)\n\n### Reasons to Hesitate ⚠️\n\n1. SQL gap is real - prepare to address this\n2. \"Fast-paced\" may mean high pressure\n3. Need to research company culture more\n\n### Overall Recommendation:\n\n**APPLY - This is a strong opportunity**\n\nYou meet 80% of required skills and 67% of preferred skills. Your developer tools and B2B SaaS experience makes you a differentiated candidate. The SQL gap is addressable with honesty and emphasis on your analytical skills. Apply within 48 hours while posting is fresh.\n```\n\n## Requirement Classification Guide\n\n### Identifying \"Must Have\" vs \"Nice to Have\"\n\n**Language indicating REQUIRED:**\n- \"Must have...\"\n- \"Required: X years of...\"\n- \"You have...\"\n- \"Essential qualifications\"\n- Listed under \"Requirements\"\n- Mentioned 3+ times in description\n\n**Language indicating PREFERRED:**\n- \"Nice to have...\"\n- \"Bonus if you have...\"\n- \"Preferred qualifications\"\n- \"Ideally, you'd have...\"\n- \"A plus if...\"\n- Mentioned only 1-2 times\n\n### Dealbreaker Detection\n\n**Absolute dealbreakers (don't apply):**\n- Required license you don't have (medical, legal, CPA)\n- Required clearance you can't get\n- Years of experience 50%+ below requirement\n- Required degree you don't have (when stated as \"required\")\n- Location requirement you can't meet\n\n**Not dealbreakers (apply anyway):**\n- Years of experience slightly below (e.g., 3 years when they want 5)\n- \"Preferred\" degree you don't have\n- Nice-to-have tools\u002Fskills you can learn\n- Industry experience when you have transferable skills\n\n## Implementation Checklist\n\nWhen analyzing a job:\n\n1. ✅ Extract all requirements (required vs preferred)\n2. ✅ Identify all keywords (hard skills, soft skills, industry terms)\n3. ✅ Calculate match score\n4. ✅ Identify strengths to emphasize\n5. ✅ Identify gaps and strategies to address\n6. ✅ Detect red flags\n7. ✅ Create resume customization plan\n8. ✅ Generate cover letter talking points\n9. ✅ Research company\n10. ✅ Provide application recommendation and timeline\n\n## Edge Cases\n\n### Vague Job Descriptions\n- Flag as potential red flag\n- Extract what keywords you can\n- Recommend reaching out for clarity before applying\n- Use industry standard requirements as baseline\n\n### Multiple Roles in One JD\n- Identify the core role vs \"other duties\"\n- Focus match score on primary responsibilities\n- Flag scope creep concerns\n\n### Internal Postings (Already Working There)\n- Different strategy - emphasize internal knowledge\n- Highlight cross-team relationships\n- Reference specific company initiatives\n\n### Reposted Jobs\n- May indicate: Previous hire didn't work out, role expanded, or first search failed\n- Worth applying, but research why it was reposted\n- Check if requirements changed from original posting\n","# Job Description Analyzer\n\n## When to Use This Skill\n\nUse this skill when the user:\n- Wants to analyze a job posting\n- Asks \"should I apply to this job?\"\n- Wants to know their match percentage for a role\n- Needs help understanding job requirements\n- Wants to tailor their resume for a specific position\n- Mentions: \"analyze this job\", \"am I qualified\", \"match score\", \"should I apply\"\n\nUse this BEFORE resume tailoring to ensure effort is worth it.\n\n## Core Capabilities\n\n- Extract and categorize job requirements (must-have vs nice-to-have)\n- Calculate match score between user's experience and job requirements\n- Identify skill gaps and strengths\n- Detect red flags in job postings\n- Prioritize which experiences to highlight\n- Generate resume tailoring strategy\n- Create cover letter talking points\n- Assess company culture fit indicators\n\n## The Strategic Problem\n\nMost job seekers waste time on:\n- Jobs they're under-qualified for (\u003C60% match)\n- Jobs they're over-qualified for (flight risk)\n- Jobs with red flags (high turnover, toxic culture)\n- Applying to 50+ jobs blindly hoping something sticks\n\nBetter approach:\n- Apply to 10-15 jobs strategically\n- Target 70-90% match jobs\n- Customize deeply for each\n- Higher response rate, less burnout\n\n## Analysis Process\n\n### Step 1: Extract Requirements\n\nBreak job description into categories:\n\n**Required (Must-Have)**\n- Education requirements\n- Years of experience\n- Specific technical skills\n- Certifications\u002Flicenses\n- Industry experience\n\n**Preferred (Nice-to-Have)**\n- \"Bonus\" skills\n- Advanced certifications\n- Domain expertise\n- Specific tool experience\n\n**Soft Skills\u002FCulture**\n- Communication style\n- Work environment\n- Team structure\n- Company values\n\n### Step 2: Keyword Extraction\n\nIdentify three types:\n\n**Hard Skills** (Technical abilities)\n- Tools: Salesforce, Python, AWS, Excel\n- Methodologies: Agile, Six Sigma, SDLC\n- Certifications: PMP, CPA, AWS Certified\n\n**Soft Skills** (Interpersonal)\n- Leadership, collaboration, communication\n- Problem-solving, critical thinking\n- Adaptability, initiative\n\n**Industry\u002FDomain Knowledge**\n- B2B SaaS, healthcare, fintech\n- Enterprise vs SMB\n- Regulatory knowledge (HIPAA, SOX, GDPR)\n\n### Step 3: Calculate Match Score\n\n```\nMATCH CALCULATION:\n\nRequired Skills:\n- User has 8 out of 10 required = 80%\n\nPreferred Skills:\n- User has 3 out of 5 preferred = 60%\n\nOverall Match:\n- Weight required 70%, preferred 30%\n- (80% × 0.7) + (60% × 0.3) = 74%\n\nINTERPRETATION:\n90-100% = Overqualified (may be flight risk)\n75-89% = Excellent fit (apply immediately)\n60-74% = Good fit (apply with strong cover letter)\n50-59% = Stretch role (apply if passionate)\n\u003C50% = Under-qualified (skip unless dream job)\n```\n\n### Step 4: Gap Analysis\n\nFor each missing requirement:\n- **Critical gap**: Deal-breaker (don't apply)\n- **Major gap**: Significant but addressable (mention in cover letter)\n- **Minor gap**: Easy to learn (downplay or emphasize related skills)\n\n### Step 5: Red Flag Detection\n\nScan for warning signs:\n\n**Workload Red Flags:**\n- \"Wear many hats\"\n- \"Fast-paced environment\"\n- \"Hit the ground running\"\n- \"Self-starter in ambiguous situations\"\n\n**Culture Red Flags:**\n- \"Rockstar\u002FNinja\u002FGuru\"\n- \"We work hard, play hard\"\n- \"Unlimited vacation\"\n- \"Like a family\"\n\n**Compensation Red Flags:**\n- \"Competitive salary\" (won't tell you range)\n- \"Equity-heavy\" (low cash compensation)\n- \"Commission-based\" (no base salary)\n- \"DOE\" with no range\n\n## Match Score Output Format\n\n```markdown\n# JOB ANALYSIS REPORT\n\n**Position:** Senior Product Manager\n**Company:** TechCorp Inc.\n**Location:** San Francisco, CA (Hybrid)\n**Salary Range:** $140K-$180K + equity\n\n═══════════════════════════════════════════\n\n## OVERALL MATCH SCORE: 78% ✅\n\n**Recommendation:** STRONG FIT - Apply within 48 hours\n\n**Application Priority:** HIGH\n**Estimated Competition:** Medium (Posted 2 days ago)\n**Time to Tailor Resume:** 30-45 minutes\n\n═══════════════════════════════════════════\n\n## REQUIREMENTS BREAKDOWN\n\n### Required Skills - 8\u002F10 ✅\n\n✅ 5+ years product management (You have: 6 years)\n✅ B2B SaaS experience (You have: 4 years)\n✅ Agile\u002FScrum (You have: 5 years)\n✅ Cross-functional leadership (You have: Strong experience)\n✅ Data-driven decision making (You have: 3 years analytics)\n✅ API products (You have: 2 years)\n✅ Roadmap planning (You have: Extensive)\n✅ User research (You have: 2 years)\n❌ SQL\u002Fdata analysis (You have: Basic Excel only) ⚠️\n❌ Mobile product experience (You don't have) ⚠️\n\n### Preferred Skills - 4\u002F6 ✅\n\n✅ MBA or equivalent (You have: MBA from UC Berkeley)\n✅ Developer tools experience (You have: 2 years)\n✅ Payment systems (You have: 1 year)\n✅ International markets (You have: Worked with EU teams)\n❌ E-commerce background (You don't have)\n❌ Machine learning products (You don't have)\n\n### Soft Skills - 5\u002F5 ✅\n\n✅ Stakeholder management (Strong mentions in your resume)\n✅ Communication (You present regularly)\n✅ Strategic thinking (MBA + senior experience)\n✅ Influence without authority (You've done this)\n✅ Customer empathy (User research experience)\n\n═══════════════════════════════════════════\n\n## STRENGTHS TO EMPHASIZE\n\n**Your Top 3 Selling Points:**\n\n1. **B2B SaaS PM Experience**\n   - 4 years in SaaS, exactly what they want\n   - Lead with this in resume summary\n\n2. **API Product Background**\n   - Your developer tools experience is highly relevant\n   - This differentiates you from other candidates\n\n3. **Data-Driven Approach**\n   - Your analytics background addresses their need\n   - Emphasize metrics and data in every bullet\n\n═══════════════════════════════════════════\n\n## GAPS TO ADDRESS\n\n**Critical Gaps:** None ✅\n\n**Major Gaps:**\n⚠️ **SQL\u002FData Analysis**\n- They mention this 5x in job description\n- They want PM who can query data independently\n\n**Strategy:**\n- Don't avoid this gap\n- Address in cover letter: \"While my primary analytics work has been in Excel and BI tools, I'm actively learning SQL through DataCamp and can currently write basic queries\"\n- Emphasize your data-driven mindset and collaboration with data team\n\n**Minor Gaps:**\n- Mobile product experience (mentioned 2x)\n- Not a dealbreaker - they want \"any product,\" mobile just a plus\n\n**Strategy:**\n- Don't mention this gap\n- If asked in interview, pivot to \"transferable product skills\"\n\n═══════════════════════════════════════════\n\n## RESUME CUSTOMIZATION STRATEGY\n\n### Priority 1: Lead with Most Relevant Experience\n\n**Current Resume Order:**\n1. Company ABC - General PM work\n2. Company XYZ - Your developer tools role\n3. Company 123 - Early career\n\n**Recommended Order:**\n1. Company XYZ - Developer tools role (MOST RELEVANT)\n2. Company ABC - B2B SaaS work\n3. Company 123 - Only if space allows\n\n### Priority 2: Keyword Integration\n\n**Add These Exact Phrases:**\n- \"SQL and data analysis\" (mentioned 5x in JD)\n- \"API product management\" (mentioned 4x)\n- \"Developer-focused products\" (mentioned 3x)\n- \"Stakeholder alignment\" (mentioned 3x)\n\n**Where to Add:**\n- Professional Summary: Mention \"API products\" and \"data-driven\"\n- Skills Section: Add \"SQL (basic), Data Analysis, API Design\"\n- Experience: Weave into existing bullets\n\n### Priority 3: Quantify Everything\n\nThey mention \"metrics\" and \"KPIs\" 7 times total.\n\n**Enhance These Bullets:**\n\nCurrent: \"Led product roadmap\"\nBetter: \"Defined product roadmap based on analysis of 50+ customer interviews and usage data from 100K+ users\"\n\nCurrent: \"Launched new features\"\nBetter: \"Launched 8 features in 12 months, increasing user engagement by 35% and reducing churn by 20%\"\n\n═══════════════════════════════════════════\n\n## COVER LETTER TALKING POINTS\n\n### Opening Hook (Choose One):\n\n**Option 1 - Specific Company Knowledge:**\n\"I noticed TechCorp recently launched your API marketplace - I've spent the last 2 years as PM for a developer tools platform, and I'm excited about the opportunity to bring that experience to your growing API ecosystem.\"\n\n**Option 2 - Mutual Connection:**\n\"[Name] on your product team mentioned you're looking for a PM to lead the API product line - my 2 years in developer tools and B2B SaaS background would be a strong fit.\"\n\n**Option 3 - Problem-Solver:**\n\"Your JD mentions challenges in stakeholder alignment across technical teams - I've navigated this exact challenge at my current role, aligning engineering, design, and sales teams across 6 concurrent product initiatives.\"\n\n### Body - Address the Match:\n- \"Your requirement for B2B SaaS experience: I have 4 years with...\" \n- \"Your focus on data-driven decisions: In my current role, I...\"\n- \"Your need for API product expertise: At [Company], I...\"\n\n### Addressing SQL Gap (Optional):\n\"While my data analysis has primarily been in Excel and Tableau, I'm expanding my SQL skills and can currently write basic queries. More importantly, I've built strong partnerships with data teams and consistently use data to inform product decisions.\"\n\n═══════════════════════════════════════════\n\n## RED FLAGS ANALYSIS\n\n### Potential Concerns: ⚠️ MINOR\n\n**Flag 1:** \"Fast-paced environment\"\n- Appears 2x in description\n- Interpretation: Likely startup or high-growth\n- May mean: Long hours, ambiguity, rapid changes\n\n**Flag 2:** Salary range is wide ($140K-$180K)\n- 29% spread\n- May indicate: Experience range is flexible, or negotiation room\n\n### Positive Signals: ✅\n\n**Signal 1:** Detailed job description\n- Shows company knows what they want\n- Well-organized role\n\n**Signal 2:** Mentions specific tools (JIRA, Amplitude)\n- Shows operational maturity\n\n**Signal 3:** Hybrid flexibility mentioned\n- Modern workplace practices\n\n### Company Research Needed:\n\nBefore applying, check:\n- Glassdoor reviews (look for patterns in 1-2 star reviews)\n- Recent funding\u002Fnews (layoffs? growth?)\n- LinkedIn: Check how long people stay (high turnover?)\n- Levels.fyi: Verify salary range is accurate\n\n═══════════════════════════════════════════\n\n## APPLICATION TIMELINE\n\n**✅ Day 1 (Today):**\n- Customize resume (30-45 minutes)\n- Write cover letter (30 minutes)\n\n**✅ Day 1-2:**\n- Submit application\n- Connect with 2-3 current employees on LinkedIn\n- Research company more deeply\n\n**✅ Week 1:**\n- Follow up if no response after 7 days\n\n**? Expected Response Time:** 1-2 weeks\n\n**? Interview Process (from job posting):**\n1. Recruiter screen (30 min)\n2. Hiring manager (1 hour)\n3. Product case study (take-home)\n4. Team interviews (3-4 hours)\n5. Executive interview (1 hour)\n\n═══════════════════════════════════════════\n\n## DECISION FACTORS\n\n### Reasons to Apply ✅\n\n1. Strong match (78%) - You meet most requirements\n2. Role aligns with career goals\n3. Salary range is appropriate for your experience\n4. Company stage fits your preferences\n5. You have unique relevant experience (developer tools)\n\n### Reasons to Hesitate ⚠️\n\n1. SQL gap is real - prepare to address this\n2. \"Fast-paced\" may mean high pressure\n3. Need to research company culture more\n\n### Overall Recommendation:\n\n**APPLY - This is a strong opportunity**\n\nYou meet 80% of required skills and 67% of preferred skills. Your developer tools and B2B SaaS experience makes you a differentiated candidate. The SQL gap is addressable with honesty and emphasis on your analytical skills. Apply within 48 hours while posting is fresh.\n```\n\n## Requirement Classification Guide\n\n### Identifying \"Must Have\" vs \"Nice to Have\"\n\n**Language indicating REQUIRED:**\n- \"Must have...\"\n- \"Required: X years of...\"\n- \"You have...\"\n- \"Essential qualifications\"\n- Listed under \"Requirements\"\n- Mentioned 3+ times in description\n\n**Language indicating PREFERRED:**\n- \"Nice to have...\"\n- \"Bonus if you have...\"\n- \"Preferred qualifications\"\n- \"Ideally, you'd have...\"\n- \"A plus if...\"\n- Mentioned only 1-2 times\n\n### Dealbreaker Detection\n\n**Absolute dealbreakers (don't apply):**\n- Required license you don't have (medical, legal, CPA)\n- Required clearance you can't get\n- Years of experience 50%+ below requirement\n- Required degree you don't have (when stated as \"required\")\n- Location requirement you can't meet\n\n**Not dealbreakers (apply anyway):**\n- Years of experience slightly below (e.g., 3 years when they want 5)\n- \"Preferred\" degree you don't have\n- Nice-to-have tools\u002Fskills you can learn\n- Industry experience when you have transferable skills\n\n## Implementation Checklist\n\nWhen analyzing a job:\n\n1. ✅ Extract all requirements (required vs preferred)\n2. ✅ Identify all keywords (hard skills, soft skills, industry terms)\n3. ✅ Calculate match score\n4. ✅ Identify strengths to emphasize\n5. ✅ Identify gaps and strategies to address\n6. ✅ Detect red flags\n7. ✅ Create resume customization plan\n8. ✅ Generate cover letter talking points\n9. ✅ Research company\n10. ✅ Provide application recommendation and timeline\n\n## Edge Cases\n\n### Vague Job Descriptions\n- Flag as potential red flag\n- Extract what keywords you can\n- Recommend reaching out for clarity before applying\n- Use industry standard requirements as baseline\n\n### Multiple Roles in One JD\n- Identify the core role vs \"other duties\"\n- Focus match score on primary responsibilities\n- Flag scope creep concerns\n\n### Internal Postings (Already Working There)\n- Different strategy - emphasize internal knowledge\n- Highlight cross-team relationships\n- Reference specific company initiatives\n\n### Reposted Jobs\n- May indicate: Previous hire didn't work out, role expanded, or first search failed\n- Worth applying, but research why it was reposted\n- Check if requirements changed from original posting\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Fjob-description-analyzer",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add davila7\u002Fclaude-code-templates --skill job-description-analyzer",{"tool":56,"command":57},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill job-description-analyzer",{"tool":59,"command":60},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill job-description-analyzer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Fjob-description-analyzer\u002FSKILL.md",true,[64],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"agents\u002Fopenai.yaml","REFERENCE","参考文档",141,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fhandoff\u002Fagents\u002Fopenai.yaml",[71,101,128,161,196,220],{"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},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[83,84,85,86,87,88,89,90,27,34,91,92,93,94,95,96,97,98,99,100],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":108,"publishedAt":35},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[107],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[109,110,111,112,113,114,115,116,117,118,119,34,120,121,122,123,124,125,126,127],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":143,"publishedAt":35},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[134,137,138],{"categoryNo":135,"categoryName":136,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[144,145,146,147,148,149,150,88,151,152,153,154,155,156,157,27,158,159,34,160],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":165,"licenseFileUrl":166,"sourceHtmlUrl":167,"categories":168,"keywords":172,"publishedAt":35},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[169],{"categoryNo":170,"categoryName":171,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000009","前端开发",[173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,88,195],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":165,"licenseFileUrl":200,"sourceHtmlUrl":201,"categories":202,"keywords":207,"publishedAt":35},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[203,206],{"categoryNo":204,"categoryName":205,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":170,"categoryName":171,"taxonomyType":80,"taxonomyTypeDesc":81},[208,209,210,211,212,174,213,183,184,214,215,216,217,88,218,92,219],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":165,"licenseFileUrl":224,"sourceHtmlUrl":225,"categories":226,"keywords":234,"publishedAt":35},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[227,230,231],{"categoryNo":228,"categoryName":229,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},{"categoryNo":232,"categoryName":233,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000036","内容创作者",[235,236,237,238,239,240,241,242,176,243,186,120,244,245,246,247,248,156,249,34,250,251,252,253,254,98,255],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]