From career-navigator
Surfaces only critical, time-sensitive notifications when the user begins a session or runs this skill on a cadence they configured in Cowork. Routine summaries belong in daily-schedule.
npx claudepluginhub tmargolis/career-navigator --plugin career-navigatorThis skill uses the workspace's default tool permissions.
Run when the user opens a new Cowork session with Career Navigator, **or** when they have scheduled this skill via Cowork **`/schedule`** (optional — for tighter proactive critical checks).
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Builds scalable data pipelines, modern data warehouses, and real-time streaming architectures using Spark, dbt, Airflow, Kafka, and cloud platforms like Snowflake, BigQuery.
Builds production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. For data pipelines, workflow orchestration, and batch job scheduling.
Run when the user opens a new Cowork session with Career Navigator, or when they have scheduled this skill via Cowork /schedule (optional — for tighter proactive critical checks).
Host integration: Claude Cowork’s SessionStart hook (see hooks/hooks.json) injects hooks/context/session-start.md so this workflow is explicitly requested at session open. If the user invokes this skill manually without that hook, follow the same steps below.
Manual fallback: In environments where the SessionStart hook does not auto-fire reliably, run /career-navigator:focus-career at the start of the task/session.
This skill is the critical-only counterpart to daily-schedule. It does not replace the daily digest.
{user_dir} and core filesLook at the current working directory and any user-provided path. Use that as {user_dir}.
Check for:
{user_dir}/CareerNavigator/profile.md{user_dir}/CareerNavigator/ExperienceLibrary.json{user_dir}/CareerNavigator/tracker.json{user_dir}/CareerNavigator/artifacts-index.jsonIf these are missing, treat as first run and output:
Welcome to Career Navigator
Run
/career-navigator:launchto initialize yourCareerNavigatordata files and enable automation.
Read {user_dir}/CareerNavigator/tracker.json.
Only surface critical notifications:
Imminent offer deadline
status: "offer" and offer.deadline within the next 24 hours.{user_dir}/CareerNavigator/offer-context-{application_id}.json is
not present for that application, label the critical reason as:
"Offer evaluation due (run /career-navigator:evaluate-offer)."Imminent follow-up deadline
follow_up_date equal to today.Meeting today with no prep logged
daily-schedule §3.1: any stage_history row with date = today and stage (case-insensitive) containing any of: interview, recruiter, phone screen, phone_screen, hiring manager, hm , hm interview, technical, panel, onsite, executive, final round, final interview.notes[] entry in the last 48 hours has text starting with [prep].[prep] note in 48h → critical (suggest day-of brief + deep prep).Do not output full pipeline digest, overdue rollups, or artifact counts here. Those belong to daily-schedule.
If no critical items:
Career Navigator — Session Start: no critical alerts right now.
If critical items exist:
**Career Navigator — Critical Alerts** [{today}]
- {Company} — {Role}: {critical reason} ({time remaining})
- {Company} — {Role}: {critical reason} ({time remaining})
After listing alerts, add one action line:
Run
/career-navigator:track-applicationor/career-navigator:follow-upto update next steps; for same-day interviews use/career-navigator:morning-briefor/career-navigator:daily-schedule(pre-interview subsection) and/career-navigator:prep-interviewfor full prep (or/career-navigator:evaluate-offerif an offer evaluation due item appeared).