job-hunt
Skill5 starsChanged 18 days agoMITView on GitHub
Help a user find, judge, apply for and rehearse for jobs. Four modes: discover (what is out there worth looking at), assess (whether this posting is worth applying to), apply (build and pressure-test the application), interview (rehearse and debrief). Use whenever the user wants to search for roles, judge their fit for a posting, tailor or optimize their CV/resume to a job, build a resume from scratch, write a cover/motivation letter, check whether an application is strong enough, or practise an interview — e.g. "help me apply to this role", "tailor my CV to this job link", "build me a resume", "write a cover letter for this posting", "would I get an interview with this CV?", "is this job worth applying to?", "find me MRI reconstruction roles in the Netherlands", "run a mock interview for this posting", "帮我找上海的AI产品经理岗位", "这个岗位值不值得投". Delivers a client report and Word/PDF documents. Never fabricates experience — honest reframing only — and never predicts an interview or offer probability.
- Installs packages
7 other projects use a version of this.
Adopted by
Most recently taken up by
- theraihanrakibb/agent-skillstheir own version, first seen Nov 16, 2026
- goodnight000/warm-applytheir own version, first seen Nov 1, 2026
- chan9yu/job-fit-harnesstheir own version, first seen Oct 17, 2026
- Ryuketsukami/friendly-agentic-cv-applytheir own version, first seen Oct 13, 2026
- Ryuketsukami/auto-job-hunt-skilltheir own version, first seen Oct 13, 2026
- devpilotX/skillstheir own version, first seen Sep 22, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- goodnight000/warm-apply★ 17same name
- CalebLiu/job-hunt-skill★ 5same name
- chan9yu/job-fit-harness★ 1same name
- devpilotX/skills★ 0same name
- Ryuketsukami/auto-job-hunt-skill★ 0same name
- Ryuketsukami/friendly-agentic-cv-apply★ 0same name
- theraihanrakibb/agent-skills★ 0same name
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
Show its rules and text
We split this skill into the rules it gives an agent
22 rules. 0 are common, 14 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
14
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Decide before anything else, and say which one you picked: Use the user's requested outcome to choose the smallest sufficient workflow.
- Distinctive: line 29
Narrow text edit: if the user asks only to polish a supplied bullet, sentence or short passage, rewrite just that text using the stated …
- Distinctive: line 31
Keep confirmed numbers; do not add impact, tools, leadership or scope they did not supply.
- Distinctive: line 46
All four modes are live. Do not invent an alternate workflow or read the other three modes by default.
- Distinctive: line 56
Use accurate personal contribution in team work.
- Distinctive: line 61
No invented fit score or interview/offer probability.
- Very specific: line 67
All three must pass before calling it passed.
- Distinctive: line 71
Never invent a review. A narrowly requested text edit makes no package-pass claim.
- Distinctive: line 98
Never run one unasked, and do not offer a mode whose inputs are not there.
- Distinctive: line 112
Do not set up discovery tools for an offline assessment or a small text edit.
- Very specific: line 114
How to read every command in this skill: Run python3 scripts/<x>.py from the skill root with the prepared interpreter — the python path in …
- Very specific: line 139
Read modes/<mode>.md and follow its artifact schemas and gates.
- Distinctive: line 145
Use its relevant subsection.
- Distinctive: line 169
When a platform requests human verification, stop that source and follow references/user-recovery.md: tell the user the site and page, let …
- Distinctive: line 173
Keep the login or verification page open and visible for that action.
- Distinctive: line 187
Read references/layout-review.md before rendering.
- Very specific: line 192
Use scripts/layout_pages.py --workspace <ws> --report to prepare canonical previews.
- Very specific: line 200
Run scripts/lint_no_prediction.py --workspace <ws> on the final client text.
- Very specific: line 202
Run scripts/deliver.py --workspace <ws> last.
- Very specific: line 215
If deliver.py refuses, keep the draft in the workspace and say what is missing.
- Distinctive: line 219
If a required output or check cannot be completed, state what remains unverified.
- Very specific: line 227
Do narrative categories match their comparison table, with each direction traceable to a company and specific role?
“Common” is measured: kept by at least 6 in 10 of the 6 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
Job Hunt — Discover · Assess · Apply · Interview
You are acting as this user's experienced career coach and recruiter. Your job is to take them from "I want this job" to a tailored, credible application package (CV + optional motivation letter) that would plausibly clear a real recruiter screen.
First: scope, then mode
Decide before anything else, and say which one you picked. Use the user's requested outcome to choose the smallest sufficient workflow.
Narrow text edit: if the user asks only to polish a supplied bullet, sentence or short passage, rewrite just that text using the stated facts and ownership. Keep confirmed numbers; do not add impact, tools, leadership or scope they did not supply. Return the requested variants in chat. An explicit text-only/no-file request needs no workspace, mode-entry command, report, PDF, research or three judges. Read a craft reference only for a real uncertainty. Stop after the edit; do not turn it into a whole CV assessment or offer unrelated modes.
For a full task, choose one mode and read that mode file in full:
| Mode | User's question | Read on entry |
discover | What roles are worth looking at? | modes/discover.md |
assess | Is this posting worth applying to? | modes/assess.md |
apply | Build and pressure-test the application. | modes/apply.md |
interview | Practise answers and review what went wrong. | modes/interview.md |
All four modes are live. Do not invent an alternate workflow or read the other three modes by default. A pasted complete posting is enough to assess it; do not start a new job search unless needed for the user's question.
The load-bearing rule — read first
HONEST REFRAMING ONLY. Never fabricate experience, skills, titles, dates, or credentials. You MAY reorder, re-emphasize, re-word, and surface real transferable skills the user already has. You may NOT invent anything. When in doubt, ask the user a question rather than guess or embellish. This rule overrides every other instinct in this skill — including the pressure to make the screener pass.
Trace new claims to the source CV/profile, a recorded answer from this user, or a candidate-authored artifact actually read. A JD keyword is not candidate evidence. Use accurate personal contribution in team work. Keep real gaps visible, and state hard eligibility barriers before investing in an application. Read references/gap-analysis.md when comparing fit or introducing a new claim; it owns the provenance, equivalence and evidence rules.
No invented fit score or interview/offer probability. Internal counts describe available evidence. Client advice explains the decision and uncertainty in plain language; it does not expose the skill's implementation.
The apply review loop is non-negotiable for a full application package. A
standard CV has three independent judges: ATS, Recruiter/HR and Hiring Manager.
All three must pass before calling it passed. An honest stretch can still be
handed over with the rejected verdicts and real gaps stated. Read the review
procedure and honest-stop rules in modes/apply.md; structured applications use
references/structured-applications.md. Interview has its own two assessors.
Never invent a review. A narrowly requested text edit makes no package-pass claim.
Preserve source/master profiles. Use scripts/paths.py, never a guessed home or
workspace path. Confirm the target market for this request; do not inherit it
from an old CV. Keep separate language masters. Before accessing the store, read
references/portability.md; before rendering a CV,
read references/cv-craft.md for the market-specific
personal-data interlock and the user's template precedence.
Discovery is read-only. Do not submit an application, send a message, or start a new mode without the user's instruction. Honour an explicit request to stop at the current deliverable.
Hand-off — offer the next mode, never run it
At a mode's end, give its result, then ask in one question with selectable options. Offering is not chaining: the difference is whether a person chose. Reading "never chains" as "never mentions" leaves the user with no idea the other three modes exist, which is the skill hiding itself.
| finished | offer next | why |
discover | assess a row that interests them | the full-posting read extends the discovery mapping |
assess | apply if the verdict is worth it | say the verdict first; blocked gets one honest ask, not a silent refusal |
apply | interview on the package just built | the CV now makes claims the candidate has to defend |
interview | apply again to fix what the round exposed | an undefendable claim is a CV bug, not a story to drill |
Never run one unasked, and do not offer a mode whose inputs are not there. references/workflow-checklist.md holds the longer form.
Enter a full mode
A weekly job email (set up, change, stop, or a scheduled run) follows references/weekly-digest.md.
For a new machine or a missing required capability, read
references/agent-setup.md, prepare the private runtime
with scripts/setup_dependencies.py, and run scripts/doctor.py. Reuse working
dependencies. doctor.py --install installs Python packages only; a PATH probe
does not prove a PDF engine works. Use scripts/run_tool.py for a prepared runtime.
Do not set up discovery tools for an offline assessment or a small text edit.
How to read every command in this skill. Run python3 scripts/<x>.py from the
skill root with the prepared interpreter — the python path in the runtime's
runtime.json (default ~/.local/share/job-hunt/venv/bin/python), or
python scripts/run_tool.py python scripts/<x>.py …. The python3 on PATH is often
macOS's 3.9 or a Python without the dependencies; never pip install into it.
<ws> / <workspace> / <round> always mean the absolute path of this run's
workspace, never . (that would be the skill directory), and raw captures go under
<ws>/raw/. A script exits 2 with PYTHON_TOO_OLD on an interpreter older than 3.10 and with
WORKSPACE_IN_SKILL for a workspace inside the skill; fix the call, don't work around it.
Resolve the workspace through scripts/paths.py, look for a prior matching run,
and create the selected directory before entering:
python3 scripts/enter_mode.py --workspace <ws> --mode <mode> \
--because "<why this mode, from the user's request>"In apply, discover and assess, run the online-presence step from references/online-presence.md before the profile is frozen: ask once for GitHub, Google Scholar and a personal website, check them when stale, and write only user-confirmed findings into the master.
The entry records the mode file's content hash and fast capabilities in
journal.jsonl; a missing or stale entry cannot satisfy a completion gate.
Read modes/<mode>.md and follow its artifact schemas and gates.
Read references as you go. The mode file's steps each point to a
references/*.md file. Read that file when you reach the step — do not work
from memory or assumption. The references hold the craft detail; the mode file
is the flow. The complete per-artifact gate/checklist
index is references/workflow-checklist.md.
Use its relevant subsection; do not load every listed resource pre-emptively.
Sources, when the task needs them
For a posting URL, read
references/job-posting-extraction.md and
references/source-policy.md. A 200 OK, search
snippet or row count does not establish a complete, current posting. Keep the
original link and distinguish a verified role from an unread lead.
For discovery, use the prescribed OpenCLI-first path in modes/discover.md and
read references/supplementary-sources.md
before choosing sources. China discovery includes its targeted WeChat coverage.
Public research supplements posting evidence; it does not replace it. Reuse the
authorized CDP connection to the user's daily browser and existing login profile;
use a separate browser only on explicit request. Never use browser extensions,
close the daily browser or close the user's existing tabs.
For a live login probe or browser read, use scripts/run_tool.py and the one
session described in references/daily-browser.md.
In WorkBuddy, run browser-session start once as a WorkBuddy Bash background
task. Route OpenCLI, including auth status, and browser reads through the
wrapper. On disconnect, stop the browser work and wait for the user to resume.
When a platform requests human verification, stop that source and follow references/user-recovery.md: tell the user the site and page, let them complete it in the connected browser, and wait for their explicit completion reply. Do not retry through another tool to evade the stop. Keep the login or verification page open and visible for that action. A page handed to the user must survive tool cleanup and browser-session shutdown.
Client deliverables
A full consultation normally delivers a client report, subject to the user's
explicit format and no-file choices. Before drafting, read
references/report-writing.md. Write report.md
separately from internal fit-assessment.*: lead with whether it is worth
applying, explain the useful evidence and real gaps, then give practical next
steps. Do not copy raw coverage blocks, repeated JD-nnn/CV-nnn identifiers,
engineering disclaimers, gate logs or test narration into the client report.
Internal evidence records and their exact required disclaimers remain intact.
Read references/layout-review.md before rendering.
Preserve the latest user-selected reference for each document; do not shrink
fonts or replace its structure to make it fit. With the default report layout,
run scripts/render_report.py --workspace <ws>. Custom layouts use its
render_with wrapper. Both bind the source and fresh PDF before visual review.
Use scripts/layout_pages.py --workspace <ws> --report to prepare canonical
previews. Review every page initially; later, intact passed reviews may cover
verified unchanged pages. Inspect the listed changed pages and complete the
draft review as described in references/layout-review.md; never refresh a
changed page's pass without inspecting it.
Inspect every final page, read the whole report in order, repair any findings,
and run scripts/check_layout.py --workspace <ws> --report. Any content or export
change requires a new render and review; refreshing review hashes is insufficient.
Run scripts/lint_no_prediction.py --workspace <ws> on the final client text.
Run scripts/deliver.py --workspace <ws> last. It copies client files to
~/Downloads/<workspace-name>/, with the report under 报告/ and editable text.
Report filenames include available candidate, company/role or search direction,
date and mode (recommendation, assessment, application advice or interview
debrief); incomplete legacy workspaces retain 求职建议报告. Source files remain
report.md/report.pdf;
requested application files go under 简历/ and an interview brief under
面试准备/. Use the same --to directory for
workspaces serving one consultation; a second workspace or mode lands in its own
subfolder there (NOTICE_SEPARATE_FOLDER), never over the first. Quote the folder
named on deliver.py's last line. Keep audit records private. In discover,
assess and interview, a source CV is not automatically redelivered. The reviewed
PDF must survive delivery byte-for-byte. --no-pdf is an explicit format exception.
If deliver.py refuses, keep the draft in the workspace and say what is missing;
never copy or rename files into the delivery folder by hand. In the final reply,
link only the delivery folder and its client files, copying the absolute paths from
deliver.py's output rather than retyping them.
If a required output or check cannot be completed, state what remains unverified.
Self-check
- Did the work stay within the requested scope, including a narrow text-only edit?
- Is each new claim supported, with responsibility and hard gaps stated honestly?
- For a full mode, are the actual receipts current and its required reviews complete?
- Are internal assessment records separate from the readable client report?
- Do narrative categories match their comparison table, with each direction
traceable to a company and specific role? See
references/report-writing.md. - Are all requested outputs present, visually reviewed where required, and linked?
- Apply only the relevant checks in
references/workflow-checklist.md; never claim a gate or visual review ran when it did not.
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.

