Get started · Privacy in 30 seconds · Safety · Privacy · Where to find it · Dashboard · Security
npx job-application-agent@latest install
npx skills add vaibhavarora14/job-application-agent
Job Application Agent is an Agent Skill that helps a coding agent discover, evaluate, complete, and track your own job applications. It uses one verified résumé, checks eligibility and duplicates, and records only confirmed submissions.
🔒 Privacy in 30 seconds
- OS credential store for profile
- One verified résumé; refuse unverifiable claims
- Never reads cookies/session files; pauses for SSO/MFA/CAPTCHA/legal
- Only records confirmed submissions (filled ≠ applied)
- Analytics/community sharing opt-out via CLI
🚀 Get started
Install it with either:
npx job-application-agent@latest install
npx skills add vaibhavarora14/job-application-agent
Then tell your coding agent:
Use job-application-agent to onboard my résumé and job preferences.
After onboarding, use natural commands:
search jobs
list discovery sources for India and global remote engineering
apply https://company.example/jobs/123
apply all relevant jobs from this thread: <URL>
run a round of 10
show attention queue
record outcome Company — Senior Engineer — interview
Requires Node.js 20 or newer and a browser-capable coding agent.
Use your preferred agent
Setup templates are available for Hermes Agent, Grok Bot, and OpenClaw:
npx job-application-agent@latest platforms
npx job-application-agent@latest platforms hermes
Replace hermes with grok or openclaw for that guide. These commands print
instructions only; they do not install a Bot, change agent settings, or access
candidate state. Browse the platform guides.
Each template starts in review mode and requires browser validation on its host.
The Grok Bot native share link is pending; use the setup prompt in the guide.
The existing installer also supports Codex, Claude Code, Cursor, Copilot, and
Gemini skill directories when present.
On Linux, profile storage uses the Secret Service via the secret-tool CLI. Install it with sudo apt-get install libsecret-tools (Debian/Ubuntu) or the equivalent package manager command for your distribution.
Unlike macOS Keychain or Windows Credential Manager, the Linux Secret Service has no always-running system daemon: a keyring daemon (GNOME Keyring, KWallet, or similar) must be running in the user session for secret-tool to store or read the profile. On a desktop login this is normally already the case; on headless servers, containers, or SSH-only sessions, start one explicitly (e.g. gnome-keyring-daemon --unlock --components=secrets) before first use.
For one person's agents across several trusted hosts, an optional private Cloudflare D1 backend with R2 (or a private Workers KV blob fallback) shares profile, résumé, application, outcome, round, answer, and attention state. Each host receives a separate revocable credential, and one renewable lease ensures only one host submits applications at a time. See CLOUD_STATE.md.
No comments yet.