verify-freehire
Skill3.6k starsChanged yesterdayMITView on GitHub
Launch an isolated freehire stack from this checkout with fixture or live ingestion and drive it like a user with Playwright to prove a change works. Use before calling a change done, when checking a pull request is ready to merge, or when asked to run, see or screenshot freehire locally. Works on the laptop (mise + Docker) and in the SuperPlane coder runner.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Who's talking about strelov1/freehire
- speedyapply/JobSpy“Feature Request: add freehire.me as a source (public API, no proxy needed, aggregates 227 boards)”GitHub · Aug 16, 2026 · 5 reactions
- alex-denisov/openqareer“feat(sources): полный текст вакансий VK (B641)”GitHub · Nov 10, 2026
- alex-denisov/openqareer“feat(sources): доски iCIMS, Jobvite и Oracle из freehire (B641)”GitHub · Nov 10, 2026
- strelov1/freehire-mcp“Connect Freehire plugin to OAuth account tools”GitHub · Nov 4, 2026
- factwright/factwright“Filling applications on SmartRecruiters' newer form, SAP SuccessFactors, iCIMS and Oracle Taleo”GitHub · Oct 24, 2026
The biggest 5 of 35 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 35
Talked about on GitHub and Bluesky (35 times).
On GitHub · 34
- Aug 16, 2026Feature Request: add freehire.me as a source (public API, no proxy needed, aggregates 227 boards) — speedyapply/JobSpy5 reactions · 1 comment
- Nov 10, 2026feat(sources): полный текст вакансий VK (B641) — alex-denisov/openqareer0 reactions
- Nov 10, 2026feat(sources): доски iCIMS, Jobvite и Oracle из freehire (B641) — alex-denisov/openqareer0 reactions
- Nov 4, 2026Connect Freehire plugin to OAuth account tools — strelov1/freehire-mcp0 reactions · 1 comment
- Oct 24, 2026Filling applications on SmartRecruiters' newer form, SAP SuccessFactors, iCIMS and Oracle Taleo — factwright/factwright0 reactions
29 more on GitHub
- Oct 21, 2026FMHY suggestions 2026-10-21 — sudosilo/free-as-in-links0 reactions
- Sep 15, 2026fix: update minio images as the original repo is no longer available — overhangio/tutor-minio0 reactions · 2 comments
- Aug 17, 2026refactor(google): extract job records from AF_initDataCallback payload — amikai/openings-mcp0 reactions
- Aug 16, 2026Add freehire.me as a job source — full JD text in the search response — he-yufeng/FindJobs-Agent0 reactions · 2 comments
- Aug 16, 2026Add freehire.me as a source — a wider pool for the agents to reject from — VonTerraProject501c3/slushpile0 reactions · 1 comment
- Aug 16, 2026Add freehire.me as an aggregator source — aggregated, but still the employer's own links — vesaias/JobNavigator0 reactions · 2 comments
- Aug 16, 2026Add freehire.me as a listing source — pre-tagged fields to score against — Keljian/JSE0 reactions · 1 comment
- Aug 16, 2026Add freehire.me as a discovery source — a stable front end for the pipeline — leopu00/job-hunter-team0 reactions
- Aug 16, 2026Add freehire.me as a source — normalized results, no scraping layer — BjornMelin/ai-job-scraper0 reactions
- Aug 16, 2026Add freehire.me as a source — an HTTP call instead of a scrape — saeedkolivand/ai-job-hunter-app0 reactions · 1 comment
- Aug 16, 2026Add freehire.me as a job source — no extra account, real ATS links — suxrobGM/jobpilot0 reactions · 3 comments
- Aug 16, 2026Add freehire.me as a source — key-free, read-only, nothing to store — cboyd0319/JobSentinel0 reactions
- Aug 16, 2026Add freehire.me as a provider — one call covering 227 aggregated sources — ever-jobs/ever-jobs0 reactions · 1 comment
- Aug 16, 2026Add freehire.me as a source — 227 boards behind one key-free API — amikai/openings-mcp0 reactions · 1 comment
- Aug 16, 2026Add freehire.me as a source — sponsorship is a server-side filter, so the pre-screen gets cheaper — abhishektuteja01/ApplYourself0 reactions · 1 comment
- Aug 16, 2026Add freehire.me as a fetch source — public ATS data, already aggregated and tagged — perryvegehan/PWP_jobhunt0 reactions
- Aug 16, 2026Add freehire.me as a discovery source — ATS boards already aggregated, no tokens — aravindpranav/job-agent0 reactions
- Aug 16, 2026Add freehire.me as a discovery provider — no API key needed for self-hosted runs — girshovich/job-hunter0 reactions
- Aug 16, 2026Add freehire.me as a source — 294K company career pages behind one key-free API — replyre/job-hunter0 reactions
- Aug 16, 2026Support for freehire.me — key-free API source that aggregates 227 boards — DaKheera47/job-ops0 reactions
- Aug 16, 2026提议:新增职位搜索渠道(freehire.me,零配置免登录)/ Proposal: a zero-config jobs channel — Panniantong/Agent-Reach0 reactions
- Jul 23, 2026chore(freehire-search): migrate freehire.dev → freehire.me — ai-job-search-dev/ai-job-search0 reactions
- Jul 21, 2026Add freehire — awesome-selfhosted/awesome-selfhosted-data0 reactions
- Jul 9, 2026Add freehire-search: country-agnostic freehire.dev aggregator skill — ai-job-search-dev/ai-job-search0 reactions · 2 comments
- Jul 8, 2026Add a freehire-search skill — one aggregator skill covering many boards & countries — ai-job-search-dev/ai-job-search0 reactions · 4 comments
- Jun 17, 2026Add freehire (open-source IT job aggregator) — idimetrix/awesome-job-boards0 reactions
- Jun 17, 2026Add freehire (open-source IT job aggregator) — trinhminhtriet/awesome-job-boards0 reactions
- Jun 17, 2026Add freehire (open-source IT job aggregator) — tramcar/awesome-job-boards0 reactions
- Jun 17, 2026Add freehire (open-source IT job aggregator) — emredurukn/awesome-job-boards0 reactions · 1 comment
On Bluesky · 1
- Oct 21, 2026🚀 Skyrocketing! 🚀 (200+ new stars) 📦 strelov1 / freehire ⭐ 2,017 (+405) 🗒 Go freehire — the open-source search engine for job seekers — @github-trending.bsky.social0 likes and reposts · 1 reply
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- design-system/AGENTS.mdAGENTS.md
- extension/AGENTS.mdAGENTS.md
- web/AGENTS.mdAGENTS.md
- .cursor/rules/commit-checks.mdcCursor rule
- code-reviewSkill
- review-dictionary-requestsSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Run .agents/skills/verify-freehire/verify.sh preflight to check local tools.
- Very specific: line 64
Not running, on purpose: Redis (the rate limiter fails open, the log shows connection refused, harmless), mail (no SES: sign-up works, …
- Very specific: line 78
Every line must say ok. It checks: the server was built from the current HEAD and the Go build source snapshot (including dirty/untracked …
- Distinctive: line 131
Check side effects next to what is visible: the row in Postgres, the document in search.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill 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.
Files
verify-freehire
Proves a change in the real app: the API built from THIS checkout, the web dev server in front of it, postings through the real ingest path, and a real browser. Tests passing is not this; this is the user path.
Everything lives in this folder. Run commands from the repository root. The helpers require Python 3 to fingerprint source files.
| Helper | What it does |
.agents/skills/verify-freehire/stack.sh up | start everything, seed, wait until ready, print doctor and the env |
.agents/skills/verify-freehire/stack.sh doctor | read-only health check of the running instance |
.agents/skills/verify-freehire/stack.sh env | the exports a drive needs: eval "$(.agents/skills/verify-freehire/stack.sh env)" |
.agents/skills/verify-freehire/run-journey.sh <spec> | run one Playwright journey against the instance, evidence included |
.agents/skills/verify-freehire/stack.sh down | stop what up started, drop its database; evidence stays |
Foreground lifecycle (recommended)
Run .agents/skills/verify-freehire/verify.sh preflight to check local tools. Run
verify.sh .agents/skills/verify-freehire/journeys/jobs-search.spec.ts for a complete
foreground lifecycle: startup, doctor, journey, evidence and teardown. Pass additional
spec paths to run them in sequence. Keep this command in one live exec session until
it exits; detached Vite can disappear when the launching session ends. EXIT, INT and
TERM trigger cleanup, retaining startup output and service logs in a unique evidence
directory. SIGKILL cannot run cleanup; use stack.sh down after inspecting diagnostics.
An existing state directory is refused rather than taken over.
Launch
.agents/skills/verify-freehire/stack.sh up # ~1 min warm, longer on a first pnpm/go buildWhat up does, in order:
- Postgres. Uses
TESTDB_ADMIN_URL(mise sets it on the laptop; the coder runner's image sets it and starts Postgres itself). On the laptop, if nothing answers, it runsdocker compose up -d db. Creates databaseverify_<api port>and runscmd/migrate. - Meilisearch, private to this instance on
api port + 2: ameilisearchbinary on PATH if there is one, else a containerverify-freehire-meili-<port>from the imagedocker-compose.ymlpins. Neither: it warns and/jobswill answer 500. - Seed.
cmd/reindexcreates the empty index. By default a three-posting fixture substitutes the external Greenhouse response and runs the real adapter, pipeline, database store and search enqueue path.cmd/search-drainindexes it. SetVERIFY_SEED_MODE=liveto crawl a real board withcmd/add-boardandcmd/ingest;VERIFY_SEED_PROVIDER/VERIFY_SEED_BOARDchoose it.VERIFY_SEED_BOARD=skips seeding. Fixture writes require a loopbackverify_database; no model or external board request is needed. - API:
go build ./cmd/server, started on the api port withJWT_SECRET,FRONTEND_ORIGINandMEILI_*set. Ready =/healthsays"database":"up". - Web:
pnpm installindesign-system/andweb/, thenvite devonapi port + 1, proxying/apito the API. Ready =GET /jobsanswers 200 (the first SSR compiles).
Ports: the api port is $VERIFY_API_PORT, else mise's per-worktree $PORT, else 18080.
State (pids, logs, the server binary) is in /tmp/verify-freehire-<api port>.
Logs to read when something is off: server.log, web.log, seed.log, migrate.log there.
Not running, on purpose: Redis (the rate limiter fails open, the log shows connection
refused, harmless), mail (no SES: sign-up works, email verification codes never arrive),
OAuth providers, payments, LLM features (no LLM_*: AI routes refuse).
Isolation. Two instances can run side by side if their api ports differ (each worktree
gets its own $PORT from mise). up refuses to start over a live instance in the same
state dir. Do not point a drive at someone else's instance.
Doctor
.agents/skills/verify-freehire/stack.sh doctorEvery line must say ok. It checks: the server was built from the current HEAD and the Go build source snapshot
(including dirty/untracked files and embedded assets under cmd/ and internal/,
vendor files and module/workspace files; down + up after changing those inputs), the API and web
processes are the ones up started, /health sees the database, Meilisearch is healthy,
search holds seeded postings, /jobs renders. The journey helper runs it before every journey and refuses an unhealthy or stale stack.
Drive
Playwright from web/node_modules with its pinned Chromium (the runner has it in
/opt/ms-playwright; on a laptop without it: cd web && pnpm exec playwright install chromium).
.agents/skills/verify-freehire/run-journey.sh .agents/skills/verify-freehire/journeys/jobs-search.spec.tsThe journeys in journeys/ are the mapped features (see features/README.md). For a
change no journey covers, write a spec of your own the same way (any path; the helper
copies it into a unique directory under web/e2e/__verify__/ and deletes only that directory after) and run it with the
same helper. If it is a real regression test, also add it under web/e2e/ in the PR.
Rules that came from failed runs:
- Wait for hydration. The page is server-rendered; typing or submitting before Svelte
hydrates is lost (a form submits as a native GET).
await page.waitForLoadState('networkidle')after everygotothat is followed by input. - Cold routes are slow.
vite devcompiles each route on its first visit (5-15s), so a journey usesexpect.configure({ timeout: 30_000 })andtest.setTimeout(120_000), as the shipped ones do.upwarms/jobsand one job page. - Stable handles:
getByTestId('job-card'), roles with names (combobox 'Search jobs',button 'Create your account'),getByLabel('Email'). When a locator misses, read the page snapshot in the failure'serror-context.md; it lists every role and name. - Some lists open a posting in a new tab: wait for
context.waitForEvent('page')only when the link hastarget="_blank"(the feed does not). - API checks go through the web origin (
page.request.get('/api/v1/...')) or straight to$VERIFY_API_URLwith curl. - Database side effects:
psql "$DATABASE_URL"aftereval "$(stack.sh env)".
Evidence
Each journey prints its unique evidence directory under $VERIFY_EVIDENCE
(default /tmp/verify-freehire-evidence-<api port>). down never touches evidence.
The journey exports its directory to the spec and stores:
<journey>-<n>-<step>.png: screenshots the journey takes at each step (action, then result);<journey>.log: the Playwright run;<journey>-playwright/: the trace (pnpm exec playwright show-trace <trace.zip>) and, on failure,error-context.mdwith the page snapshot;- anything you add: save
psql/curloutput there too (| tee "$VERIFY_EVIDENCE/x.txt").
Proof standards:
- Drive the real user path: the UI or the public API. No internal setters, no test-only routes, no SQL writes to fake a state the feature should have produced.
- Capture the action and the resulting state, not only the last screen.
- Check side effects next to what is visible: the row in Postgres, the document in search.
- A journey that fails because the seed lacks something is a failure; write the reason in that feature's Gotchas. Never weaken the journey to make it pass.
- In a pull request, name what you drove, link or attach the screenshots, and say what you could not drive (mail, payments, LLM) instead of implying it was covered.
Cleanup
.agents/skills/verify-freehire/stack.sh downStops the processes up recorded (by pid, never by name), removes its Meilisearch
container, drops verify_<port>, deletes the state dir. It leaves the shared compose
Postgres running and the evidence folder in place. Run it after every failed attempt too.
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
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.

