Agent skill · writing content · github
technical-job-search
Use this skill when a software engineer asks for help with job search tasks: parsing or analyzing a job description, tailoring a CV/resume, writing a cover letter, evaluating a job offer, or drafting a post-interview follow-up email. Do not activate for general career advice unrelated to an active job search action.
Why this skill is useful
Provides structured frameworks for analyzing job descriptions and tailoring CVs that are not commonly found in generic career advice.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Technical Job Search Helps software engineers with discrete job search tasks: job description analysis, CV tailoring, cover letter writing, offer evaluation, and follow-up emails. --- Job Description Analysis When given a job description, extract and structure: Must-haves (explicitly required or repeated multiple times): Technical skills, years of experience, specific domain knowledge Nice-to-haves (preferred, a bonus, or mentioned once): List these separately. Candidates often disqualify themselves over requirements that are actually optional. What the role actually solves (inferred from the description): Summarize in 2-3 sentences what business problem this hire addresses Red flags to surface: "Wear many hats" with no clarity on scope — risk of undefined ownership 10+ must-have technologies for a single role — unrealistic bar or poor team planning No mention of team size, tech stack, or what the role ships — may indicate disorganization --- CV / Resume Tailoring When tailoring a CV to a specific job description: 1. Match language exactly — use the same terminology as the JD, not synonyms. If the JD says "distributed systems", do not write "large-scale systems". 2. Lead with impact — every bullet should have a result: "Reduced P99 latency by 40%" not "Worked on performance improvements". 3. Quantify everything possible — users, QPS, team size, cost saved, revenue impact. 4. Cut what does not match — a two-page CV tailored to the role beats a four-page generic one. 5. Mirror the seniority signals — entry roles want "built", senior roles want "designed", staff and principal roles want "drove" or "defined". Do not keyword-stuff. Write for the hiring manager reading it, not for an ATS parser. --- Cover Letter Writing A cover letter should answer three questions in under 300 words: 1. Why this company? Something specific — a product, a technical challenge they have written about, a problem space you care about. Not "I admire your mission." 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/technical-job-search