[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BNASBADTQW6ZYR8GFV7ZXV":3,"skill-same:01M7BNASBADTQW6ZYR8GFV7ZXV":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":47},"01M7BNASBADTQW6ZYR8GFV7ZXV","career-ops",null,"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\u002FPDF, track applications, prepare for interviews, draft outreach\u002Femails, or run any career-ops mode.","xs3curity\u002Fskillguard-action-test","xs3curity","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F83658112?v=4","01M7BKPAAZ8H0V8MMNN8PVR2PJ","xsec","01M7BKPABJNGD944G93J56FDWS",0,"MIT","https:\u002F\u002Fgithub.com\u002Fxs3curity\u002Fskillguard-action-test\u002Fblob\u002Fdev\u002Fold\u002Fsantifer-career-ops-agents-skills-career-ops-skill-md\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: career-ops\ndescription: >-\n  AI job search command center -- evaluate offers, generate CVs, scan portals,\n  track applications. Use when the user pastes a job URL or JD, asks to scan\n  portals, generate a CV\u002FPDF, track applications, prepare for interviews, draft\n  outreach\u002Femails, or run any career-ops mode.\narguments: mode\nuser_invocable: true\nuser-invocable: true\nargument-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 | interview\u002Fplan | interview\u002Fpractice | interview\u002Fdebrief | interview-redflag | patterns | offer-prep | titles | upskill | followup | reply-watch | outcome | update]\"\nlicense: MIT\n---\n\n# career-ops -- Router\n\ncareer-ops is a multi-CLI job-search command center. The routing below is shared across supported agent CLIs even when the invocation surface differs.\n\n## Project Root Resolution\n\nBefore 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\u002F`. Resolve every path in this router (`modes\u002F`, `config\u002F`, `data\u002F`, 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.\n\n## Invocation Notes\n\n- CLIs with slash-command registration can expose this router as `\u002Fcareer-ops`.\n- In Cursor, this skill lives at `.cursor\u002Fskills\u002Fcareer-ops\u002F` and is auto-discovered; ask for a mode by name, or paste a JD\u002FURL to trigger auto-pipeline.\n- 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 `\u002Fcareer-ops` is unavailable.\n- Headless Codex workers use `codex exec \"prompt\"`.\n- The routing semantics below stay the same regardless of whether the entrypoint is a slash command or a natural-language prompt.\n\nCodex prompt examples that map to the same router semantics:\n\n```text\nEvaluate this JD with career-ops auto-pipeline: https:\u002F\u002Fcompany.com\u002Fjobs\u002F123\nRun the career-ops scan mode and summarize new matches.\nRun the career-ops pipeline mode for data\u002Fpipeline.md.\nRun the career-ops pdf mode for the latest evaluated role.\nRun the career-ops tracker mode and summarize the current statuses.\n```\n\n## Mode Routing\n\nDetermine the mode from `$mode`:\n\n| Input | Mode |\n|-------|------|\n| (empty \u002F no args) | `discovery` -- Show command menu |\n| JD text or URL (no sub-command) | **`auto-pipeline`** |\n| `oferta` | `oferta` |\n| `ofertas` | `ofertas` |\n| `contacto` | `contacto` |\n| `deep` | `deep` |\n| `interview-prep` | `interview-prep` |\n| `interview` | `interview` |\n| `eu-swe` | `regional\u002Feu-swe` |\n| `eu-fintech` | `regional\u002Feu-fintech` |\n| `interview\u002Fplan` | `interview\u002Fplan` |\n| `interview\u002Fpractice` | `interview\u002Fpractice` |\n| `interview\u002Fdebrief` | `interview\u002Fdebrief` |\n| `pdf` | `pdf` |\n| `text` | `text` |\n| `latex` | `latex` |\n| `latex-tex` | `latex-tex` |\n| `email` | `email` |\n| `add` | `add` |\n| `expand` | `expand` |\n| `training` | `training` |\n| `project` | `project` |\n| `tracker` | `tracker` |\n| `agent-inbox` | `agent-inbox` |\n| `inbox` | `agent-inbox` |\n| `pipeline` | `pipeline` |\n| `apply` | `apply` |\n| `scan` | `scan` |\n| `discover` | `discover` |\n| `batch` | `batch` |\n| `patterns` | `patterns` |\n| `offer-prep` | `offer-prep` |\n| `titles` | `titles` |\n| `upskill` | `upskill` |\n| `followup` | `followup` |\n| `reply-watch` | `reply-watch` |\n| `outcome` | `outcome` |\n| `interview-redflag` | `interview-redflag` |\n| `update` | `update` |\n| `cover` | `cover` |\n\n**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`.\n\nIf `$mode` is not a sub-command AND doesn't look like a JD, show discovery.\n\n---\n\n## Output Language Directive\n\nBefore executing any mode, read `config\u002Fprofile.yml` if it exists and resolve:\n\n- `language.output` → ISO language code for human-facing output. Default: `en`.\n- `language.modes_dir` → optional market-mode directory. This controls market vocabulary and local evaluation rules only.\n\nInject this directive after loading the mode instructions and before producing any user-visible content:\n\n> 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, keep the market logic but explain terms in `{language.output}` when needed.\n\n`language.output` is authoritative for prose. `modes_dir` is market context; it must not force the prose language.\n\n---\n\n## Discovery Mode (no arguments)\n\nIf your CLI supports `\u002Fcareer-ops`, show this menu. In Codex, surface the same options in plain text and map the requested mode the same way.\n\nConcrete equivalents for Codex prompt-driven sessions:\n\n```text\n\u002Fcareer-ops {JD}           ↔ \"Evaluate this JD with career-ops auto-pipeline: {JD or URL}\"\n\u002Fcareer-ops scan           ↔ \"Run the career-ops scan mode and summarize new matches.\"\n\u002Fcareer-ops pipeline       ↔ \"Run the career-ops pipeline mode for data\u002Fpipeline.md.\"\n\u002Fcareer-ops pdf            ↔ \"Run the career-ops pdf mode for the latest evaluated role.\"\n\u002Fcareer-ops email          ↔ \"Run the career-ops email mode for the latest evaluated role.\"\n\u002Fcareer-ops tracker        ↔ \"Run the career-ops tracker mode and summarize the current statuses.\"\n```\n\nShow this menu:\n\n```\ncareer-ops -- Command Center\n\nAvailable commands:\n  \u002Fcareer-ops {JD}      → AUTO-PIPELINE: evaluate + report + PDF + tracker (paste text or URL)\n  \u002Fcareer-ops pipeline  → Process pending URLs from inbox (data\u002Fpipeline.md)\n  \u002Fcareer-ops oferta    → Evaluation only A-F (no auto PDF)\n  \u002Fcareer-ops ofertas   → Compare and rank multiple offers\n  \u002Fcareer-ops contacto  → LinkedIn power move: find contacts + draft message\n  \u002Fcareer-ops deep      → Deep research prompt about company\n  \u002Fcareer-ops interview-prep → Generate company-specific interview prep doc\n  \u002Fcareer-ops interview    → Interactive profile\u002FCV onboarding interview\n  \u002Fcareer-ops eu-swe    → Calibrate a European SWE application before CV\u002Fapply\u002Finterview\n  \u002Fcareer-ops eu-fintech → Scan 21 EU fintech portals for Product Manager roles (zero-token)\n  \u002Fcareer-ops interview\u002Fplan → Time-blocked prep plan for an upcoming interview\n  \u002Fcareer-ops interview\u002Fpractice → Practice interview, one question at a time with feedback\n  \u002Fcareer-ops interview\u002Fdebrief → Post-interview debrief: close gaps, predict next round\n  \u002Fcareer-ops pdf       → PDF only, ATS-optimized CV\n  \u002Fcareer-ops text      → Tailored markdown CV (mirrors cv.md, no PDF)\n  \u002Fcareer-ops latex     → Export CV as LaTeX\u002FOverleaf .tex\n  \u002Fcareer-ops latex-tex → Tailor your own resume.tex in place (opt-in; cv.md stays default)\n  \u002Fcareer-ops cover     → Cover letter: standalone JD paste or \u002Fcareer-ops cover {slug}\n  \u002Fcareer-ops email     → Formal application email draft (draft-only; never sends, submits, or clicks)\n  \u002Fcareer-ops add       → Add a project\u002Fpaper\u002Frole to your CV (fetch + preview + confirm)\n  \u002Fcareer-ops expand    → Auto-discover and add missing competencies from profile links\n  \u002Fcareer-ops training  → Evaluate course\u002Fcert against North Star\n  \u002Fcareer-ops project   → Evaluate portfolio project idea\n  \u002Fcareer-ops tracker   → Application status overview\n  \u002Fcareer-ops agent-inbox → Queue\u002Fdrain requests for the next session (data\u002Fagent-inbox.md)\n  \u002Fcareer-ops apply     → Live application assistant (reads form + generates answers)\n  \u002Fcareer-ops scan      → Scan portals and discover new offers\n  \u002Fcareer-ops discover  → Resolve a company list to scannable ATS boards + append to portals.yml (zero-token)\n  \u002Fcareer-ops batch     → Batch processing with parallel workers\n  \u002Fcareer-ops patterns  → Analyze rejection patterns and improve targeting\n  \u002Fcareer-ops offer-prep → Read a received offer\u002Fcontract with the candidate: clause walk + lawyer questions (not legal advice)\n  \u002Fcareer-ops titles    → Suggest adjacent job titles from your CV to broaden the search\n  \u002Fcareer-ops upskill   → Aggregate skill-gap analysis from your evaluated reports\n  \u002Fcareer-ops followup  → Follow-up cadence tracker: flag overdue, generate drafts\n  \u002Fcareer-ops outcome   → Record application outcome & archive artifacts\n  \u002Fcareer-ops update    → Update career-ops system files with diff preview + compat check\n\nInbox: add URLs to data\u002Fpipeline.md → \u002Fcareer-ops pipeline\nOr paste a JD directly to run the full pipeline.\n```\n\n---\n\n## Context Loading by Mode\n\nAfter determining the mode, load the necessary files before executing:\n\nIf `modes\u002F_custom.md` exists, read it after `modes\u002F_profile.md` and before the selected mode file. It contains user house rules and procedural preferences. It may override workflow\u002Fstyle defaults, but it never adds factual claims about the candidate.\n\n### Modes that require `_shared.md` + their mode file\n\nRead `modes\u002F_shared.md` + `modes\u002F_profile.md` (if exists) + `modes\u002F_custom.md` (if exists) + `modes\u002F{mode}.md`\n\nApplies to: `auto-pipeline`, `oferta`, `ofertas`, `pdf`, `text`, `contacto`, `apply`, `pipeline`, `scan`, `batch`\n\n### Standalone modes with profile and custom context\n\nRead `modes\u002F_profile.md` (if exists) + `modes\u002F_custom.md` (if exists) + `modes\u002F{mode}.md`\n\nApplies to: `tracker`, `agent-inbox`, `deep`, `interview-prep`, `interview`, `regional\u002Feu-swe`, `interview\u002Fplan`, `interview\u002Fpractice`, `interview\u002Fdebrief`, `latex`, `latex-tex`, `training`, `project`, `patterns`, `titles`, `upskill`, `followup`, `reply-watch`, `outcome`, `cover`, `email`, `add`, `offer-prep`, `discover`\n\n### Modes delegated to subagent\n\nFor `scan`, `apply` (with Playwright), and `pipeline` (3+ URLs): launch as a worker\u002Fsubagent with the content of `_shared.md` + `_profile.md` (if exists) + `_custom.md` (if exists) + `modes\u002F{mode}.md` injected into the worker prompt. If your CLI exposes an `Agent(...)` primitive, the call looks like this:\n\n```python\nAgent(\n  subagent_type=\"general-purpose\",\n  prompt=\"[output language directive]\\n\\n[content of modes\u002F_shared.md]\\n\\n[content of modes\u002F_profile.md if exists]\\n\\n[content of modes\u002F_custom.md if exists]\\n\\n[content of modes\u002F{mode}.md]\\n\\n[invocation-specific data]\",\n  description=\"career-ops {mode}\"\n)\n```\n\nExecute the instructions from the loaded mode file.\n","# career-ops -- Router\n\ncareer-ops is a multi-CLI job-search command center. The routing below is shared across supported agent CLIs even when the invocation surface differs.\n\n## Project Root Resolution\n\nBefore 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\u002F`. Resolve every path in this router (`modes\u002F`, `config\u002F`, `data\u002F`, 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.\n\n## Invocation Notes\n\n- CLIs with slash-command registration can expose this router as `\u002Fcareer-ops`.\n- In Cursor, this skill lives at `.cursor\u002Fskills\u002Fcareer-ops\u002F` and is auto-discovered; ask for a mode by name, or paste a JD\u002FURL to trigger auto-pipeline.\n- 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 `\u002Fcareer-ops` is unavailable.\n- Headless Codex workers use `codex exec \"prompt\"`.\n- The routing semantics below stay the same regardless of whether the entrypoint is a slash command or a natural-language prompt.\n\nCodex prompt examples that map to the same router semantics:\n\n```text\nEvaluate this JD with career-ops auto-pipeline: https:\u002F\u002Fcompany.com\u002Fjobs\u002F123\nRun the career-ops scan mode and summarize new matches.\nRun the career-ops pipeline mode for data\u002Fpipeline.md.\nRun the career-ops pdf mode for the latest evaluated role.\nRun the career-ops tracker mode and summarize the current statuses.\n```\n\n## Mode Routing\n\nDetermine the mode from `$mode`:\n\n| Input | Mode |\n|-------|------|\n| (empty \u002F no args) | `discovery` -- Show command menu |\n| JD text or URL (no sub-command) | **`auto-pipeline`** |\n| `oferta` | `oferta` |\n| `ofertas` | `ofertas` |\n| `contacto` | `contacto` |\n| `deep` | `deep` |\n| `interview-prep` | `interview-prep` |\n| `interview` | `interview` |\n| `eu-swe` | `regional\u002Feu-swe` |\n| `eu-fintech` | `regional\u002Feu-fintech` |\n| `interview\u002Fplan` | `interview\u002Fplan` |\n| `interview\u002Fpractice` | `interview\u002Fpractice` |\n| `interview\u002Fdebrief` | `interview\u002Fdebrief` |\n| `pdf` | `pdf` |\n| `text` | `text` |\n| `latex` | `latex` |\n| `latex-tex` | `latex-tex` |\n| `email` | `email` |\n| `add` | `add` |\n| `expand` | `expand` |\n| `training` | `training` |\n| `project` | `project` |\n| `tracker` | `tracker` |\n| `agent-inbox` | `agent-inbox` |\n| `inbox` | `agent-inbox` |\n| `pipeline` | `pipeline` |\n| `apply` | `apply` |\n| `scan` | `scan` |\n| `discover` | `discover` |\n| `batch` | `batch` |\n| `patterns` | `patterns` |\n| `offer-prep` | `offer-prep` |\n| `titles` | `titles` |\n| `upskill` | `upskill` |\n| `followup` | `followup` |\n| `reply-watch` | `reply-watch` |\n| `outcome` | `outcome` |\n| `interview-redflag` | `interview-redflag` |\n| `update` | `update` |\n| `cover` | `cover` |\n\n**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`.\n\nIf `$mode` is not a sub-command AND doesn't look like a JD, show discovery.\n\n---\n\n## Output Language Directive\n\nBefore executing any mode, read `config\u002Fprofile.yml` if it exists and resolve:\n\n- `language.output` → ISO language code for human-facing output. Default: `en`.\n- `language.modes_dir` → optional market-mode directory. This controls market vocabulary and local evaluation rules only.\n\nInject this directive after loading the mode instructions and before producing any user-visible content:\n\n> 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, keep the market logic but explain terms in `{language.output}` when needed.\n\n`language.output` is authoritative for prose. `modes_dir` is market context; it must not force the prose language.\n\n---\n\n## Discovery Mode (no arguments)\n\nIf your CLI supports `\u002Fcareer-ops`, show this menu. In Codex, surface the same options in plain text and map the requested mode the same way.\n\nConcrete equivalents for Codex prompt-driven sessions:\n\n```text\n\u002Fcareer-ops {JD}           ↔ \"Evaluate this JD with career-ops auto-pipeline: {JD or URL}\"\n\u002Fcareer-ops scan           ↔ \"Run the career-ops scan mode and summarize new matches.\"\n\u002Fcareer-ops pipeline       ↔ \"Run the career-ops pipeline mode for data\u002Fpipeline.md.\"\n\u002Fcareer-ops pdf            ↔ \"Run the career-ops pdf mode for the latest evaluated role.\"\n\u002Fcareer-ops email          ↔ \"Run the career-ops email mode for the latest evaluated role.\"\n\u002Fcareer-ops tracker        ↔ \"Run the career-ops tracker mode and summarize the current statuses.\"\n```\n\nShow this menu:\n\n```\ncareer-ops -- Command Center\n\nAvailable commands:\n  \u002Fcareer-ops {JD}      → AUTO-PIPELINE: evaluate + report + PDF + tracker (paste text or URL)\n  \u002Fcareer-ops pipeline  → Process pending URLs from inbox (data\u002Fpipeline.md)\n  \u002Fcareer-ops oferta    → Evaluation only A-F (no auto PDF)\n  \u002Fcareer-ops ofertas   → Compare and rank multiple offers\n  \u002Fcareer-ops contacto  → LinkedIn power move: find contacts + draft message\n  \u002Fcareer-ops deep      → Deep research prompt about company\n  \u002Fcareer-ops interview-prep → Generate company-specific interview prep doc\n  \u002Fcareer-ops interview    → Interactive profile\u002FCV onboarding interview\n  \u002Fcareer-ops eu-swe    → Calibrate a European SWE application before CV\u002Fapply\u002Finterview\n  \u002Fcareer-ops eu-fintech → Scan 21 EU fintech portals for Product Manager roles (zero-token)\n  \u002Fcareer-ops interview\u002Fplan → Time-blocked prep plan for an upcoming interview\n  \u002Fcareer-ops interview\u002Fpractice → Practice interview, one question at a time with feedback\n  \u002Fcareer-ops interview\u002Fdebrief → Post-interview debrief: close gaps, predict next round\n  \u002Fcareer-ops pdf       → PDF only, ATS-optimized CV\n  \u002Fcareer-ops text      → Tailored markdown CV (mirrors cv.md, no PDF)\n  \u002Fcareer-ops latex     → Export CV as LaTeX\u002FOverleaf .tex\n  \u002Fcareer-ops latex-tex → Tailor your own resume.tex in place (opt-in; cv.md stays default)\n  \u002Fcareer-ops cover     → Cover letter: standalone JD paste or \u002Fcareer-ops cover {slug}\n  \u002Fcareer-ops email     → Formal application email draft (draft-only; never sends, submits, or clicks)\n  \u002Fcareer-ops add       → Add a project\u002Fpaper\u002Frole to your CV (fetch + preview + confirm)\n  \u002Fcareer-ops expand    → Auto-discover and add missing competencies from profile links\n  \u002Fcareer-ops training  → Evaluate course\u002Fcert against North Star\n  \u002Fcareer-ops project   → Evaluate portfolio project idea\n  \u002Fcareer-ops tracker   → Application status overview\n  \u002Fcareer-ops agent-inbox → Queue\u002Fdrain requests for the next session (data\u002Fagent-inbox.md)\n  \u002Fcareer-ops apply     → Live application assistant (reads form + generates answers)\n  \u002Fcareer-ops scan      → Scan portals and discover new offers\n  \u002Fcareer-ops discover  → Resolve a company list to scannable ATS boards + append to portals.yml (zero-token)\n  \u002Fcareer-ops batch     → Batch processing with parallel workers\n  \u002Fcareer-ops patterns  → Analyze rejection patterns and improve targeting\n  \u002Fcareer-ops offer-prep → Read a received offer\u002Fcontract with the candidate: clause walk + lawyer questions (not legal advice)\n  \u002Fcareer-ops titles    → Suggest adjacent job titles from your CV to broaden the search\n  \u002Fcareer-ops upskill   → Aggregate skill-gap analysis from your evaluated reports\n  \u002Fcareer-ops followup  → Follow-up cadence tracker: flag overdue, generate drafts\n  \u002Fcareer-ops outcome   → Record application outcome & archive artifacts\n  \u002Fcareer-ops update    → Update career-ops system files with diff preview + compat check\n\nInbox: add URLs to data\u002Fpipeline.md → \u002Fcareer-ops pipeline\nOr paste a JD directly to run the full pipeline.\n```\n\n---\n\n## Context Loading by Mode\n\nAfter determining the mode, load the necessary files before executing:\n\nIf `modes\u002F_custom.md` exists, read it after `modes\u002F_profile.md` and before the selected mode file. It contains user house rules and procedural preferences. It may override workflow\u002Fstyle defaults, but it never adds factual claims about the candidate.\n\n### Modes that require `_shared.md` + their mode file\n\nRead `modes\u002F_shared.md` + `modes\u002F_profile.md` (if exists) + `modes\u002F_custom.md` (if exists) + `modes\u002F{mode}.md`\n\nApplies to: `auto-pipeline`, `oferta`, `ofertas`, `pdf`, `text`, `contacto`, `apply`, `pipeline`, `scan`, `batch`\n\n### Standalone modes with profile and custom context\n\nRead `modes\u002F_profile.md` (if exists) + `modes\u002F_custom.md` (if exists) + `modes\u002F{mode}.md`\n\nApplies to: `tracker`, `agent-inbox`, `deep`, `interview-prep`, `interview`, `regional\u002Feu-swe`, `interview\u002Fplan`, `interview\u002Fpractice`, `interview\u002Fdebrief`, `latex`, `latex-tex`, `training`, `project`, `patterns`, `titles`, `upskill`, `followup`, `reply-watch`, `outcome`, `cover`, `email`, `add`, `offer-prep`, `discover`\n\n### Modes delegated to subagent\n\nFor `scan`, `apply` (with Playwright), and `pipeline` (3+ URLs): launch as a worker\u002Fsubagent with the content of `_shared.md` + `_profile.md` (if exists) + `_custom.md` (if exists) + `modes\u002F{mode}.md` injected into the worker prompt. If your CLI exposes an `Agent(...)` primitive, the call looks like this:\n\n```python\nAgent(\n  subagent_type=\"general-purpose\",\n  prompt=\"[output language directive]\\n\\n[content of modes\u002F_shared.md]\\n\\n[content of modes\u002F_profile.md if exists]\\n\\n[content of modes\u002F_custom.md if exists]\\n\\n[content of modes\u002F{mode}.md]\\n\\n[invocation-specific data]\",\n  description=\"career-ops {mode}\"\n)\n```\n\nExecute the instructions from the loaded mode file.\n",{"name":5,"license":15,"arguments":24,"description":7,"argument-hint":25,"user-invocable":26,"user_invocable":26},"mode","[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 | interview\u002Fplan | interview\u002Fpractice | interview\u002Fdebrief | interview-redflag | patterns | offer-prep | titles | upskill | followup | reply-watch | outcome | update]",true,"dev","43ddf82aded0870549685e5df8dceb70bf42a4c2","old\u002Fsantifer-career-ops-agents-skills-career-ops-skill-md",1,"https:\u002F\u002Fgithub.com\u002Fxs3curity\u002Fskillguard-action-test","https:\u002F\u002Fgithub.com\u002Fxs3curity","security engineer","2026-09-01 00:39:28",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":26},[37,40,43],{"tool":38,"command":39},"npx","npx skills add xs3curity\u002Fskillguard-action-test --skill career-ops",{"tool":41,"command":42},"bunx","bunx skills add xs3curity\u002Fskillguard-action-test --skill career-ops",{"tool":44,"command":45},"pnpm","pnpm dlx skills add xs3curity\u002Fskillguard-action-test --skill career-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fxs3curity\u002Fskillguard-action-test\u002Fblob\u002Fdev\u002Fold\u002Fsantifer-career-ops-agents-skills-career-ops-skill-md\u002FSKILL.md",[],[49,58,66,73,80,87],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":54,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7BNDGBAMKWZJRG5QAH7JGK1","mcp-apps-builder","**MANDATORY for ALL MCP server work** - mcp-use framework best practices and patterns.\n\n**READ THIS FIRST** before any MCP server work, including:\n- Creating new MCP servers\n- Modifying existing MCP servers (adding\u002Fupdating tools, resources, prompts, widgets)\n- Debugging MCP server issues or errors\n- Reviewing MCP server code for quality, security, or performance\n- Answering questions about MCP development or mcp-use patterns\n- Making ANY changes to server.tool(), server.resource(), server.prompt(), or widgets\n\nThis skill contains critical architecture decisions, security patterns, and common pitfalls.\nAlways consult the relevant reference files BEFORE implementing MCP features.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fxs3curity\u002Fskillguard-action-test\u002Fblob\u002Fdev\u002Fold\u002Fshubhamsaboo-awesome-llm-apps-generative-ui-agents-ai-mcp-app-builder-apps-mcp-use-server-agent-skills-mcp-apps-builder-skill-md\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fxs3curity\u002Fskillguard-action-test\u002Fblob\u002Fdev\u002Fold\u002Fshubhamsaboo-awesome-llm-apps-generative-ui-agents-ai-mcp-app-builder-apps-mcp-use-server-agent-skills-mcp-apps-builder-skill-md\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":62,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7BNDBAK4CH7F5QF3HCW90FD","chatgpt-app-builder","DEPRECATED: This skill has been replaced by `mcp-app-builder`.\nCheck if `mcp-app-builder` is available in the skills folder. If not, install it:\n`npx skills install mcp-use\u002Fmcp-use --skill mcp-app-builder`\nUse `mcp-app-builder` instead of this skill.\n\nBuild ChatGPT apps with interactive widgets using mcp-use and OpenAI Apps SDK.\nUse when creating ChatGPT apps, building MCP servers with widgets, defining React widgets,\nworking with Apps SDK, or when user mentions ChatGPT widgets, mcp-use widgets, or Apps SDK development.","https:\u002F\u002Fgithub.com\u002Fxs3curity\u002Fskillguard-action-test\u002Fblob\u002Fdev\u002Fold\u002Fshubhamsaboo-awesome-llm-apps-generative-ui-agents-ai-mcp-app-builder-apps-mcp-use-server-agent-skills-chatgpt-app-builder-skill-md\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fxs3curity\u002Fskillguard-action-test\u002Fblob\u002Fdev\u002Fold\u002Fshubhamsaboo-awesome-llm-apps-generative-ui-agents-ai-mcp-app-builder-apps-mcp-use-server-agent-skills-chatgpt-app-builder-skill-md\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7BND3E7T2VTBFM95V6DTFQ8","thinking-out-loud","A contract for what the agent does when a long, messy, stream-of-consciousness ramble arrives (usually voice dictation): act on nothing until the echo brief is approved. The echo audits the entire transfer, mission, locked decisions and constraints, open questions, flips and parked tangents, with the model's inferences and guesses quarantined away from the user's own phrasing, so the user verifies what the model believes, not just what it doubts. Use when the user says \"let me think out loud\" or wants to ramble a bit before building anything, when a message opens with a speech-to-text preamble like \"switching to voice, sorry for typos\", when input is a long weakly punctuated stream with restarts and mid-message reversals (\"actually no, wait, scrap that idea entirely\"), or when the user asks to be interviewed about a fuzzy half-formed idea. Includes an optional capture mode for rambles spread across several messages and an optional targeted interview.","https:\u002F\u002Fgithub.com\u002Fxs3curity\u002Fskillguard-action-test\u002Fblob\u002Fdev\u002Fold\u002Fshubhamsaboo-awesome-llm-apps-agent-skills-thinking-out-loud-skill-md\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7BNCZA24EY6B9D6BNQGG0VT","scope-creep-detector","Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad pull requests, changes that grew beyond a fix, dependency additions, public API renames, config or CI edits, oversized hunks, and formatting-only files. Use when the user asks whether a change grew beyond the fix, a PR is too broad, or what unrelated stuff they touched, and wants keep, split, or justify guidance. Operates locally and offline.","https:\u002F\u002Fgithub.com\u002Fxs3curity\u002Fskillguard-action-test\u002Fblob\u002Fdev\u002Fold\u002Fshubhamsaboo-awesome-llm-apps-agent-skills-scope-creep-detector-skill-md\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7BNCT47CZHQS68CMD9JEZVX","project-graveyard","Scans the developer's machine for dead side projects, autopsies each one from its git history (died at the payments wall, killed by a newer project, finished but never shipped), surfaces their personal death patterns, and picks the corpse most worth resurrecting — then helps ship it. Use when the user mentions abandoned, unfinished, or old side projects, asks \"what should I finish\", wants to revive or resurrect a project, says \"run the graveyard\", wonders why they never finish anything, or is about to start a new project that sounds like one they already built. Runs entirely locally.","https:\u002F\u002Fgithub.com\u002Fxs3curity\u002Fskillguard-action-test\u002Fblob\u002Fdev\u002Fold\u002Fshubhamsaboo-awesome-llm-apps-agent-skills-project-graveyard-skill-md\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7BNCMBHV66QM01QQWE0HGNP","dependency-doctor","Checks requirements.txt, pyproject.toml, and package.json dependency manifests for surface-level direct-dependency footguns: standard-library shadowing pins, abandoned backports, unpinned dependencies, and obvious intra-manifest conflicts, plus opt-in PyPI yanked releases. Use when the user asks to check a manifest for dependency problems, asks why dependencies won't install or whether anything is wrong with their dependencies, wants a dependency autopsy, or suspects dependency manifest rot. Runs offline by default as a local tool for the user's own project, not repository CI.","https:\u002F\u002Fgithub.com\u002Fxs3curity\u002Fskillguard-action-test\u002Fblob\u002Fdev\u002Fold\u002Fshubhamsaboo-awesome-llm-apps-agent-skills-dependency-doctor-skill-md\u002FSKILL.md",[],[]]