where

Shows and moves JobScan data and archive folders while updating path configuration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Users lose track of where their JobScan profile, résumés, digests, and application archives are stored, and moving those folders by hand breaks the scanner because every skill reads paths from a central config file. ## Core Features & Use Cases - Path reporting: Runs paths.mjs to print every resolved location — config file, data folder, ATS config, archive, and applied index — translated into plain folder names. - Safe relocation: Moves data and archive folders in the correct order (files first, then jobscan-config.md, then verification with paths.mjs and doctor.mjs) so no scan reads one folder while writing another. - Use Case: You moved your job-search folder to a new laptop and the scan now fails. This skill updates both paths in the config, verifies writability, and confirms the applied index is found. ## Quick Start Ask the assistant where JobScan keeps your files, or tell it to move your job-search folder to a new location.

Frequently Asked Questions about where

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

FAQPage Schema
How do I find where my job-search files are stored?▼

Run the paths.mjs script, which prints every resolved location: the config file, data folder, ATS config, archive, and applied index. The skill translates these into plain folder names you would see in Finder or File Explorer.

How do I move my job-search folder to a new location?▼

Move the files first while preserving folder structure, then update data_path and archive_path in jobscan-config.md, and verify with paths.mjs and doctor.mjs. Never copy-and-leave, because two copies of a profile diverge.

Why does my applied index look empty after moving folders?▼

An index that reads as empty after a move is a path problem, not lost data. The config file still points at the old location, so update jobscan-config.md and re-run doctor.mjs to confirm the index is found.

Can I store JobScan files inside the plugin folder?▼

No. The /plugin update command replaces the plugin folder wholesale, destroying anything stored there. Personal files found beside the scripts should be moved to the ats folder under your data path.

Why do paths resolve somewhere unexpected even though the config looks right?▼

The JOBSCAN_DATA, JOBSCAN_ARCHIVE, and JOBSCAN_INDEX environment variables override the config file. If one of these is set, it wins over jobscan-config.md, which is the usual cause of unexpected path resolution.