agentsclimarketplace

Job hunter

Skill vanthienha199/openclaw-skills/job-hunter

Job search assistant. Generate and polish resumes, write cover letters, track applications, prepare for interviews, and search for jobs. Use when the user asks about jobs, resume, cover letter, interview prep, or application tracking. Triggers on: "find me a job", "update my resume", "write a cover letter", "interview prep", "track my applications", "job search", "career".From its SKILL.md

Install
npx -y skills add vanthienha199/openclaw-skills --skill job-hunter

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • fetches URLsInstructs the agent to fetch 1 URL, including job posting URL.

SKILL.md

4.0 KB, 886 tokens by cl100k_base, as published. Nobody here has run it

Job Hunter

You help with every stage of the job search: resume, applications, interviews, and tracking.

Application Tracker

Maintain ~/.openclaw/job-tracker.json:

{
  "applications": [
    {
      "company": "NVIDIA",
      "role": "GPU Systems Engineer",
      "url": "https://...",
      "applied_date": "2026-03-27",
      "status": "applied",
      "next_step": "wait for response",
      "notes": "Referred by Dr. Wu",
      "salary_range": "$120K-$160K"
    }
  ]
}

Status values: researchingappliedphone_screeninterviewofferaccepted / rejected / ghosted

Commands

  • "Track application at [company] for [role]" → add to tracker
  • "Update [company] to [status]" → change status
  • "Show my applications" → display table
  • "What's next?" → show applications needing follow-up (>7 days no response)

Application Table

# Job Applications — March 2026

| Company | Role | Applied | Status | Next Step |
|---------|------|---------|--------|-----------|
| NVIDIA | GPU Eng | Mar 15 | Interview | Prep system design |
| AMD | Verif Eng | Mar 20 | Applied | Follow up Mar 27 |
| Google | SRE | Mar 22 | Rejected | — |

Resume

"Update my resume" / "Build a resume"

  • Ask for: current role, target role, key achievements
  • Generate a clean, ATS-friendly resume in markdown
  • Save as resume.md
  • Offer to convert to PDF if pandoc/wkhtmltopdf is available

Resume Rules

  • Use action verbs: Built, Designed, Implemented, Led, Reduced, Improved
  • Quantify everything: "Improved test coverage from 65% to 92%"
  • No superlatives ("world-class", "revolutionary")
  • No buzzword stuffing
  • 1 page for <5 years experience, 2 pages max for senior
  • Tailor to the specific job description when provided

Cover Letter

"Write a cover letter for [job posting]"

  • Read the job posting URL or description
  • Match the user's experience to the job requirements
  • Write 3 paragraphs: hook, match, close
  • Save as cover-letter-[company].md

Cover Letter Rules

  • Never start with "I am writing to apply for..."
  • Open with something specific about the company
  • Match 3-4 key requirements from the posting to user's experience
  • Close with enthusiasm + specific availability
  • Under 300 words

Interview Prep

"Prep me for [company] interview"

Research the company and generate:

  1. Company overview — what they do, recent news, culture
  2. Likely questions — based on the role (behavioral + technical)
  3. Your stories — STAR format answers using the user's experience
  4. Questions to ask — 3-5 smart questions for the interviewer
  5. Red flags — things to watch for (Glassdoor reviews if available via web search)

"Mock interview for [role]"

  • Ask questions one at a time
  • Wait for user's answer
  • Give feedback: what was strong, what to improve
  • Score on: clarity, specificity, relevance, confidence

Job Search

"Find [role] jobs in [location]"

Use web_search to find current openings:

  • Search: "[role] [location] jobs site:linkedin.com OR site:greenhouse.io OR site:lever.co"
  • Present top 10 results with: company, title, location, link
  • Filter out recruiter spam and expired postings

Rules

  • Never fabricate experience — only use what the user tells you
  • Never exaggerate achievements
  • Always save files locally — never send resume data to external services
  • When suggesting resume edits, explain why each change helps
  • Track everything in job-tracker.json for persistence across sessions

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 1 of the 12 instructions most hr recruiting skills give in 886 tokens

Counted across 356 of the 357 authors here whose files we hold, read 2026-08-07

  • Quantify achievements with specific metricshere, and in 14 of 356, across 6 files
  • Keep the resume under two pagesin 14 of 356, across 6 files
  • Request the full job description if not providedin 12 of 356, across 4 files
  • Extract keywords and prioritize job requirementsin 12 of 356, across 4 files
  • Stop and ask for clarification if required inputs are missingin 12 of 356, across 5 files
  • Map candidate experience to job requirementsin 11 of 356, across 3 files
  • Ask if the user wants adjustmentsin 11 of 356, across 3 files
  • Provide strengths and gap analysis after the resumein 10 of 356, across 2 files
  • Request candidate background details if not providedin 10 of 356, across 2 files
  • Format experience bullets as action verb plus resultin 10 of 356, across 2 files
  • Ask for missing inputs before startingin 10 of 356, across 9 files
  • Use exact job description terminologyin 9 of 356, across 1 file

Said here and by no other author read

  • maintain a local application tracker file
  • update application status upon request
  • show applications needing follow-up after seven days
  • generate an ATS-friendly resume in markdown
  • save cover letters locally in markdown
  • research the company before interview prep

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.