career-ops

Plugin career-ops from marketplace career-ops in ahmedyusef9/jobby-share. Commands read from the repo's manifest — 27 days ago.

Skills (25)

• 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.

• qa-agent

  Run a jobby QA round as an agent — drive the real UI against qa/features.yml, record every verdict with evidence, and turn repeatable manual checks into permanent Playwright tests. Use when asked to "run a QA round", "QA the app", "verify the manual matrix", or "automate the manual QA".

• docker-deploy

  Deploy and run jobby only via Docker. Use when starting the app, rebuilding after UI changes, promoting to stage/production, or preparing Kubernetes. Stages: dev, stage, production. Never start host next dev.

• dry-reuse

  Enforce Don't Repeat Yourself (DRY) in jobby web/UI work: extract once, reuse via shared components/helpers, never copy-paste Job info / status / Apply / PDF controls across pages. Use when adding screens, duplicating UI, or wiring Pipeline ↔ Workers role detail.

• github-trace

  Enforce GitHub traceability via the built-in GitHub MCP server (plugin-github-github). Use for milestones, issues, labels, PRs, and TASK_ID. Never use gh CLI or custom sync scripts for GitHub mutations.

• qa-manual-automation

  How to run jobby manual QA — pick the right attended-browser path (Playwright MCP extension, browsermcp, or headed debug Chromium), cover the most cases, and record a ledger verdict before merge. Jobby delta over the upstream .agents/skills/qa-manual-automation skill.

• qa-pass

  Run the BrowserMCP QA gate for a jobby feature — drive the UI per checklist, then record PASS/FAIL with scripts/qa-ship.mjs. Use when asked to "QA", "verify a feature", or "run the QA pass".

• sdlc-report

  Render the formal task and handoff report. Use for bounded delivery, investigation, review, QA, release, cross-agent handoff, status, completion, blocker, or verification reports.

• speckit-analyze

  Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

• speckit-checklist

  Generate a custom checklist for the current feature based on user requirements.

• speckit-clarify

  Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

• speckit-constitution

  Create or update the project constitution from interactive or provided principle inputs.

• speckit-converge

  Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

• speckit-implement

  Execute the implementation plan by processing and executing all tasks defined in tasks.md

• speckit-plan

  Execute the implementation planning workflow using the plan template to generate design artifacts.

• speckit-specify

  Create or update the feature specification from a natural language feature description.

• speckit-tasks

  Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

• speckit-taskstoissues

  Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

• tailscale-serve

  Point Tailscale Serve/Funnel at Jobby Compose. Use when ChatGPT/Claude/Cursor cannot reach the MCP URL, after .ports.yml compose-web changes, or when enabling HTTPS on this machine's *.ts.net name. Backend is always 127.0.0.1:<compose-web>, never 3001.

• ui-e2e

  Automates jobby UI and API smoke tests: BrowserMCP sign-in (fill email and password), click every primary nav/button scenario, and OmniRoute/OpenCode API checks. Use when the user asks to UI-test, e2e, smoke-test the web app, verify buttons, or test via browsermcp / OpenCode / OmniRoute.

• upstream-sync

  Safely pull upstream career-ops changes into jobby, and contribute fixes back. Use when updating, syncing with upstream, resolving a fork conflict, or when a system-layer file needs to change.

• career-ops-plugin-{{NAME}}

  How to use the {{NAME}} plugin and the data it produces.

• career-ops-plugin-apify

  How to scan a job source through an Apify actor as a keyed provider.

• career-ops-plugin-gmail

  How to pull job leads from a Gmail label into the career-ops pipeline.

• career-ops-plugin-notion

  How to mirror the career-ops tracker to a Notion database and read records back as job leads.

Similar plugins