---
name: job-search-setup
description: Set up a private job-search workspace or connect an existing search to these skills. Use for onboarding and source mapping.
---

# Set up a job search

Give the search a home, then get to work. Standalone coaching can start from supplied context without a workspace, interview invitation or offer.

## Start with a request

Let users ask naturally:

- **Find and Apply to Jobs** — `job-research`
- **Find and Request Referrals** — `recruiting-outreach`
- **Interview Coach** — `job-interview`
- **Offer Negotiator** — `job-offer`

Call supporting skills when needed. Resume tailoring belongs inside the application workflow; users need not manage every handoff.

## Choose the workspace

Use the user's chosen private folder, outside the public package and installed skill folders. For an existing search, read its instructions and map its sources. Preserve names, storage services, records and owners; don't create a competing tracker.

For a new search, use ordinary file tools to copy the [blank workspace](assets/workspace/AGENTS.md) from `assets/workspace/` into that folder, preserving subfolders. Rename `gitignore.template` to `.gitignore`. Check destination paths first; never overwrite existing files. No installation script is required.

## Learn what matters

Reuse the resume and confirmed answers. Ask only for missing targets, level, locations/work rights, working languages, constraints and immediate priorities. Optional unknowns can wait. Collect sensitive identifiers or legal declarations only when an authorized application needs them.

Keep sourced, dated facts and corrections in `references/profile.md`; keep choices and workflow limits in `references/preferences.md`. Confirm the scheduling timezone when needed. Don't infer work rights from residence or timezone, or generalize an employer-specific declaration. Leave permissions unset unless granted.

## Keep one source for each thing

Adapt the private `AGENTS.md` to map installed skills and sources. The template routes all ten skills; load only what's needed. Follow [recordkeeping](assets/workspace/references/recordkeeping.md) when choosing fields and owners.

Start with one application tracker and one outreach record. Keep shortlist choices separate from employer stages; “pursue” alone doesn't authorize submission. Reuse valid grants within scope. Add separate lanes only when needed, with clear ownership.

Reuse resume templates and inventory; preserve submitted versions and receipts. Interview, offer, inbox and schedule notes support the live records. Leave unused templates blank. Dashboards read these sources rather than duplicating stages.

Check links, ownership and corrections, then report what's ready and the next useful action. Keep personal data out of the distributable package. Setup sends no messages, submits no applications and schedules nothing.