← Back to Skills Marketplace
sharbelayy

Job Hunter

by sharbel · GitHub ↗ · v1.0.0
cross-platform ⚠ suspicious
966
Downloads
2
Stars
7
Active Installs
1
Versions
Install in OpenClaw
/install job-hunter
Description
Assist with finding, evaluating, and applying to jobs using multi-source searches, fit scoring, application support, interview prep, and status tracking.
README (SKILL.md)

Job Hunter

End-to-end job search assistant — from finding opportunities to landing interviews.

Quick Start

1. Set up candidate profile

Create a profile JSON for the user. Use the template at {baseDir}/references/profile-template.json as a starting point. Ask the user about:

  • Target roles and seniority level
  • Key skills and tools
  • Location preferences (cities + remote)
  • Salary expectations
  • Dealbreakers and excluded companies
  • Preferred industries/domains

Save as profile.json in the workspace.

2. Search for jobs

Use the web_search tool with multiple queries to cast a wide net:

site:linkedin.com/jobs "[role]" "[city]"
site:indeed.com "[role]" "[city]"  
site:glassdoor.com/job "[role]" "[city]"
"[role]" "[city]" hiring 2025 2026

Expand keywords — don't just search one title. See {baseDir}/references/search-strategies.md for keyword expansion patterns.

Alternative: run the search script if Brave API is available:

{baseDir}/scripts/search_jobs.sh "CX Manager" --location "Amsterdam" --days 7

3. Evaluate fit

For each job found, run fit analysis:

python3 {baseDir}/scripts/analyze_fit.py --profile profile.json --jobs jobs.json --threshold 50

Or evaluate manually using this framework:

  • Skill match (40%): Does user have 60%+ of required skills?
  • Seniority match (25%): Right level — not over/under qualified?
  • Location match (15%): Compatible location or remote?
  • Domain match (10%): Preferred industry/domain?
  • Red flags (10%): Excluded companies? Dealbreakers?

Score: 🟢 75+ great | 🟡 55-74 good | 🟠 40-54 stretch | 🔴 \x3C40 skip

4. Present results

For each job, present:

  • Role & Company with direct link
  • Fit score with color indicator
  • Why it's a match (top 3 skill matches)
  • Gaps to address (missing skills to highlight as "eager to learn")
  • Salary estimate if available
  • Recommendation: Apply / Maybe / Skip

Application Support

Cover letters

Read {baseDir}/references/cover-letter-guide.md for structure and tone guidelines. Generate tailored cover letters that:

  • Reference specific company details (not generic)
  • Map user's experience to top 2-3 job requirements
  • Include quantified achievements
  • Stay under 350 words

Interview prep

Read {baseDir}/references/interview-prep.md for complete preparation framework. Help with:

  • Company research summaries
  • STAR stories for key requirements
  • Tailored "tell me about yourself" script
  • Salary negotiation talking points
  • Questions to ask the interviewer

Salary research

bash {baseDir}/scripts/salary_research.sh "Job Title" "Location"

Cross-reference 3+ sources. In the Netherlands: factor in 8% holiday allowance, possible 13th month, pension.

Daily Brief Format

When running as a scheduled job search brief:

  1. New opportunities — jobs found in last 24h with fit scores and direct links
  2. Application status — updates on pending applications
  3. Action items — what to apply to today, follow-ups due
  4. Market intel — industry trends, salary movements, hiring patterns

Tracking

Maintain a job tracker with:

  • Company, role, date found, source URL
  • Fit score and recommendation
  • Status: newappliedscreeninginterviewoffer/rejected/ghosted
  • Applied/skipped with reason
  • Contact info and follow-up dates

Tips for Agents

  • Never apply on behalf of the user — present opportunities, let them decide
  • Don't overwhelm — 3-5 quality matches beat 20 mediocre ones
  • Track excluded companies — never suggest the same company twice after rejection
  • Be honest about fit — stretches are okay to flag, but don't oversell poor matches
  • Respect dealbreakers — if user said no customer service, don't suggest it even if "it's a great company"
  • Update the profile — as you learn user preferences, refine the profile
  • Celebrate wins — applied to a job? Got an interview? Acknowledge it
Usage Guidance
This skill appears to implement a legitimate job-search assistant, but note these concerns before installing or running it: - The search script conditionally uses a BRAVE_API_KEY environment variable to call the Brave Search API, but the skill metadata does not declare this requirement. If you provide a Brave API key, the script will send queries and receive results from api.search.brave.com. - If you are security-conscious, do not place sensitive credentials (cloud credentials, company tokens, or personal API keys unrelated to Brave) in the same environment where this skill runs. Treat BRAVE_API_KEY like a secret: only provide it if you understand and trust the endpoint. - Consider running the included scripts manually in a sandboxed environment first (with a dummy BRAVE_API_KEY or without it) to inspect the network traffic and outputs. The skill will fall back to producing search queries for manual use if no BRAVE_API_KEY is present. - Ask the skill author to update the manifest to declare required env vars (BRAVE_API_KEY) and to document where network requests go and what data is transmitted. Also request explicit documentation about what the skill will send to external services and whether any logs or outputs could contain user profile data. - If you want to be extra cautious, disable autonomous invocation for this skill (or restrict when it can run) and only invoke it manually after reviewing inputs/outputs.
Capability Analysis
Type: OpenClaw Skill Name: job-hunter Version: 1.0.0 The skill bundle is classified as suspicious due to critical shell injection vulnerabilities found in `scripts/salary_research.sh` and `scripts/search_jobs.sh`. These scripts directly embed user-controlled input (e.g., job title, location) into shell commands without robust sanitization, potentially allowing an attacker to execute arbitrary commands if they can control the input provided to the agent. Additionally, `scripts/search_jobs.sh` performs external network calls to `https://api.search.brave.com` using an API key, which, while aligned with the stated purpose, represents a significant capability that could be misused if the underlying vulnerabilities were exploited.
Capability Assessment
Purpose & Capability
Name/description, SKILL.md, reference docs, and the three scripts are coherent: they focus on searching job boards, scoring fit, salary research, and generating application assets. The included scripts and templates are proportional to a job-hunter assistant. One capability (calling the Brave search API) is plausible for multi-source searching, but the skill metadata does not declare the associated credential.
Instruction Scope
SKILL.md instructs the agent to run local scripts and use web_search/web_fetch to query third-party job sites — expected for this purpose. However, the search script also reads BRAVE_API_KEY from the environment and will call https://api.search.brave.com when present; that environment dependency and outbound network calls are not declared in the skill metadata. The SKILL.md does not warn the user that an API key may be used or that network requests will be made to the Brave API.
Install Mechanism
Instruction-only skill with no install spec. No external archives or installers are fetched by the platform when installing the skill itself. The scripts require common tools (python3, curl) but those are expected and not installed by the skill.
Credentials
Declared requirements list no environment variables, but scripts reference an environment variable (BRAVE_API_KEY) to enable the Brave API search path. This is an undeclared credential requirement. Supplying such a token would expose it to the script and any tool that executes it; the skill does not request or document other credentials, which is inconsistent with the code.
Persistence & Privilege
The skill does not request permanent presence (always: false) and has no install-time hooks or config writes in the manifest. It performs network calls at runtime if executed, but it does not request elevated agent privileges or attempt to modify other skills/configs.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install job-hunter
  3. After installation, invoke the skill by name or use /job-hunter
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release: multi-source job search, fit scoring, interview prep, cover letter guide, salary research
Metadata
Slug job-hunter
Version 1.0.0
License
All-time Installs 7
Active Installs 7
Total Versions 1
Frequently Asked Questions

What is Job Hunter?

Assist with finding, evaluating, and applying to jobs using multi-source searches, fit scoring, application support, interview prep, and status tracking. It is an AI Agent Skill for Claude Code / OpenClaw, with 966 downloads so far.

How do I install Job Hunter?

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

Is Job Hunter free?

Yes, Job Hunter is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Job Hunter support?

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

Who created Job Hunter?

It is built and maintained by sharbel (@sharbelayy); the current version is v1.0.0.

💬 Comments