/jobsearch:checkupSomething is not working, or you want to know whether the search is working well. Use whenever the user says a thing is broken, wrong, missing, stuck, or slow — "this doesn''t work", "why didn''t it find that", "it keeps failing", "how do I get this fixed" — and for a periodic effectiveness review.
/jobsearch:doctorCheck that this job search's install and configuration are healthy and current with the installed plugin: deterministic checks, and a `--fix` that only makes safe repairs. Not for whether the search is working well: that is /jobsearch:checkup.
/jobsearch:lettersConfigure where finished cover letters go — a Google Doc in your Drive folder, or a local .docx — and render one.
/jobsearch:linkedinCheck whether LinkedIn is signed in for the job search, and walk the user through signing in if it is not.
/jobsearch:mailboxesConfigure which mail accounts the job search reads, check that each one can actually be searched, and show or switch which mail connector the search uses (gmail-multi, or the claude.ai Gmail, Microsoft 365, Fastmail or Superhuman connector). Not for registering an account with the connector; that is
/jobsearch:resumeConfigure where a rendered resume variant goes — a Google Doc in your Drive folder, or a local .docx — and render one. Not for reviewing resume content; that is /jobsearch:review-resume.
/jobsearch:review-linkedinReview the public-profile layer: every public-profile variant with each field measured against its recorded character cap, its open items and the presence rules. Use when the user wants to check their LinkedIn profile text. Not for signing LinkedIn in; that is /jobsearch:linkedin.
/jobsearch:review-resumeReview the resume layer: the claim union, every print-surface variant as it will look, its open items and the presence rules. Use when the user wants to see or check their resume. Not for rendering a file to Drive or .docx; that is /jobsearch:resume.
/jobsearch:searchLook for roles now: sweep employer career pages (`companies`), job boards and aggregators (`boards`), or both, on any day, without waiting for the posture's scheduled days. Needs the explicit `attended` form, in a session you are present for. Not the full daily run (that is /jobsearch:daily-run atte
/jobsearch:setup-routinesCreate or repair the two scheduled runs for this job search (the daily run and the weekly review), with thin prompts and the cron your tier declares. Use after setup, after changing tier, or when a routine has drifted. Not for changing how often the search runs; that is /jobsearch:tier.
/jobsearch:sourcingSee every job source this search uses (LinkedIn, boards such as Indeed and Dice, alert emails, company job-board feeds, curated boards), whether each is on and covered, and turn any on or off. Also choose how each board is reached: a site plugin, the in-app browser, or Chrome. `employers attended` f
/jobsearch:statusShow the job search's status now: what needs you and by when, roles whose stored pay removal would now be screened differently (flagged, never reopened), the inbox, the lock, the last and next background run, whether the runs did anything, dashboard freshness and gate health. Use when the user asks
/jobsearch:tierChange how often the job search runs (the main lever on cost), and which weekdays career pages and job boards are swept. Not for turning a source on or off; that is /jobsearch:sourcing.