local-first skill suite · 6 skills · 0 cloud accounts
Network Jobs turns your LinkedIn graph into a private job corpus. Your agent discovers openings at companies you know, ranks them against your preferences, and drafts forwardable warm intros — all on your machine.
npm i -g @hirefrank/network-jobs@latestnetwork-jobs setup --agent autoOne prompt carries the whole setup — install check included. Nothing to install first.
Your agent installs the CLI, links the skills, and walks the rest with you — profile, preferences, imports. Two minutes, once.
Works with Claude Code · Cursor · Codex · OpenCode · Muse · Pi · Gemini CLI · Hermes · Grok Bot
setup→ profile.json · preferences.jsonPrefs interview grounded in your background.
import→ companies.json · 87 companiesFree export becomes a graph, locally.
discover→ triage/careers-*/ · review meCareer pages staged for review. Always.
ingest→ corpus/ · totalJobs 5Your word turns listings into corpus.
intros→ search/intros.json · email draftRanked roles, forwarders, warm email.
Resume → profile + preferences interview: location, remote/hybrid, IC vs manager, former employers.
Connections ZIP → local company graph. No PII leaves the machine.
Model-driven career pages, JS boards via agent-browser. Stages, never ingests.
Promotes a confirmed batch into searchable shards. Only on your word.
Prefs-aware search with scores; semantic matching via embed-setup.
Forwardable warm intros through real mutuals. You send.
Import → discover → ingest → search → warm intro. Press play — timings compressed.
Reconstructed from real commands · timings compressed · nothing leaves ~/.network-jobs/
For install, update, doctor, and imports. Everything else lives in the agent.
Everything in ~/.network-jobs/ — connections, corpus, profile, prefs, resume. No hosted API exists.
Skills read local files. The only network calls are public career pages.
Stronger models discover better; mid-tier is plenty for search and intros.
Open source, local-free. Only your own agent's tokens cost anything.
~/.network-jobs/ and are never sent to a remote API.setup --agent auto links everything it detects, Muse included via the shared ~/.agents/skills.manifest.json persist between runs, so a background agent — Muse's persistent agents, say — resumes exactly where it left off. Nothing lives in a cloud queue that can time out.network-jobs import ~/Downloads/Connections.zip.npx --yes @hirefrank/network-jobs@latest setup --agent auto runs setup with no global install. The launcher still lands on ~/.local/bin, so the network-jobs command sticks around.