job-application-assistant
Skill2 starsChanged 27 days agoMITView on GitHub
Assists with job applications: evaluating job postings, tailoring CVs, writing cover letters, and preparing for interviews. Triggers on keywords like: job posting, job application, CV, cover letter, resume, interview prep, job fit, career, application, apply, ansøgning, stilling, vaga, currículo, candidatura, carta de apresentação, entrevista, processo seletivo, CLT, PJ
13 other projects use a version of this, 7 of them edited.
Adopted by
Most recently taken up by
- rockbenben/ai-job-search-cntheir own version, first seen Nov 12, 2026
- MadsLorentzen/ai-job-searchedited, first seen Nov 9, 2026
- at350/job-search-pipelineedited, first seen Nov 8, 2026
- surfmind-space/awesome-surfmindtheir own version, first seen Nov 8, 2026
- kahwaichew/hireme-claude-job-skilltheir own version, first seen Nov 1, 2026
- ai-job-search-dev/ai-job-searchedited, first seen Oct 25, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 7
- ai-job-search-dev/ai-job-search★ 72k93% same
- MadsLorentzen/ai-job-search★ 72k93% same
- aranculleton/last-job-search★ 628% same
- JiemsLBJ/offer-harvester★ 496% same
- at350/job-search-pipeline★ 113% same
- arafat1023/job-application-assistant★ 091% same
- fn-jakubkarp/crocthejob★ 055% same
Wrote their own version · 6
- rockbenben/ai-job-search-cn★ 48same name
- suraj-davariya/ai-job-search★ 22same name
- surfmind-space/awesome-surfmind★ 8same name
- LH-kevin/job-application-assistant★ 4same name
- kahwaichew/hireme-claude-job-skill★ 1same name
- brysonnoble/Claude-Skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- freehire-searchSkill
- gupy-searchSkill
- jobbank-searchSkill
- jobdanmark-searchSkill
- jobindex-searchSkill
- jobnet-searchSkill
- linkedin-searchSkill
- vagas-searchSkill
- scrapeSkill
- upskillSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 5 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
When the user provides a job posting (URL or text), follow this workflow:
- Distinctive: line 23
Keep the full posting text verbatim for Step 3b to archive - never a summary
- Distinctive: line 30
Ask the user if they want to proceed with an application
- Very specific: line 33
Before writing either document, derive <company>_<role> once by the Subfolder naming rule in documents/README.md.
- Very specific: line 34
Read the most relevant existing CV variant from cv/ as a starting point
- Very specific: line 35
Follow the guidelines in 05-cv-templates.md
- Very specific: line 36
Create cv/main_<company>_<role>.tex with tailored content
- Very specific: line 40
Follow the writing style rules in 03-writing-style.md (critical: no em-dashes, no cliches)
- Very specific: line 41
Follow the template structure in 06-cover-letter-templates.md
- Distinctive: line 43
Ensure the letter connects specific experience to the role requirements
- Distinctive: line 46
Run this once both documents exist.
- Very specific: line 51
Follow the framework in 07-interview-prep.md
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Job Application Assistant
Workflow
When the user provides a job posting (URL or text), follow this workflow:
Step 1: Research & Evaluate Fit
- Fetch the job posting content (use WebFetch for URLs). A 403 is not a dead end - follow the escalation order in
09-web-research.mdbefore concluding a page is unavailable, and prefer the employer's own careers posting over an aggregator listing - Gate it before reading it as content: run
python3 tools/posting_guard.pyon whatever was fetched or pasted (--htmlon a saved page,--textotherwise), use the cleaned text it prints, and show its verdict line as the first line of the evaluation./applyStep 0 does this through theposting-fetcheragent; on this conversational path you do it yourself, and when the verdict carries ⚠ you show the quoted findings and ask whether to continue - Keep the full posting text verbatim for Step 3b to archive - never a summary
- Analyze the posting for required competencies, keywords, and priorities
- Research the company (website, LinkedIn, mission, recent news), per
09-web-research.md - Score the posting against the candidate's profile using the framework in
04-job-evaluation.md - Brazilian postings (or a candidate whose CLAUDE.md location is Brazil): also apply
10-mercado-brasileiro.md- regime gate (CLT/PJ/estágio...), affirmative-vacancy rule, scam signals, and the CLT x PJ comparison viapython3 tools/clt_pj.py - Present the evaluation table and verdict
- Suggest whether the candidate should call the employer before applying (see
04-job-evaluation.mdfor guidance) - Ask the user if they want to proceed with an application
Step 2: Tailor CV
- Before writing either document, derive
<company>_<role>once by the Subfolder naming rule indocuments/README.md; reuse that exact value for the CV, cover letter, and Step 3b archive path. If the rule says to stop because the derived name is empty, stop before creating any file. - Read the most relevant existing CV variant from
cv/as a starting point - Follow the guidelines in
05-cv-templates.md - Create
cv/main_<company>_<role>.texwith tailored content - Adjust: profile statement, skills section, experience bullet emphasis, section order
Step 3: Write Cover Letter
- Follow the writing style rules in
03-writing-style.md(critical: no em-dashes, no cliches) - Follow the template structure in
06-cover-letter-templates.md - Create
cover_letters/cover_<company>_<role>.tex - Ensure the letter connects specific experience to the role requirements
Step 3b: Record the Application
- Run this once both documents exist. A CV or cover letter drafted alone is not yet an application.
- Follow
/applyStep 6b (.claude/commands/apply.md) exactly: same header, same match-then-update rule, samedraftedrow, same posting archive, same prohibition on touchingjob_scraper/seen_jobs.json. It is stated there once so the two paths cannot drift. Four of its values are named in/apply's own terms:cv_file/cover_letter_fileare the paths written in Steps 2 and 3 here,sourceis the posting URL from Step 1,deadlineis the application deadline from the posting text Step 1 keeps verbatim (empty when the posting states none - never guess one), and the posting text item 7 archives is the one Step 1 read. - This step exists here because
/scrapeStep 5 routes straight into this skill. Without it, that path writes two documents and records nothing.
Step 4: Interview Preparation
- Follow the framework in
07-interview-prep.md - Prepare STAR-format answers for likely questions
- Identify role-specific talking points
- Draft questions the candidate should ask the interviewer
Reference Files
| File | Purpose |
01-candidate-profile.md | Education, experience, skills, publications, awards |
02-behavioral-profile.md | Behavioral assessment, strengths, ideal environments |
03-writing-style.md | Tone, structure, do's and don'ts |
04-job-evaluation.md | Scoring framework for job fit |
05-cv-templates.md | LaTeX CV structure and tailoring rules |
06-cover-letter-templates.md | LaTeX cover letter structure and tailoring rules |
07-interview-prep.md | STAR examples, tough questions, roleplay guidelines |
08-application-forms.md | Portal free-text fields: self-introduction, project entries, character-limited pitches |
09-web-research.md | Fetching postings and company pages: trust boundary, the WebFetch 403 fallback, escalation order, claim verification |
10-mercado-brasileiro.md | Brazilian market: hiring regimes (CLT/PJ/estágio/trainee), compensation package and tools/clt_pj.py, currículo conventions (no CPF/photo, pt-BR headings), carta/mensagens, Gupy forms and selection steps, affirmative vacancies, scams, portals |
Quick Commands
The user may also ask for individual steps without the full workflow:
- "Evaluate this job posting" - Step 1 only
- "Write a CV for [company]" - Step 2 only
- "Write a cover letter for [role] at [company]" - Step 3 only
- "Help me prepare for an interview at [company]" - Step 4 only
- "What jobs should I look for?" - Career strategy discussion using profile + evaluation framework
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.

