agentleFS
Sign inStart free
hirefrankhirefrank/network-jobs/AGENTS.md

network-jobs

AGENTS.md0 starsChanged 3 months agoMITView on GitHub

  • Installs packages
  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,542 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository7 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Prefer a public, installable multi-agent skill suite (gstack/Keep-style CLI) over Claude-only or private-only packaging.

    line 3
  2. Distinctive:

    Prefer ATS-agnostic, model-driven career-page discovery and parsing rather than hard-coded ATS adapters.

    line 4
  3. Distinctive:

    Do not commit real LinkedIn connection dumps or other personal network PII.

    line 6
  4. Very specific:

    Prefer quiet CLI output by default.

    line 7
  5. Very specific:

    Prefer setup to install agent-browser when missing rather than leaving it optional-only.

    line 8
  6. Distinctive:

    Prefer automatic skill/routing install over asking users to paste AGENTS.md or CLAUDE.md snippets.

    line 9
  7. Very specific:

    Prefer setup to leave network-jobs on PATH (e.g.

    line 10
  8. Very specific:

    Do not surface the deprecated hosted product (jobs.hirefrank.com) in skill-suite setup or docs.

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Learned User Preferences

  • Prefer a public, installable multi-agent skill suite (gstack/Keep-style CLI) over Claude-only or private-only packaging.
  • Prefer ATS-agnostic, model-driven career-page discovery and parsing rather than hard-coded ATS adapters.
  • Day-to-day use should be in the agent after one-time CLI setup; keep the CLI for setup, doctor, and optional import.
  • Do not commit real LinkedIn connection dumps or other personal network PII; keep only synthetic fixtures in-repo.
  • Prefer quiet CLI output by default; put detail behind a -v / verbose flag.
  • Prefer setup to install agent-browser when missing rather than leaving it optional-only.
  • Prefer automatic skill/routing install over asking users to paste AGENTS.md or CLAUDE.md snippets.
  • Prefer setup to leave network-jobs on PATH (e.g. ~/.local/bin) without requiring a manual shell source.
  • Do not surface the deprecated hosted product (jobs.hirefrank.com) in skill-suite setup or docs.

Learned Workspace Facts

  • Public repo is hirefrank/network-jobs; this workspace is the local skill suite at ~/Projects/network-jobs.
  • Runtime data lives under ~/.network-jobs/ and is shared across agents (Claude Code, Cursor, Codex, etc.).
  • Skills live under skills/; install via npx skills add hirefrank/network-jobs and/or network-jobs setup --agent.
  • Clone or install the suite as network-jobs-suite (not network-jobs) so the network-jobs skill can be symlinked without path collision.
  • Pipeline is import → careers-discover (stage only) → user confirm → jobs-ingest → search → warm intro; never invent job fields; the suite has no hosted API (local files only).
  • Scraping-skill patterns are modeled after ~/Projects/provenance; the hosted 410 Worker source is worker/ (jobs-api on jobs.hirefrank.com), with ops notes in worker/SUNSET.md.
  • Setup links the same skill set into multiple agent skill dirs (claude-code, cursor, codex, opencode, pi, gemini-cli, hermes-agent, muse, agents), typically via symlinks re-pointed on re-setup.
  • Install with npm i -g @hirefrank/network-jobs@latest && network-jobs setup --agent auto (registry primary; npx --yes @hirefrank/network-jobs@latest setup … for zero-install; npx --yes 'github:hirefrank/network-jobs#main' … only for bleeding edge — use #main, not @main); setup should place the CLI on PATH under ~/.local/bin.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free