# Omh AI Job Search

[omh] Career search to interview: find verified opportunities, tailor evidence-grounded...

- Repository: https://github.com/rlaope/oh-my-hermes (5004 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add rlaope/oh-my-hermes --skill omh-ai-job-search -g -a claude-code -y`
Codex: `npx skills add rlaope/oh-my-hermes --skill omh-ai-job-search -g -a codex -y`
Cursor: `npx skills add rlaope/oh-my-hermes --skill omh-ai-job-search -g -a cursor -y`
Gemini CLI: `npx skills add rlaope/oh-my-hermes --skill omh-ai-job-search -g -a gemini-cli -y`

## Description

[omh] Career search to interview: find verified opportunities, tailor evidence-grounded applications and track confirmed outcomes. Use when the user says: ai-job-search, job search, evaluate this job posting, tailor my resume, tailor my cv, prepare for my job interview, track my job applications, draft my cover letter.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Ai Job Search

This is an OMH `ai-job-search` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

## Why This Exists

Cross-session career work needs stable posting identity, candidate-evidence links and a strict boundary between prepared applications and confirmed events.

## First Steps

- Read `toolkit/README.md` and `references/execution-and-qa.md`; load only the relevant profile/discovery, fit/drafting or interview/outcomes reference for the current action.
- Confirm an approved private workspace outside the product checkout through the active profile; ask only action-specific questions and keep group replies public-safe.
- Actually invoke `toolkit/scripts/job_state.py` through the host terminal: validate captures, merge approved local tracking input, then summary and read-back; produce requested documents rather than stopping at a prepared card.

## Do Not Use When

- For employer-side hiring and candidate assessment, use `omh-people-ops`.
- For background task scheduling or service repair, use the existing automation or debugging owner.
- For repository symbol lookup or implementation work, use the selected coding owner.

## Examples

Good example:

- Prompt: Find library coordinator opportunities and tailor my supported experience to a selected posting.
- Expected behavior: Capture verified sources, preserve unknown constraints, draft evidence-mapped documents and review them privately.
- Why: Career evidence and application state need a coherent method.

Bad example:

- Prompt: Debug a failed cron job in the application server.
- Expected behavior: Use the debugging owner; do not collect career facts.
- Why: Generic task vocabulary does not establish a career request.

## Completion Checklist

The rest: https://github.com/rlaope/oh-my-hermes/blob/HEAD/agent-skills/omh-ai-job-search/SKILL.md