← Back to Skills Marketplace
meteoryf

AI Job Hunter Pro

by MeteorYF · GitHub ↗ · v1.3.0 · MIT-0
cross-platform ⚠ suspicious
373
Downloads
1
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install ai-job-hunter-pro
Description
AI-powered job search assistant with RAG-based resume-JD matching, automated application pipeline, and status tracking. Use when the user wants to search for...
README (SKILL.md)

AI Job Hunter Pro

Intelligent job search assistant with RAG-based semantic matching, automated applications, and data-driven tracking.

Setup (first-time only)

Run the setup script to install dependencies and initialize the vector database:

cd {SKILL_DIR}
pip install -r scripts/requirements.txt
python3 scripts/setup_rag.py --init

Then create your profile:

cp assets/profile_template.json ~/job_profile.json
# Edit ~/job_profile.json with your info

Import your resume (PDF or DOCX):

python3 scripts/rag_engine.py --import-resume ~/path/to/resume.pdf

Core Workflows

Workflow 1: Smart Job Search (RAG Matching)

When user says "find jobs for me" or "match my resume":

  1. Load user profile from ~/job_profile.json
  2. Run RAG matching engine:
    python3 {SKILL_DIR}/scripts/rag_engine.py \
      --mode search \
      --platforms linkedin,boss \
      --min-score 0.75 \
      --max-results 20
    
  3. Present results sorted by match score
  4. For each job, show: title, company, match score, top matching skills, missing skills
  5. Ask user which jobs to apply to, or auto-apply if configured

Workflow 2: Auto-Apply Pipeline

When user says "apply to these jobs" or "auto-apply":

  1. For each selected job:
    python3 {SKILL_DIR}/scripts/apply_pipeline.py \
      --job-id \x3Cid> \
      --mode dry-run \
      --generate-cover-letter \
      --optimize-ats
    
  2. In dry-run mode: show generated cover letter and ATS-optimized resume highlights for review
  3. After user confirms, switch to --mode submit
  4. Log result to tracker database

Workflow 3: Application Tracking

When user says "track my applications" or "job search report":

python3 {SKILL_DIR}/scripts/tracker.py --report daily

Status flow: Discovered → Applied → Screening → Interview → Offer / Rejected

Workflow 4: Feedback Loop

When user says "I like this job" or "not interested":

python3 {SKILL_DIR}/scripts/rag_engine.py \
  --mode feedback \
  --job-id \x3Cid> \
  --signal like|dislike

This adjusts the RAG query vectors to improve future recommendations.

Rules

  • Always start in dry-run mode. Never submit applications without explicit user confirmation.
  • Respect platform rate limits: max 20 applications per day across all platforms.
  • Never misrepresent the user's qualifications in cover letters or applications.
  • Store all data locally. Never send resume data to external services other than the job platforms themselves.
  • When a platform returns an error or blocks access, report it clearly and suggest manual fallback.
  • Always show the match score and reasoning before applying.

Configuration

User config lives at ~/job_profile.json. Skill config in OpenClaw:

{
  "skills": {
    "ai-job-hunter-pro": {
      "enabled": true,
      "profile_path": "~/job_profile.json",
      "default_platforms": ["linkedin", "boss"],
      "max_daily_applications": 20,
      "min_match_score": 0.75,
      "require_confirmation": true,
      "dry_run": true
    }
  }
}
Usage Guidance
Things to check before installing or enabling auto-apply: - Inspect scripts/requirements.txt and scripts/setup_rag.py to see exactly which Python packages and binaries will be installed (especially anything that talks to cloud APIs or downloads executables). If any packages call remote LLMs (openai, anthropic, google-cloud), confirm where API keys should go and whether data is sent off-host. - Open scripts/rag_engine.py and setup_rag.py and search for network calls or client libraries (openai, anthropic, google, requests, httpx). If the RAG flow uses remote LLMs/embedding APIs, expect to provide API keys and understand that resume text may be sent to those services — this would contradict the 'local-only' promise. - Confirm how browser sessions are handled for auto-apply: the code uses Playwright and will operate with your browser/session state. Understand that automation may use your logged-in accounts and cookies; this can trigger platform anti-bot defenses or account locks. - Keep the default dry-run and require_confirmation settings until you've manually reviewed outputs and test runs. Never enable automatic submit/auto_greet without testing in a controlled environment. - Note the dashboard pulls JS and fonts from CDNs (Chart.js, Google Fonts) which will cause your machine to make network requests to third-party providers when viewing the dashboard — consider hosting assets locally if you need full privacy. - If you need higher assurance, run the skill in an isolated environment (container or VM) and review network traffic during setup and first runs. If anything in rag_engine.py or other scripts references OPENAI_API_KEY / ANTHROPIC_API_KEY / GOOGLE_* or posts to non-job-platform endpoints, treat that as a red flag. If you can share the full contents of scripts/rag_engine.py, scripts/setup_rag.py, and scripts/requirements.txt I can give a higher-confidence verdict and point to any exact lines that contact external APIs or require secrets.
Capability Analysis
Type: OpenClaw Skill Name: ai-job-hunter-pro Version: 1.3.0 The skill bundle provides a comprehensive AI job search assistant that utilizes high-risk capabilities including automated web scraping via Playwright (job_scraper.py, company_scraper.py), sensitive file access for resume and profile management, and the execution of system binaries (pdftotext, pandoc) via subprocess calls in rag_engine.py. While these behaviors are plausibly aligned with the stated purpose of RAG-based job matching and application tracking, the broad network access and handling of personal data (stored in ~/job_profile.json) represent a significant attack surface. The 'auto-apply' feature in apply_pipeline.py is currently simulated, which mitigates immediate risk, but the overall privilege requirements and complexity justify a suspicious classification under the provided criteria.
Capability Assessment
Purpose & Capability
Name/description describe resume-to-job matching, auto-apply, and tracking, which aligns with the included scrapers, RAG engine, apply_pipeline, and tracker. However, the skill only declares 'python3' as a required binary while the code depends on Playwright/browser automation and Python packages (playwright, chromadb/embedding libs, etc.). The README and scripts reference browser automation/Playwright and LLM/tool names (Claude, Gemini, ChromaDB), but no corresponding environment variables or explicit install instructions for browser binaries are declared in the registry metadata — this mismatch is noteworthy.
Instruction Scope
SKILL.md instructs reading ~/job_profile.json and the user's resume and storing a local DB (~/.ai-job-hunter-pro), which is expected. The skill promises to 'store all data locally' and 'never send resume data to external services other than the job platforms themselves', but the codebase contains a RAG engine and references to external LLMs and CDNs. Without inspecting rag_engine.py and setup_rag.py in full, it's unclear whether embeddings or LLM calls are local (sentence-transformers + Chroma) or call remote APIs (OpenAI/Anthropic/Google). The dashboard.html loads Chart.js and Google Fonts from CDNs (network calls) and the auto-apply pipeline performs browser automation using user sessions (which implies it may access browser cookies/sessions). The instructions correctly enforce dry-run by default, but they give the agent wide discretion to scrape many sites and perform automated submissions once configured — that level of access should be confirmed.
Install Mechanism
The skill is instruction-only (no registry install spec), which reduces installer-level risk. Setup instructions ask the user to pip install -r scripts/requirements.txt and run setup_rag.py --init. The code clearly depends on Playwright and browser binaries; one scraper prints a message asking the user to run 'playwright install chromium' if Playwright is not installed. There is no download-from-arbitrary-URL or extraction step in the registry metadata, but users must run pip and browser installs themselves — verify the requirements.txt and setup_rag.py before executing to see what packages/binaries will be installed.
Credentials
Registry metadata lists no required environment variables or primary credential, yet the codebase references model/LLM names (Claude, Gemini, OpenAI-like tokens in README and HIGHLIGHT_MAP strings) and platform integrations that commonly require credentials or sessions (LinkedIn, Boss直聘, Indeed). The skill will need browser sessions or API keys to submit applications; these are not declared. There is also a 'report_channel': 'whatsapp' present in the profile template suggesting possible external reporting channels, but no env vars or code shown for WhatsApp integration. The absence of declared credentials is inconsistent and should be clarified.
Persistence & Privilege
The skill does create persistent local state (profile at ~/job_profile.json and a SQLite DB at ~/.ai-job-hunter-pro/applications.db) which is consistent with its purpose. always is false and disable-model-invocation is default; the skill does not request elevated system-wide privileges. It stores data under the user's home directory rather than system locations, which is proportionate for this functionality.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install ai-job-hunter-pro
  3. After installation, invoke the skill by name or use /ai-job-hunter-pro
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.3.0
ai-job-hunter-pro 1.3.0 introduces new scraping and dashboard capabilities. - Added company and job scraping scripts for enhanced job data collection. - Introduced a dashboard HTML interface. - Updated RAG engine script to support new data inputs and workflows.
v1.0.0
AI Job Hunter Pro v1.0.0 — Initial release - Introduces RAG-based job-resume matching for intelligent job search. - Automates application workflows including tailored cover letter generation and ATS optimization, always starting in dry-run for user review. - Tracks application status through all job search stages, with daily reporting. - Enables interactive feedback to refine future job recommendations. - Stores all user data locally for privacy; honors platform rate limits and never submits applications without confirmation.
Metadata
Slug ai-job-hunter-pro
Version 1.3.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 2
Frequently Asked Questions

What is AI Job Hunter Pro?

AI-powered job search assistant with RAG-based resume-JD matching, automated application pipeline, and status tracking. Use when the user wants to search for... It is an AI Agent Skill for Claude Code / OpenClaw, with 373 downloads so far.

How do I install AI Job Hunter Pro?

Run "/install ai-job-hunter-pro" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is AI Job Hunter Pro free?

Yes, AI Job Hunter Pro is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does AI Job Hunter Pro support?

AI Job Hunter Pro is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created AI Job Hunter Pro?

It is built and maintained by MeteorYF (@meteoryf); the current version is v1.3.0.

💬 Comments