job-fit-analyzer
Skill9 starsChanged 7 months agoMITView on GitHub
Analyze any job posting to see if you're a fit — match score, skill gap breakdown, red flag detection, and whether it's worth applying
In this repository11 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use when the user wants to analyze a job posting, know if they should apply, or understand their fit for a role.
- Distinctive: line 14
Use BEFORE resume-customizer to determine if customizing is worth the effort.
- Distinctive: line 101
If the job description is vague, flag that as a concern itself
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Job Fit Analyzer
Trigger
Use when the user wants to analyze a job posting, know if they should apply, or understand their fit for a role.
Keywords: "am I a fit", "job fit", "should I apply", "am I qualified", "analyze this job", "analyze job posting", "job description", "job requirements", "qualification check", "match score", "skill gap", "is this job right for me", "job red flags", "do I qualify", "job match"
Use BEFORE resume-customizer to determine if customizing is worth the effort.
Process
Step 1: Extract Requirements
Parse the job description into:
- Required (must-have): stated as required/essential/minimum qualifications
- Preferred (nice-to-have): stated as bonus/preferred/ideal
- Implicit: inferred from the responsibilities section
For each, note: hard skills, soft skills, years of experience, education, certifications, domain knowledge.
Step 2: Calculate Match Score
Required match = matched required / total required
Preferred match = matched preferred / total preferred
Overall = (required × 0.7) + (preferred × 0.3)Interpretation:
- 85%+: Strong fit — apply immediately
- 70-84%: Good fit — apply with targeted resume
- 55-69%: Stretch role — apply if motivated
- <55%: Under-qualified — skip unless dream job
Step 3: Gap Analysis
Classify each missing requirement:
- Dealbreaker: Required license/clearance/degree you can't obtain
- Addressable: Significant gap you can explain in cover letter
- Minor: Easy to learn or close enough to dismiss
Step 4: Red Flag Scan
Flag warning signs neutrally:
- Vague responsibilities or scope creep ("wear many hats")
- Culture signals ("rockstar", "family", "hustle")
- Compensation opacity ("competitive salary" with no range, equity-heavy)
- Role instability (reposted multiple times, vague about why it's open)
Step 5: Recommend Strategy
Based on match score and gaps:
- Apply / Skip / Apply with caveats
- Which experiences to emphasize
- Gaps to address in cover letter
- Keywords to add to resume
- Estimated customization effort (quick tweak vs. significant rework)
Output Format
## Job Analysis: [Title] at [Company]
**Match Score: X%** — [STRONG FIT / GOOD FIT / STRETCH / SKIP]
### Requirements Breakdown
| Requirement | Status | Notes |
|---|---|---|
| [Skill] | ✅ Match | [your evidence] |
| [Skill] | ❌ Gap | [severity + strategy] |
| [Skill] | ⚠️ Partial | [explanation] |
### Strengths to Emphasize
1. [Top selling point for this role]
2. [Second strongest match]
3. [Third]
### Gaps to Address
- [Gap]: [How to handle in resume/cover letter]
### Red Flags
- [Flag]: [What it might mean]
### Application Strategy
- Resume focus: [what to emphasize]
- Cover letter: [key points to address]
- Timeline: [urgency based on posting age]Rules
- Be honest about match — don't encourage applying to clearly wrong roles
- Distinguish "required" from "preferred" carefully (many JDs inflate requirements)
- Years-of-experience requirements are often flexible (±2 years is normal)
- If the job description is vague, flag that as a concern itself
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

