メニュー
How to validate a job posting URL before adding it to the pipeline or recommending it to the user. Built from real failures during search sessions — HTTP 200 ≠ active posting, and most ATS systems serve empty pages to scrapers.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
@dom's task-delegation system. Use when @dom needs to hand work to a subordinate bot (@smartballz, @job, @grof2, @nyx, etc.) — it writes a structured task into that bot's root TODO.md or memory; the bot implements it. @dom NEVER implements. Also use bot-side to read your own delegated tasks (dom intake). Commands: dom delegate/tasks/intake/bots.
Report AI token usage, cost, and latency per model and audit that Ollama routing is being enforced. Use when you want to know what tokens/cost went to which model (Ollama vs Haiku/Sonnet/Opus via OpenRouter), what Ollama saved vs paid tiers, the cost-vs-time tradeoff, or to verify the four-tier waterfall is keeping cheap/free work on local Ollama. Invoked as `dom usage` (named dom-usage to avoid colliding with Claude Code's built-in /usage). Reads the log that delegate_task/ask_local write.
Gate any new MCP tool, skill, agent persona, voice profile, or LLM-backed surface behind a behavior eval before shipping. Also enforces skill shape, memory architecture, and workflow-script placement. Invoke when adding, renaming, or relaxing any of the above.
Extracts and classifies form fields from job posting pages. Identifies form system (Workday, Lever, Greenhouse, LinkedIn, custom HTML). Maps resume data to standard fields. Suggests answers for custom fields. Outputs JSON schema showing what the user needs to fill in.
Discovers new job postings matching the user's criteria from major job boards. Runs daily to find roles matching profile.yaml's search section (target_roles, keywords, min_salary, remote_only). Outputs to the discovered_jobs table in data/job_tracker.db for curation.
SOC 職業分類に基づく
| name | job-search-validation |
| description | How to validate a job posting URL before adding it to the pipeline or recommending it to the user. Built from real failures during search sessions — HTTP 200 ≠ active posting, and most ATS systems serve empty pages to scrapers. |
The single biggest source of frustration during a search session is recommending dead links and stale postings. This skill encodes what works.
HTTP 200 does NOT mean the posting is active. Many ATS systems serve a "this job is no longer active" page with a 200 status. Examples confirmed in the wild:
careers.thehersheycompany.com) — returns 200 + "This job posting is no longer active"jobs.lincolnfinancial.com) — returns 200 + "This position is no longer posted"careers.upmc.com) — returns 200 + "Job not found - UPMC" as the page titlevanguardjobs.com) — returns 200 + "Page not found - Vanguard Careers" for stale IDsYou must read the page content (the actual job title, description, or the absence of "no longer active" / "not found" language) to validate.
Fast batch validation. Use this for screening ~20 URLs at once.
UA="Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"
URL="..."
body=$(curl -A "$UA" -L -s --max-time 12 "$URL")
title=$(echo "$body" | grep -oE '<title>[^<]+' | head -1 | sed 's|<title>||')
if echo "$body" | grep -qiE 'no longer (active|posted|available|accepting)|position is closed|job has been (closed|filled)|posting (has expired|is closed)|requisition is no longer|job not found|page not found|expired'; then
echo "❌ CLOSED | $title"
elif echo "$title" | grep -qiE 'not found|page not found|expired'; then
echo "❌ NOT FOUND | $title"
elif [ -n "$title" ]; then
echo "✅ LIKELY OPEN | $title"
else
echo "❓ NEED MANUAL CHECK | (empty title — JS-rendered ATS)"
fi
Use when curl returns empty title (JS-rendered) OR to confirm Tier 1 hits before recommending.
WebFetch(
url: "...",
prompt: "Is this an active, currently-open job posting? Or does the page say
'no longer active', 'this job is closed', 'this position has been
filled', or redirect to a generic page? Quote the relevant text."
)
Workday-based ATS (*.wd5.myworkdayjobs.com) and dejobs.org are heavily
JS-rendered. Neither curl nor WebFetch can read the job content. Either:
| ATS / host | Reliability | Validation method |
|---|---|---|
Greenhouse (job-boards.greenhouse.io, boards.greenhouse.io) | ⭐⭐⭐⭐⭐ | WebFetch reads content reliably |
| Direct ATS (Lockheed, Erie Insurance, Hershey, Lincoln Financial) | ⭐⭐⭐⭐ | Tier 1 works — read body for "no longer" patterns |
LinkedIn (linkedin.com/jobs/view/{id}) | ⭐⭐⭐ | Rate-limited; same URL returns different content per call. Newer job IDs (43xxxxxxxx+) more likely fresh; older (38xxxxxxxx) usually stale. Use WebFetch with retry. |
Ashby (jobs.ashbyhq.com) | ⭐⭐⭐ | WebFetch sometimes returns minimal content |
Workday (*.wd5.myworkdayjobs.com) | ⭐ | JS-rendered, scraper-blind. Browser only. |
| dejobs.org | ⭐ | JS-rendered aggregator. Browser only. |
| JS-rendered company sites (Northrop, UPMC newer pages) | ⭐ | Browser only |
LinkedIn job IDs are auto-incrementing integers. Rough freshness signal:
43xxxxxxxx and 44xxxxxxxx → posted 2026, likely fresh42xxxxxxxx → late 2025, possibly fresh40xxxxxxxx–41xxxxxxxx → mid 2025, mixed38xxxxxxxx and below → 2024 or earlier, usually closed and redirects to generic searchWhen LinkedIn redirects a closed job, the page title becomes something like:
"7,000+ Senior Product Design Engineer jobs in United States" or
"813 Klaviyo jobs in United States" (a generic search result). That title
pattern is the dead-job signal.
A live LinkedIn job has a title like:
"Stanley Black & Decker, Inc. hiring Lead Engineer, Embedded Software in Towson, MD | LinkedIn"
The presence of " hiring " in the title is the alive marker.
Before handing a list of links to the user:
search.target_rolessearch.remote_only) OR matches search.locationssearch.min_salary (if posted)All criteria come from profile.yaml — see profile.yaml.example at the repo root.