Job application assistant
Skill suraj-davariya/ai-job-search/.claude/skills/job-application-assistant
Tailors CVs and cover letters, evaluates job fit, and prepares interviews. Activates on: applying to a job, evaluating a posting, writing a CV/cover letter, interview prep.From its SKILL.md
npx -y skills add suraj-davariya/ai-job-search --skill job-application-assistantAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
4.3 KB, 979 tokens by cl100k_base, as published. Nobody here has run it
Purpose
This file is the Plane 1 knowledge anchor for the job application workflow (ARCH-0010). As a Plane 1 skill, it lives under .claude/skills/job-application-assistant/ and provides the AI assistant with structured knowledge — it does not execute binaries. When activated, this skill loads candidate identity and preference data from the companion profile files and applies the framework rules that govern the drafter-reviewer pipeline (ARCH-0030). The skill supports all four pipeline steps: fit evaluation, CV generation, cover letter generation, and interview preparation. All steps operate under the no-fabrication rule (ARCH-0007), the read-before-write invariant, and the writing-style rules in 03-writing-style.md.
Trigger Phrases
- "Apply to <job/URL/company>"
- "Evaluate this job posting"
- "Tailor my CV for <role/company>"
- "Write a cover letter for <company>"
- "Prepare me for an interview with <company>"
- "Am I a good fit for <job>?"
- Any phrase about job applications, fit evaluation, or interview prep
Companion Files
| File | When to Read |
|---|---|
01-candidate-profile.md | Whenever candidate identity, education, experience, or skills data is needed |
02-behavioral-profile.md | For behavioral/culture fit evaluation or when writing about personality fit |
03-writing-style.md | Before generating any CV or cover letter content — rules always apply |
04-job-evaluation.md | When evaluating fit for a job posting (Step 1 of pipeline) |
05-cv-templates.md | When generating or tailoring a CV (Step 2 of pipeline) |
06-cover-letter-templates.md | When generating a cover letter (Step 3 of pipeline) |
07-interview-prep.md | When preparing for an interview or running practice sessions |
08-legitimacy.md | Before drafting (Step 1) — assess posting legitimacy as a separate gate (REQ-8001) |
Sub-Commands (REQ-6003)
| Entry Phrase | Pipeline Step | Files to Read |
|---|---|---|
| "Evaluate this job posting" | Step 1 — Fit Evaluation | 04-job-evaluation.md, 08-legitimacy.md, 01-candidate-profile.md, 02-behavioral-profile.md |
| "Write a CV for <company>" | Step 2 — CV Generation | 05-cv-templates.md, 01-candidate-profile.md, 03-writing-style.md |
| "Write a cover letter for <company>" | Step 3 — Cover Letter | 06-cover-letter-templates.md, 01-candidate-profile.md, 02-behavioral-profile.md, 03-writing-style.md |
| "Prepare for interview with <company>" | Step 4 — Interview Prep | 07-interview-prep.md, 01-candidate-profile.md |
Missing context rule: Each sub-command can run without upstream steps having completed. If upstream context is missing, prompt: "I need [X] first — want me to run that step now?" Never silently fail or fabricate missing information (ARCH-0007). All sub-commands share 03-writing-style.md rules, the no-fabrication rule, and the verification checklist.
Contract
- Always read existing profile files before writing (read-before-write invariant)
- Respect
[UPPER_SNAKE_CASE]placeholder tokens — do not overwrite them with invented data - Default AI tool name in all generated documents: Claude Code (unless
[AI_TOOL_NAME]is set in01-candidate-profile.md— DEC-017) - Never fabricate skills, experience, or claims not present in the candidate profile (ARCH-0007)
- The full application pipeline (ARCH-0030) has 7 steps: 0=Parse, 1=Evaluate, 2=Draft, 3=Reviewer Dispatch, 4=Revise, 5=Compile+Verify, 6=Final Checklist. The Sub-Commands table above labels user-facing entry points (Fit Evaluation, CV Gen, Cover Letter, Interview Prep) using shorthand step names — these are not the same as the pipeline step numbers.
- The verification checklist (pipeline Step 6 — Final Checklist) runs exactly once at the end of the full
/applypipeline. It does NOT run during the reviewer pass (pipeline Step 3 — Reviewer Dispatch, a separate Claude Code invocation with fresh context per ARCH-0002). Never run the verification checklist inside the reviewer's context.
What ships with it: 9 files
51.8 KB alongside SKILL.md
- 01-candidate-profile.md1.8 KB
- 02-behavioral-profile.md2.0 KB
- 03-writing-style.md7.1 KB
- 04-job-evaluation.md5.2 KB
- 05-cv-templates.md14.9 KB
- 06-cover-letter-templates.md11.0 KB
- 07-interview-prep.md7.3 KB
- 08-legitimacy.md2.5 KB
- .gitkeep0 B
Gives 0 of the 12 instructions most hr recruiting skills give in 979 tokens
Counted across 356 of the 357 authors here whose files we hold, read 2026-08-07
- Quantify achievements with specific metricsin 14 of 356, across 6 files
- Keep the resume under two pagesin 14 of 356, across 6 files
- Request the full job description if not providedin 12 of 356, across 4 files
- Extract keywords and prioritize job requirementsin 12 of 356, across 4 files
- Stop and ask for clarification if required inputs are missingin 12 of 356, across 5 files
- Map candidate experience to job requirementsin 11 of 356, across 3 files
- Ask if the user wants adjustmentsin 11 of 356, across 3 files
- Provide strengths and gap analysis after the resumein 10 of 356, across 2 files
- Request candidate background details if not providedin 10 of 356, across 2 files
- Format experience bullets as action verb plus resultin 10 of 356, across 2 files
- Ask for missing inputs before startingin 10 of 356, across 9 files
- Use exact job description terminologyin 9 of 356, across 1 file
Said here and by no other author read
- read existing profile files before writing
- evaluate job posting legitimacy before drafting
- assess candidate fit for the job posting
- generate tailored CVs using templates
- write cover letters using templates
- respect placeholder tokens
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.