[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79QNEP6Y37H6CWC1GS8640F":3,"skill-same:01M79QNEP6Y37H6CWC1GS8640F":47},{"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":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":46},"01M79QNEP6Y37H6CWC1GS8640F","career-ops",null,"AI job search command center -- evaluate offers, generate CVs, scan portals, track applications","Manmit124\u002Fjob-jarvis","Manmit124","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F112580293?v=4","01M79QNCK5R1RBB9FZK55B2SVQ","Manmit Tiwade","01M79QNCM7RWFXQKHYCPM81R0T",0,"MIT","https:\u002F\u002Fgithub.com\u002FManmit124\u002Fjob-jarvis\u002Fblob\u002Fmain\u002Fcareer-ops\u002F.agents\u002Fskills\u002Fcareer-ops\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: career-ops\ndescription: AI job search command center -- evaluate offers, generate CVs, scan portals, track applications\narguments: mode\nuser_invocable: true\nuser-invocable: true\nargument-hint: \"[scan | deep | pdf | latex | latex-tex | cover | email | add | eu-swe | oferta | ofertas | apply | batch | tracker | agent-inbox | pipeline | contacto | training | project | interview-prep | interview | interview\u002Fplan | interview\u002Fpractice | interview\u002Fdebrief | patterns | offer-prep | titles | upskill | followup | 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## Invocation Notes\n\n- CLIs with slash-command registration can expose this router as `\u002Fcareer-ops`.\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| `interview\u002Fplan` | `interview\u002Fplan` |\n| `interview\u002Fpractice` | `interview\u002Fpractice` |\n| `interview\u002Fdebrief` | `interview\u002Fdebrief` |\n| `pdf` | `pdf` |\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| `batch` | `batch` |\n| `patterns` | `patterns` |\n| `offer-prep` | `offer-prep` |\n| `titles` | `titles` |\n| `upskill` | `upskill` |\n| `followup` | `followup` |\n| `update` | `update` |\n| `cover` | `cover` |\n| `add` | `add` |\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 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 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 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 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`, `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`, `cover`, `email`, `add`, `offer-prep`\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## Invocation Notes\n\n- CLIs with slash-command registration can expose this router as `\u002Fcareer-ops`.\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| `interview\u002Fplan` | `interview\u002Fplan` |\n| `interview\u002Fpractice` | `interview\u002Fpractice` |\n| `interview\u002Fdebrief` | `interview\u002Fdebrief` |\n| `pdf` | `pdf` |\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| `batch` | `batch` |\n| `patterns` | `patterns` |\n| `offer-prep` | `offer-prep` |\n| `titles` | `titles` |\n| `upskill` | `upskill` |\n| `followup` | `followup` |\n| `update` | `update` |\n| `cover` | `cover` |\n| `add` | `add` |\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 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 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 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 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`, `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`, `cover`, `email`, `add`, `offer-prep`\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 | deep | pdf | latex | latex-tex | cover | email | add | eu-swe | oferta | ofertas | apply | batch | tracker | agent-inbox | pipeline | contacto | training | project | interview-prep | interview | interview\u002Fplan | interview\u002Fpractice | interview\u002Fdebrief | patterns | offer-prep | titles | upskill | followup | update]",true,"main","d33163c3cce804cbdbda545367eb6a6f25872882","career-ops\u002F.agents\u002Fskills\u002Fcareer-ops","https:\u002F\u002Fgithub.com\u002FManmit124\u002Fjob-jarvis","https:\u002F\u002Fgithub.com\u002FManmit124","### Hi there, I'm Manmit Tiwade! 👋\r\n","2026-07-26 22:40:34",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":26},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Manmit124\u002Fjob-jarvis --skill career-ops",{"tool":40,"command":41},"bunx","bunx skills add Manmit124\u002Fjob-jarvis --skill career-ops",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Manmit124\u002Fjob-jarvis --skill career-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FManmit124\u002Fjob-jarvis\u002Fblob\u002Fmain\u002Fcareer-ops\u002F.agents\u002Fskills\u002Fcareer-ops\u002FSKILL.md",[],[48,55,62,69],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M79QP1HYMDP6EW4RCZZ1JAHY","career-ops-plugin-notion","How to mirror the career-ops tracker to a Notion database and read records back as job leads.","https:\u002F\u002Fgithub.com\u002FManmit124\u002Fjob-jarvis\u002Fblob\u002Fmain\u002Fcareer-ops\u002Fplugins\u002Fnotion\u002Fskill.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M79QNZ3CNB58DS1SSPSAJ2V0","career-ops-plugin-gmail","How to pull job leads from a Gmail label into the career-ops pipeline.","https:\u002F\u002Fgithub.com\u002FManmit124\u002Fjob-jarvis\u002Fblob\u002Fmain\u002Fcareer-ops\u002Fplugins\u002Fgmail\u002Fskill.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M79QNX1QWBAF6557TXP7JZM6","career-ops-plugin-apify","How to scan a job source through an Apify actor as a keyed provider.","https:\u002F\u002Fgithub.com\u002FManmit124\u002Fjob-jarvis\u002Fblob\u002Fmain\u002Fcareer-ops\u002Fplugins\u002Fapify\u002Fskill.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M79QNVF1A2HNK96PBR53BDTH","career-ops-plugin-{{NAME}}","How to use the {{NAME}} plugin and the data it produces.","https:\u002F\u002Fgithub.com\u002FManmit124\u002Fjob-jarvis\u002Fblob\u002Fmain\u002Fcareer-ops\u002Fplugins\u002F_template\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FManmit124\u002Fjob-jarvis\u002Fblob\u002Fmain\u002Fcareer-ops\u002Fplugins\u002F_template\u002Fskill.md",[],[]]