菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | job-discovery |
| description | 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. |
Invoke this skill when: Running daily job discovery scrape, manually refreshing job boards, or searching for jobs in a specific niche (e.g., "Show me all Example Corp jobs in the market").
Daily automated scraping of major job boards to surface opportunities matching the user's constraints
(see profile.yaml and job_config.json). Filters out non-matching roles early.
Presents a curated list for manual approval.
job_config.json)profile.yaml search.target_companies)All criteria come from your profile.yaml search section and job_config.json filters:
Hard Constraints (must match all):
search.target_rolessearch.remote_only) or matches search.locationssearch.min_salary+ (if posted)Soft Constraints (preferential):
search.keywords (in priority order)Exclusions:
6:00 AM → job-discovery server wakes up
6:05 AM → Scrape LinkedIn, Indeed, Workday
6:20 AM → Filter for matching criteria
6:25 AM → Insert into discovered_jobs table
6:30 AM → Notify the user: "35 new jobs found"
→ → User curates + approves ~15 for application
CREATE TABLE discovered_jobs (
id INT PRIMARY KEY AUTO_INCREMENT,
job_url VARCHAR(255) UNIQUE,
company VARCHAR(100),
role_title VARCHAR(150),
source VARCHAR(50), -- 'linkedin', 'indeed', 'workday', etc
discovered_date TIMESTAMP,
salary_range VARCHAR(50),
description TEXT,
location VARCHAR(100),
status ENUM('discovered', 'approved', 'skip', 'applied'),
reason_skipped TEXT,
user_notes TEXT
);
=== JOB DISCOVERY REPORT (2026-04-29) ===
35 New Jobs Found
├─ LinkedIn: 12 jobs
├─ Indeed: 8 jobs
├─ Workday: 10 jobs
├─ Dice: 5 jobs
└─ Other: 0 jobs
TOP MATCHES (for user review):
1. Example Corp — Senior Engineer, Infrastructure
└─ Remote, $140-180K, Posted 1h ago
└─ https://examplecorp.com/careers/...
2. Acme Inc — Staff Engineer, Platform
└─ Remote, $150-190K, Posted 3h ago
└─ https://acme.example/careers/...
... (25 more)
ACTION: review these and approve for application
{
"job_boards": [
{
"name": "linkedin",
"enabled": true,
"scrape_frequency": "daily",
"search_terms": ["Principal Engineer remote", "Staff Engineer remote", "Architect remote"],
"min_salary": 150000
},
{
"name": "indeed",
"enabled": true,
"scrape_frequency": "daily",
"search_query": "(\"Principal Engineer\" OR \"Staff Engineer\" OR \"Architect\") AND remote AND $150000",
"location": "remote"
},
{
"name": "workday",
"enabled": true,
"scrape_frequency": "daily",
"instances": [
"databricks.wd5.myworkdayjobs.com",
"anthropic.wd5.myworkdayjobs.com",
"stripe.wd1.myworkdayjobs.com"
]
}
],
"filters": {
"min_salary": 150000,
"required_location": "remote",
"exclude_keywords": ["contract", "consulting", "visa sponsorship required"],
"include_keywords": ["principal", "staff", "architect", "lead"]
}
}
name: Daily Job Discovery
on:
schedule:
- cron: '0 6 * * *' # 6am daily
jobs:
discover:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Run job discovery
run: python mcp-servers/job-discovery/scraper.py
- name: Upload results
run: sqlite3 data/job_tracker.db < discovered_jobs.sql
- name: Notify the user
run: |
COUNT=$(sqlite3 data/job_tracker.db "SELECT COUNT(*) FROM discovered_jobs WHERE status='discovered' AND discovered_date >= datetime('now', '-1 day')")
echo "$COUNT new jobs discovered. Ready for curation."
| Component | Usage |
|---|---|
form-parser MCP | Takes approved jobs from discovered_jobs → extracts form fields |
job_tracker.db | Stores discovered_jobs + curation status |
| application workflow | Orchestrates discovery → parsing → submission |
| GitHub Actions | Triggers daily discovery, notifies the user |
| File | Purpose |
|---|---|
profile.yaml (repo root) | Search criteria source of truth |
mcp-servers/job-discovery/job_config.json | Scraper configuration |
mcp-servers/form-parser/ | Downstream: parses approved jobs |
@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.
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.