career-ops
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.
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 72 493
- Лиценз
- MIT
- Последна проверка на записа
- 19.09.2026 г.
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add career-ops-hq/career-opsСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
career-ops -- Router
career-ops is a multi-CLI AI job search agent. 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/. 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. Then derive DATA_ROOT, where the user's own files live, with the precedence path-resolver.mjs uses: CAREER_OPS_ROOT or CAREER_OPS_DATA_DIR if either is set; otherwise the path written in PROJECT_ROOT/.career-ops-data if that file exists and is not empty; otherwise PROJECT_ROOT itself. A relative value in either place resolves against PROJECT_ROOT. Run from PROJECT_ROOT, node -e "import('./path-resolver.mjs').then(m => console.log(m.getCareerOpsRoot()))" prints the same directory. With no override the two roots are one directory.
Resolve every path in this router against one of these two roots, never against the process's current working directory. User Layer paths resolve against DATA_ROOT. They include cv.md, article-digest.md, portals.yml, config/ (except the shipped *.example.* files), data/, reports/, output/, interview-prep/, modes/_profile.md, modes/_custom.md, modes/_brief.md, batch/tracker-additions/, and every other User Layer path in DATA_CONTRACT.md. Everything else (the other modes/ files, scripts, templates, the config/*.example.* files) resolves against PROJECT_ROOT.