Omh AI Job Search
[omh] Career search to interview: find verified opportunities, tailor evidence-grounded...
Install
npx skills add rlaope/oh-my-hermes --skill omh-ai-job-search -g -a claude-code -y- Repository
- rlaope/oh-my-hermes5k
- Category
- Engineering
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 1,611 tokens
- Runs scripts
- Yes, review before use
What it does
[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.
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.mdandreferences/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.pythrough 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.
