employers

Adds or removes employers in the JobScan registry and updates job title match patterns.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/MarioLuppino/JobScanPlugin --skill employers-marioluppino
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: employers
Source: https://github.com/MarioLuppino/JobScanPlugin/tree/main/plugins/jobscan/skills/employers
Command: npx skills add https://github.com/MarioLuppino/JobScanPlugin --skill employers-marioluppino

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Job seekers need their automated job scanner to watch the right companies and match the right job titles, but employer lists change constantly and editing configuration files by hand is error-prone. This Skill manages the employer registry and title-matching rules so the weekly scan keeps finding relevant openings. ## Core Features & Use Cases - Employer Registry Management: Add or remove organizations in employers.json, then re-run ATS feed discovery (Greenhouse, Lever, Workday) so changes take effect immediately. - Registry Growth from Search Results: Harvest employer names from real job search results instead of relying on memory, merging new entries without overwriting hand-corrected slugs. - Job Title Pattern Tuning: Write and test case-insensitive regex patterns for matchTitlePatterns and excludeTitlePatterns, with a test script to confirm patterns actually match before relying on them. - Use Case: Eight months after setup, you remember a company you want to watch. You say "add Acme Group to my job scan" and the Skill registers it, discovers its job board feed, and reports how many open roles it currently has. ## Quick Start Add the employer Acme Group to my job scan and tell me how many open roles it has right now.

Frequently Asked Questions about employers

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

FAQPage Schema
How do I add a new employer to my automated job scan?▼

Provide only the employer name; the Skill adds it to employers.json with candidate slugs, then runs discovery scripts to locate its ATS feed on Greenhouse, Lever, or Workday. It verifies success by reporting how many open roles that employer currently has.

How do I change which job titles my job scanner matches?▼

Edit the matchTitlePatterns regex list in triage-config.json, keeping word boundaries so terms like nurse do not match nursery. Run the test-triage script and a summary fetch afterward to confirm the pattern actually matches live postings.

Why is my job scan finding no postings for an employer?▼

The employer may use Workday, which needs a separate discovery script, or its slug may be spelled differently than guessed. Some employers run their own careers page with no public feed, in which case the weekly web-search sweep must cover them.

Can I grow my employer list from real job search results?▼

Yes. Run a search sweep for your job titles, collect the employer behind every matching posting, and pipe the names into the harvest script. Harvesting merges safely, preserving existing sectors and hand-corrected slugs.

Does removing an employer hide its previously seen job postings?▼

Removing an employer stops future postings from arriving, but postings already screened out stay screened out because the seen-URL cache tracks them independently. That cache behavior is intentional and unaffected by registry changes.