apply
Skill3 starsChanged 53 days agoMITView on GitHub
Use this skill when the candidate wants to apply to a role or produce application materials — e.g. "tailor my resume for Writer", "write the cover letter", "answer these application questions", "open the application and fill it in", "apply to this one", "prepare applications for my top 3". Produces JD-tailored résumés, cover letters, and application answers; can read, fill, and (with the candidate's go) submit the live application form in the browser.
25 other projects use a version of this.
Adopted by
Most recently taken up by
- priyansh1210/shirotheir own version, first seen Nov 8, 2026
- matthewwong525/WongStacktheir own version, first seen Nov 8, 2026
- galiprandi/job-seekertheir own version, first seen Nov 5, 2026
- hiddenjobs/job-search-mcptheir own version, first seen Nov 1, 2026
- ChadPapineau/espn-fantasy-football-mcptheir own version, first seen Nov 1, 2026
- ankul5/internship-hunt-skilltheir own version, first seen Nov 1, 2026
Used with
Projects with it also use track, hunt and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
theYahiaSkilltrack
Отследить посылку Почты России
Also in 4 projects that use this
ninehillsSkillhunt
Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code review or new features.
Also in 3 projects that use this
kstonekuanSkillDaily
Documentation and capabilities reference for Daily
Also in 3 projects that use this
genomewalkerSkillexplore
RLM-style recursive memory exploration - dynamically navigate the memory graph
Also in 4 projects that use this
AnthropicSkillinterview-prep
Create structured interview plans with competency-based questions and scorecards. Trigger with "interview plan for", "interview questions for", "how should we interview", "scorecard for", or when the user is preparing to interview candidates.
Also in 3 projects that use this
Google CloudSkilltriage
Gather context on a change or bug and plan the implementation.
Also in 4 projects that use this
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 25
- andrew-shwetzer/career-ops-plugin★ 501same name
- andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-★ 500same name
- proficientlyjobs/proficiently-claude-skills★ 389same name
- galiprandi/job-seeker★ 120same name
- hiddenjobs/job-search-mcp★ 25same name
- 1carusalwayswa/apply★ 18same name
- kirkchen/beat★ 9same name
- iliasedelkin/jobissimo★ 8same name
- matthewwong525/WongStack★ 7same name
- qbeka/jev-job-search★ 5same name
15 more not listed
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.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 36
Each round: Read ## Standard and earlier ## Rounds rows first.
- Very specific: line 49
Exits: All answers in ## Answers with gaps flagged.
- Very specific: line 66
Ensure each job has an evaluate decode.
- Very specific: line 75
Session close: Run node scripts/check_materials.mjs, node scripts/proposal_block.mjs, and node ../profile/scripts/check_files.mjs …
- Distinctive: line 79
Reshape-only, never invent: No claim the base doesn't support.
- Distinctive: line 80
Never: Create accounts, handle passwords, bypass CAPTCHAs, guess screening answers, or claim "submitted" without captured confirmation.
“Common” is measured: kept by at least 6 in 10 of the 24 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
Apply — job-scoped application materials, end to end
Goal
A submitted application the candidate is proud of. An application ships THREE artifacts: tailored résumé (+ ATS PDF), cover letter, and outreach plan (contacts/<company>.md with recruiter/HM message drafts). A cold submit without outreach is half an application.
| Must be true | Where |
| Tailored résumé is reshape-only from base, with ATS PDF measured against page target | applications/<key>-resume.md + PDF |
| Cover letter argues one clear thesis in candidate's voice | applications/<key>-cover-letter.md |
| Decisions disclosed beside delivered doc (cuts, placed words, gaps) | applications/<key>-application.md · chat |
| Deterministic checks pass, and all three panel lenses Pass or are waived in chat, before the package is called ready | reply outcomes, never narration |
| Nothing submitted without explicit candidate go and captured confirmation | ## Submission · jobs.md at Applied |
| Outreach plan exists with findable leads or honest "none findable" | ## Outreach plan · contacts/<company>.md |
Prerequisites
- Required: Workspace
CLAUDE.md(none: route to profile's Setup);base-resume.md(SSOT: body + § Claim rules — hard stop if absent, never fabricate);jd-analysis/for the role (suggestevaluatefirst if absent). - Optional:
profile.md(+§ Application defaults),storybank.md,pitch.md,voice.md.
Loops and sequences
Extended craft and form automation in references/patterns.md. File shapes in references/schema.md.
Tailoring (the loop)
Runs when the candidate asks to tailor a résumé, letter, or "materials" for a specific role.
- Standard: The
## Standardbullets in the application file (references/schema.md). - Budget: Two self-passes; one review incorporation round, which re-checks only the lenses short of Pass, once. Said up front.
- Each round: Read
## Standardand earlier## Roundsrows first. Reshape-only frombase-resume.md(selection, order, depth — never invented facts). Run the checks and the three-lens panel (references/eval.md § The panel — three lenses). Score round asN/M heldcount and append row to## Rounds. - Obligations:
- Facts need a yes: Voluntarily surfaced facts go to
storybank.md, not directly into a résumé without an explicit yes. - Deliver & Disclose: Present the deliverable beside the proposal block (
scripts/proposal_block.mjslist of cuts and placed words with easy reversal). - Exact edits: Apply candidate edits directly in place and re-render.
- Facts need a yes: Voluntarily surfaced facts go to
- Exits: When the round scores M/M held with every lens at Pass and the candidate accepts; at the budget; or at the ceiling: two
## Roundsrows with the same count and lens verdicts. At the budget or the ceiling, stop and present a decision for the candidate to make, showing each lens still at Revise or Fail with its## Panelrows; the package is not ready until every lens passes or the candidate waives it in chat. Never relax the standard — cutting a claim's supporting evidence to fit a limit IS relaxing it: a claim-name without its number is not the claim.
Answers (the loop)
Runs when application questions or form fields need drafting. Follow references/patterns.md § Application answers and voice.md.
- Standard: Answer addresses the exact prompt within word limits; CONFIRMED stories only.
- Budget: 2 rounds; ceiling applies.
- Exits: All answers in
## Answerswith gaps flagged; or at the ceiling with tradeoff surfaced. Never relax the standard — cutting a claim's supporting evidence to fit a limit IS relaxing it: a claim-name without its number is not the claim.
Full application (a sequence)
Runs when candidate says "apply to this one".
- Extract & Draft: Extract all form fields/pages into the application file before drafting essays. Screening answers pull from
profile.md § Application defaults. - Review Gate: Complete application (fields, essays, chosen résumé) approved in chat before touching the live form, with any LinkedIn drift named.
- Submit Gate (Rule 7): Form filled in the browser, then a screenshot and a plain summary, then the candidate's explicit word fires submit.
- Third Artifact: Capture submission confirmation into
## Submission, setjobs.mdrow to Applied, and draft the outreach plan incontacts/<company>.md(## Outreach plan).
Exits with all three artifacts delivered or at the gate candidate declined.
Batch prep (a sequence)
Runs when "prepare top N" (default N ≤ 5). User-armed, never scheduled.
- Ensure each job has an
evaluatedecode; run the tailoring loop for résumé/letter; draft form questions; build outreach plans. Never auto-submit in batch.
Exits with one status line per job.
State
Owned: applications/ (shapes in references/schema.md).
- Hands back: Outreach sends go to
outreach; interview prep goes tointerview; confirmed story leads go tostorybank; base updates go toprofile. - Session close: Run
node scripts/check_materials.mjs,node scripts/proposal_block.mjs, andnode ../profile/scripts/check_files.mjs --workspace .. Wording check subagent runs on every delivered document. Report outcomes, never narration (clean is 1 line, and only when nothing failed or warned; fix FAILs before the reply ends; fix each WARN or tell it to the candidate).
Guardrails
- Reshape-only, never invent: No claim the base doesn't support. Unsupported sections are omitted, never filled with filler.
- Never: Create accounts, handle passwords, bypass CAPTCHAs, guess screening answers, or claim "submitted" without captured confirmation.
Every reply ends with ONE contextual next step — a sentence with its why, not a menu.
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.

