job-search

Scan job boards, score matches, and store results in SQLite.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/kenbanks-peng/skills --skill job-search-kenbanks-peng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: job-search
Source: https://github.com/kenbanks-peng/skills/tree/main/job-search
Command: npx skills add https://github.com/kenbanks-peng/skills --skill job-search-kenbanks-peng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Scan job-board URLs for roles matching the user's skillset and constraints, record new matches in a SQLite database, and produce a daily summary report.

Core Features & Use Cases

  • Automates the end-to-end job-hunt workflow: URL resolution, data extraction, deduplication, scoring, and daily reporting.
  • Maintains a local workspace with data, templates, and a runnable pipeline to generate a docx daily report and a workbook export.
  • Supports multiple tracks, rubric guidance, and profile context to tailor scoring.

Quick Start

Run the skill to scan configured job boards, hydrate postings, and generate today's matches report.

Frequently Asked Questions about job-search

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate job search daily matches and scoring against a rubric?

To automate job search daily matches, configure a workspace with job-search-spec.toml and job-search-urls.md. The pipeline resolves URLs, fetches postings, hydrates descriptions, dedupes records, scores candidates against track rubrics, and exports results to a SQLite database.

How does automated job board scanning handle deduplication and data persistence?

Automated job board scanning handles deduplication by resolving fetched postings against existing records in a local SQLite database. It persists new matches and maintains historical data within the workspace's data directory to ensure reproducible daily results.

Can I use a SQLite database and toml configuration to generate a daily job report?

Yes, you can use a SQLite database and toml configuration to generate a daily job report. The workspace requires job-search-spec.toml to define constraints and tracks, while the SQLite database persists hydrated job postings and scoring outputs for daily workbook exports.

What is the best way to track multiple job tracks and profile context in a local database?

The best way to track multiple job tracks and profile context in a local database is using a structured workspace pipeline. It leverages track rubrics and profile context specified in configuration files to tailor candidate scoring and maintain distinct match histories.

Do I need specific workspace files to run the job-hunting workflow and export a workbook?

Yes, you need specific workspace files to run the job-hunting workflow and export a workbook. The pipeline requires a workspace containing job-search-spec.toml, job-search-urls.md, and a data directory to hydrate postings, score candidates, and produce reproducible daily reports.

Why does my job board URL resolution fail to hydrate full descriptions during the scan?

Job board URL resolution fails to hydrate full descriptions when the workspace lacks properly configured URL templates in job-search-urls.md. The pipeline depends on resolving these templates correctly before fetching postings, extracting descriptions, and persisting matches to the database.