skills/technical-job-search/SKILL.md
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.
npx skillsauth add williamlimasilva/.copilot technical-job-searchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Helps software engineers with discrete job search tasks: job description analysis, CV tailoring, cover letter writing, offer evaluation, and follow-up emails.
When given a job description, extract and structure:
Must-haves (explicitly required or repeated multiple times):
Nice-to-haves (preferred, a bonus, or mentioned once):
What the role actually solves (inferred from the description):
Red flags to surface:
When tailoring a CV to a specific job description:
Do not keyword-stuff. Write for the hiring manager reading it, not for an ATS parser.
A cover letter should answer three questions in under 300 words:
Format: three short paragraphs. No preamble ("I am writing to apply for..."). No summary of your CV.
Avoid:
When evaluating a job offer, compare across these dimensions:
Compensation
Role clarity
Company health
Red flags in an offer
Get everything in writing before accepting.
After an interview, send a follow-up within 24 hours:
Do not write multiple paragraphs. Do not restate your qualifications. Do not follow up more than once if there is no reply.
development
Anxiety-aware, evidence-driven collaboration for stalled or high-stakes work when a user says uncertainty, repeated setbacks, or lack of visible progress is causing significant anxiety or distress. Use immediately when explicitly invoked; when this fit is only inferred from the user's own account, ask permission before applying it. Preserve the user's ideal and turn grounded perspective-taking into persistent, bounded problem solving. Do not use to diagnose, provide therapy, manufacture certainty, or lower goals for reassurance.
development
Build, review, debug, package, and test Roslyn diagnostic analyzers, code fix providers, and incremental source generators. Use for DiagnosticAnalyzer, CodeFixProvider, IIncrementalGenerator, IOperation analysis, Microsoft.CodeAnalysis dependency pinning, Roslyn test harnesses, C#/VB tests, and analyzer NuGet packaging.
testing
Migrates a project that uses checked-in .designer.cs files behind .resx to using a source-generator instead
development
Polish any GitHub repository's surface — labels (emoji rating tiers, P0–P3 priority, impact severity), issue forms, PR template, CI workflows, CODEOWNERS, rulesets, docs. Repo meta & config only — no code logic touched. Use when creating a new repo or polishing an existing one.