← Plugin catalog
Productivity

Career Command Center

Mehmet Riza Arseven v1.3.0+codex.20260715213050

Find, track applications

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Interactive
  • Write

Not specified in the available declarations: limitations, pricing & account requirements.

Onboarding example

Set up Career Command Center.
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 22, 2026. Package observed Nov 21, 2026.

View package source →

Description

From the marketplace listing

Audits career documents, returns cited project-specific questions in a native macOS workspace, organizes job and PhD opportunities, builds role-family master CVs, creates tailored application packages, and keeps configurable Codex searches synchronized. Career documents and application state remain in a workspace chosen by the user.

Language: English · Automatically detected from descriptions.

What changed

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Keywords

Files & skills

File archives

Plugin package51 files · 2.42 MBBrowse files →
Skill instructions
career-command-center9.04 KB

View saved version →

---
name: career-command-center
description: Install, set up, open, diagnose, or operate Career Command Center; manage its job and PhD search automation; audit career evidence; build role-family master CVs; tailor application packages; or sync app search and schedule settings with Codex. Use when the user mentions Career Command Center, targeted career search, the app's setup wizard, its application queue, or its recurring automation.
---

# Career Command Center

Use the bundled app for user input and lifecycle management. Use Codex for evidence auditing, web research, document generation, quality review, and scheduled runs.

`PLUGIN_ROOT` is the plugin directory containing this skill. Scripts live in `PLUGIN_ROOT/scripts`; references live in `PLUGIN_ROOT/references`.

## First Setup

1. Choose a workspace. Prefer the current Codex project when the user wants automation in that project; otherwise use `~/Documents/Career Command Center`.
2. Run:

```bash
python3 PLUGIN_ROOT/scripts/bootstrap_workspace.py WORKSPACE
python3 PLUGIN_ROOT/scripts/install_app.py --workspace WORKSPACE
```

3. Tell the user the app has opened and ask them to complete every wizard step. New setup is deliberately neutral: no role family, country, opportunity type, seniority, CV language, photo policy, or recurring schedule should be assumed. Do not register an automation before `onboarding_completed` is true.
4. When the user returns with `Finish Career Command Center setup`, run `doctor.py WORKSPACE` and read:
   - `Config/command_center_config.json`
   - `Evidence_Bank/intake_answers.md`
   - `references/CV_GENERATION_STANDARD.md`
   - `references/PERSONALIZED_QUESTION_STANDARD.md`
   - `references/WORKSPACE_CONTRACT.md`
5. If evidence blocks and approved masters are missing, begin the evidence foundation before scheduling:
   - Inventory and extract every CV, transcript, certificate, recommendation, report, and project file.
   - Write the verified portion of `Evidence_Bank/Verified_Evidence_Ledger.md` and structured `approved_evidence.json`, keeping unresolved claims out of approved evidence.
   - Identify only unresolved, high-impact gaps that satisfy the personalized-question standard. Do not repeat generic onboarding questions or ask for facts already stated clearly in a source.
   - Create a temporary generation payload and run `question_cli.py --workspace WORKSPACE generate --input PAYLOAD`. Every question must cite the source path, locator, and ambiguity that triggered it.
   - Run `question_cli.py --workspace WORKSPACE summary`.
   - Treat `audit_status: needs_refresh` exactly like a new evidence pass. Re-audit the newly imported or changed material and run question generation even when the result is an empty question list.
6. If the summary reports `needs_user_answer` greater than zero, tell the user that personalized questions are ready in the app's **Questions** workspace. Do not dump the same questionnaire into chat, build final master CVs, or activate automation yet. The app's **Review in Codex** action will bring the user back after responses are saved.
7. When the user asks to review saved evidence answers:
   - Read all `answered` and `unable_to_verify` questions and reopen every cited source.
   - Update the verified evidence ledger and `approved_evidence.json` only where the response and source support the claim. Record `unable_to_verify` as a boundary or exclusion.
   - Create a review payload and run `question_cli.py --workspace WORKSPACE review --input REVIEW_PAYLOAD` with a concise decision note and resulting evidence IDs for every reviewed item.
   - Generate a new cited question only when the response creates a material unresolved ambiguity. Resolve the original first; never silently rewrite an answered question.
   - Run the summary again. If questions remain open or answers await review, return the user to the Questions workspace and stop before master-CV generation.
8. Once no questions need an answer or Codex review, compl

Preview of the first 4,000 characters. Read full instructions →

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
MIT
Package author
Mehmet Riza Arseven
Keywords
See keywords

Declared capabilities

  • Interactive
  • Write

Package observed Nov 21, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 22, 2026 · 00:00 UTC
Collection status
Collected

plugins_6a57e1af43a48191a841ef23dd9db029

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.