Job applications pack reference

Every skill in the Job applications pack — what it makes, when to use it, what it needs, its quality bar, and what it hands off to.

Job applications, for any occupation: a shortlist of which of an employer's roles to go for, an honest check of your resume against the posting, a tailored resume and a cover letter that say nothing you didn't, the application form's answers drafted from your resume, and a script that lists every figure and name in a draft that your own resume doesn't contain.

Skills

application-form-answers

Prepare the answers to a job application form from the person's resume: each question in the form's own order with either a drafted answer and the resume line behind it, or a note that it is theirs alone to answer (right to work, sponsorship, salary, declarations, monitoring questions), plus the questions that could screen the application out and the ones their resume already bears on. Works for any occupation.

Tier standard · v0.1.0 · SKILL.md · skill page

Use it when the user says "help me fill in this application form", "answer these application questions", "what do I put for these screening questions", or pastes the questions from an online job application.

A good result:

• Every question on the form appears once, in the form's order and wording.
• No declaration, preference or private fact is answered for the person.
• Every drafted answer traces to the resume or the person's own words, and fits its limit.
• Honest answers that could screen the application out are named first, and left honest.
• Where the resume bears on a question that is theirs, they are told.

Not for:

• Deciding whether the job is worth applying for. Use job-fit-analysis.
• Tailoring the resume the form asks you to upload. Use resume-tailor.
• Writing the cover letter the form asks you to attach. Use cover-letter.

cover-letter

Write a cover letter for one job from the person's resume and the posting: under a page, opening on the strongest evidence for the role, two or three specifics matched to what the employer asked for, and no enthusiasm, company facts or experience the person didn't supply. A script lists every figure and name in the letter that their own material doesn't contain. Works for any occupation and level.

Tier standard · v0.1.1 · SKILL.md · skill page

Use it when the user says "write a cover letter for this job", "draft a covering letter", "write the cover note for my application", or needs an application email to go with a resume.

Needs: Python 3 for its scripts (standard library only).

A good result:

• Every claim about the person is in their resume or their own words.
• Every claim about the employer is in the posting or was supplied by the person.
• The first two sentences name the job and give real evidence.
• 200 to 350 words, and within any limit the posting sets.
• It can be sent as it is: no placeholders, brackets or notes.

Not for:

• Checking whether the job is worth applying for. Use job-fit-analysis.
• Rewriting the resume itself. Use resume-tailor.
• Removing machine artifacts from a letter that is already written. Use output-hygiene.

job-fit-analysis

Compare a job posting with a resume and say honestly whether to apply: each requirement marked met, partly met, not shown or not met, with the resume line it rests on; the requirements an employer screens on listed first; and the questions whose answers would change the picture. Works for any occupation and level.

Tier standard · v0.1.3 · SKILL.md · skill page

Use it when the user asks "am I a good fit for this job", "should I apply for this", "how does my resume match this posting", or wants the gaps between a job description and their CV before applying.

A good result:

• Every Met and Partly quotes the resume. A status with no line behind it is a guess.
• What could get the application rejected is named first, never left as one row among many.
• No length of time appears that the resume's own dates don't give.
• Not shown and Not met are kept apart. One is a question, the other is a gap.
• Nothing is credited that the resume or the person doesn't state.
• The verdict matches the table. An unmet required degree cannot sit under "strong match", and a verdict that names one gap cannot sit over a table that shows four.

Not for:

• Sorting a long list of openings into which to apply for. Use role-shortlist, then come back for the first choice.
• Rewriting the resume for the posting. Use resume-tailor.
• Writing the cover letter. Use cover-letter.
• Critiquing the resume as a document, with no job in mind. Use doc-critique.

resume-tailor

Tailor a resume or CV to one job posting without adding anything that isn't true: reorder, cut and reword what the person has already done so the posting's needs are answered first, keep every employer, title, date and number as it was, and report what the posting asks for that the resume cannot claim. A script lists every figure and name in the draft that the original doesn't contain. Works for any occupation and level.

Tier standard · v0.1.2 · SKILL.md · skill page

Use it when the user says "tailor my resume for this job", "adapt my CV to this posting", "rewrite my resume for this role", or pastes a job description next to their resume.

Needs: Python 3 for its scripts (standard library only).

A good result:

• Every employer, title, date, qualification and number matches the original exactly.
• Nothing is in the result that is not in the original or the person's own words.
• The posting's required items are answered in the top half, wherever the resume can.
• The file can be sent as it is: no placeholders, notes or brackets.
• What the resume cannot claim is reported to the person, not papered over.
• Nothing is cut silently and nothing from outside the resume is added silently.
• The original file and its project are untouched.

Not for:

• Deciding whether to apply at all. Use job-fit-analysis.
• Writing the covering letter. Use cover-letter.
• Reviewing a resume's quality with no job in mind. Use doc-critique.

role-shortlist

Read every open role on an employer's careers page, a job-board export or a folder of saved postings, and say which ones one person should apply for — each role judged only from its own posting text, roles that couldn't be read listed as unread instead of guessed from their titles, a role whose screening requirement the person doesn't meet named as out whatever else fits, and the same role posted twice counted once. Works for any occupation.

Tier standard · v0.1.1 · SKILL.md · skill page

Use it when the user asks "which of these jobs should I apply for", "go through this company's openings", "shortlist these postings against my CV", or has more postings than they want to check one by one.

A good result:

• No role is ranked without its posting text having been read. Unread roles are listed as unread, with no verdict.
• A role with an unmet screening requirement is never under Apply, and the requirement is named. An item the posting calls preferred is never treated as one.
• Every role given appears exactly once; duplicates are merged, closed ones are noted.
• Every "fits" rests on the person's own material, and a similar thing is not counted as the named one.
• The answer opens the reply, and the size is the one asked for, with no empty groups.

Hands off to: job-fit-analysis when the shortlist has put one or two roles under Apply.

Not for:

• A full, requirement-by-requirement check of one posting — use job-fit-analysis on the role this shortlist puts first
• Rewriting the resume for a role — use resume-tailor
• Searching the internet for jobs to apply for — this reads the postings you have or point to

Loops

apply

Take one job posting and one resume to an application ready to send — an honest fit check, a tailored resume, a cover letter and the answers to the application form — with the candidate deciding whether to apply before any writing, and confirming every claim is true before anything is sent.

Cap: 3 returns before BLOCKED. LOOP.md

Included from core

Installed with this pack. Details: Core pack reference.

• brief-intake: Turn raw mess — a Slack thread, meeting transcript, Jira ticket, half-written Notion page, email chain, or paragraph of free-form context — into a structured brief that the downstream skill (adr-generator, design-doc, runbook-generator, exec-summary, slide-outliner) can consume without further intake.
• context-graph: Map the decisions behind a codebase from its ADRs, RFCs and design records — each record's status and date, what supersedes or amends what, which records cite which, the files and folders each decision governs, and with git the commits that implemented it and the commits that changed each decision's code since it was made, and who made them — then answer "why is it like this?" from the record and check the record is still true. Finds supersessions only one side records, current decisions pointing at code that is gone, code that has drifted from its decision, two current decisions governing the same path, and references to records that don't exist.
• council-review: Convene a council of distinct senior-engineer personas (Architect, Security, Operator/SRE, Pragmatist, User-Advocate, plus optional bench seats) to deliberate a decision, design, or code change — each takes an independent stance, the genuine disagreements are surfaced as named cruxes, and a Chair issues a reconciled verdict that records dissents and states what would change the decision. The "Claude Council."
• doc-critique: Review an existing document — ADR, design doc, runbook, exec summary, tech-comparison matrix, deck outline, decision log — and produce a structured critique against the same quality bars the skilldrop generators enforce. Categorizes findings by severity (blocker / major / minor / nit), points to the exact section/line, and suggests a concrete fix for each.
• output-hygiene: Review agent-written text before it ships and strip the machine artifacts it carries — invisible Unicode, non-breaking spaces, homoglyphs, harness-added provenance trailers, trailing chat closers — then flag the prose tells a script cannot catch, each quoted with a rewrite.

Edit this page on GitHub · View source