What problem does it solve? A job scan can silently degrade — a config at the wrong path, an empty employer registry, or a Firecrawl connection that was never loaded in the current session — and return a fraction of expected results while looking like it worked. This Skill turns every silent degradation into one visible, fixable line. ## Core Features & Use Cases - Automated environment check: Runs a Node script that verifies Node's version, config paths, the data folder, profile files, job-title patterns, the employer registry, feed lists, the seen-URL cache, the federal API key, the archive folder, and the applied index. - Session-level checks a script cannot do: Verifies Firecrawl tools are actually loaded, the docx skill is available, browser fallback tools exist, a subagent dispatch tool is present, and the plugin root variable resolves. - Step zero of every scan: Runs automatically before each job-search run, classifying issues as fatal (stop and offer onboarding), degrading (continue with a noted fallback), or thin (mention once at the end). - Use Case: A user's scan returned almost nothing. They say "check my job scanner" and receive a plain-words list of what works, what is broken, and the one fix for each problem — such as restarting Claude Code to load Firecrawl. ## Quick Start Ask the assistant to check my job scanner and report anything that is not working with the fix for each issue.
