career-ops
>-
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
Your turn
Paste one job you were about to apply to tonight. If it comes back do not apply, you just got the night back. If it comes back with a plan, you know what to do next.
npx @santifer/career-ops init
You don't have to search alone
The silence after you hit send is not about you. Enough people saw the same thing to write the practice down, in six lines:
Apply better to fewer. Signal over volume. Evidence over keywords. A human decides. Local-first. Dignity on both sides of the table.
Hiring will not fix itself. The people going through it can, and they are already in the room, comparing notes and fixing each other's setups.
This is where the fix gets written. A room, not a club. Let's build together.
Sponsors
career-ops is free for candidates, forever. These companies sponsor the project:
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
.agents/skills/career-ops/SKILL.md7.8 KBupstream ↗
--- name: career-ops description: >- AI job search command center -- evaluate offers, generate CVs, scan portals, track applications. Use when the user pastes a job URL or JD, asks to scan portals, generate a CV/PDF, track applications, prepare for interviews, draft outreach/emails, or run any career-ops mode. arguments: mode user_invocable: true user-invocable: true argument-hint: "[scan | discover | deep | pdf | text | latex | latex-tex | cover | email | add | expand | eu-swe | oferta | ofertas | apply | batch | tracker | agent-inbox | pipeline | contacto | training | project | interview-prep | interview | master-profile | interview/plan | interview/practice | interview/debrief | interview-redflag | patterns | offer-prep | titles | upskill | followup | reply-watch | outcome | update]" license: MIT --- # career-ops -- Router career-ops is a multi-CLI job-search command center. The routing below is shared across supported agent CLIs even when the invocation surface differs. ## Project Root Resolution Before reading any repo-relative path, derive `PROJECT_ROOT` from this loaded `SKILL.md`: start at the skill file's directory and walk upward until the nearest directory containing both `AGENTS.md` and `modes/`. Resolve every path in this router (`modes/`, `config/`, `data/`, scripts, templates, and output paths) against `PROJECT_ROOT`, never against the process's current working directory. This is required even when the checkout itself is nested (for example `Development\\career-ops`) or the command starts from a subdirectory. If those two sentinels cannot be found, stop and locate the career-ops checkout before reading or writing files. ## Invocation Notes - CLIs with slash-command registration can expose this router as `/career-ops`. - In Cursor, this skill lives at `.cursor/skills/career-ops/` and is auto-discovered; ask for a mode by name, or paste a JD/URL to trigger auto-pipeline. - In Pi, this skill is auto-discovered from `.agents/skills/career-ops/` and exposed as `/skill:career-ops`; `AGENTS.md` loads from the repo root as project context, so there is no wrapper file. Headless Pi workers use `pi -p "prompt"`. Project skill discovery follows Pi's per-folder trust decision: `/trust` applies to future Pi processes, so restart `pi` before invoking `/skill:career-ops` (`-a` trusts a single run and needs no restart). - Interactive Codex sessions use `codex` in the repo root. Slash commands are not guaranteed in Codex, so ask Codex to run the same mode by name if `/career-ops` is unavailable. - Headless Codex workers use `codex exec "prompt"`. - The routing semantics below stay the same regardless of whether the entrypoint is a slash command or a natural-language prompt. Codex prompt examples that map to the same router semantics: ```text Evaluate this JD with career-ops auto-pipeline: https://company.com/jobs/123 Run the career-ops scan mode and summarize new matches. Run the career-ops pipeline mode for data/pipeline.md. Run the career-ops pdf mode for the latest evaluated role. Run the career-ops tracker mode and summarize the current statuses. ``` ## Mode Routing Determine the mode from `$mode`: | Input | Mode | |-------|------| | (empty / no args) | `discovery` -- Show command menu | | JD text or URL (no sub-command) | **`auto-pipeline`** | | `oferta` | `oferta` | | `ofertas` | `ofertas` | | `contacto` | `contacto` | | `deep` | `deep` | | `interview-prep` | `interview-prep` | | `interview` | `interview` | | `master-profile` | `master-profile` | | `eu-swe` | `regional/eu-swe` | | `interview/plan` | `interview/plan` | | `interview/practice` | `interview/practice` | | `interview/debrief` | `interview/debrief` | | `pdf` | `pdf` | | `text` | `text` | | `latex` | `latex` | | `latex-tex` | `latex-tex` | | `email` | `email` | | `add` | `add` | | `expand` | `expand` | | `training` | `training` | | `project` | `project` | | `tracker` | `tracker` | | `agent-inbox` | `agent-inbox` | | `inbox` | `agent-inbox` | | `pipeline` | `pipeline` | | `apply` | `apply` | | `scan` | `scan` | | `discover` | `discover` | | `batch` | `batch` | | `patterns` | `patterns` | | `offer-prep` | `offer-prep` | | `titles` | `titles` | | `upskill` | `upskill` | | `followup` | `followup` | | `reply-watch` | `reply-watch` | | `outcome` | `outcome` | | `interview-redflag` | `interview-redflag` | | `update` | `update` | | `cover` | `cover` | **Auto-pipeline detection:** If `$mode` is not a known sub-command AND contains JD text (keywords: "responsibilities", "requirements", "qualifications", "about the role", "we're looking for", company name + role) or a URL to a JD, execute `auto-pipeline`. If `$mode` is not a sub-command AND doesn't look like a JD, show discovery. --- ## Output Language Directive Before executing any mode, read `config/profile.yml` if it exists and resolve: - `language.output` → ISO language code for human-facing output. Default: `en`. - `language.modes_dir` → optional market-mode directory. This controls market vocabulary and local evaluation rules only. It may be a single string (one declared market, the historical default) or a list of declared candidate markets for a candidate genuinely running parallel campaigns in more than one market at once (#3793), e.g. `modes_dir: [modes/de, modes/zh]`. When a list is given, the FIRST entry is primary and supplies the evaluation-mode file (Block A-F rules can only run from one market's file at a time); EVERY declared market's `_shared.md` is loaded into context. `modes` itself is a valid declared candidate for markets without a localized directory; when first it supplies `modes/oferta.md`, and its baseline `modes/_shared.md` is loaded once. Per posting, judge which declared market actually applies from the JD's own MARKET signals (hiring-entity jurisdiction, currency, benefits/legal vocabulary) — never from the JD's language alone. If genuinely ambiguous, an interactive session asks and stops before persistence; an unattended worker uses the primary market and records that fallback in the report header or Block G. Inject this directive after loading the mode instructions and before producing any user-visible content: > Write all human-facing output in `{language.output}` regardless of the language of these instructions or of the job description. This includes reports, tracker notes, PDFs, cover letters, outreach, interview prep, form answers, and summaries. If `language.modes_dir` supplies market-specific vocabulary (one market, or several declared at once), keep the market logic but explain terms in `{language.output}` when needed. `language.output` is authoritative for prose. `modes_dir` is market context; it must not force the prose language. --- ## Discovery Mode (no arguments) If your CLI supports `/career-ops`, show this menu. In Codex, surface the same options in plain text and map the requested mode the same way. Concrete equivalents for Codex prompt-driven sessions: ```text /career-ops {JD} ↔ "Evaluate this JD with career-ops auto-pipeline: {JD or URL}" /career-ops scan ↔ "Run the career-ops scan mode and summarize new matches." /career-ops pipeline ↔ "Run the career-ops pipeline mode for data/pipeline.md." /career-ops pdf ↔ "Run the career-ops pdf mode for the latest evaluated role." /career-ops email ↔ "Run the career-ops email mode for the latest evaluated role." /career-ops tracker ↔ "Run the career-ops tracker mode and summarize the current statuses." ``` Show this menu: ``` career-ops -- Command Center Available commands: /career-ops {JD} → AUTO-PIPELINE: evaluate + report + PDF + tracker (paste text or URL) /career-ops pipeline → Process pending URLs from inbox (data/pipeline.md) /career-ops oferta → Evaluation only A-F (no auto PDF) /career-ops ofertas → Compare and rank multiple offers /career-ops contacto → LinkedIn power move: find contacts + draft message /career-ops deep → Deep researREADME.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/career-ops-hq-career-ops-agents-skills-career-ops.md