From career-navigator
Analyzes application outcome data to find what's working and what isn't. Cross-references tracker history with artifact performance to update ExperienceLibrary weights and surface search_performance signals. Invokes the analyst agent.
npx claudepluginhub tmargolis/career-navigator --plugin career-navigatorThis skill uses the workspace's default tool permissions.
Invoke the `analyst` agent to run an outcome pattern analysis on the user's application history.
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.
Invoke the analyst agent to run an outcome pattern analysis on the user's application history.
Read {user_dir}/CareerNavigator/tracker.json. If the applications array is empty or has fewer than 3 entries with a resolved outcome (phone_screen, interview, offer, rejected, or inactive):
"You don't have enough outcome data yet for pattern analysis — I need at least a few applications with known results. Keep logging updates via
/career-navigator:track-applicationand run this again once you have more history."
Otherwise, proceed.
Hand off to the analyst agent with:
CareerNavigator/tracker.jsonartifacts-index.jsonCareerNavigator/ExperienceLibrary.jsonThe agent will:
performance_weights in CareerNavigator/ExperienceLibrary.jsonweight_update_log entry for each changesearch_performance summary to tracker.jsonAfter the agent completes, report what changed:
Pattern analysis complete.
ExperienceLibrary weights updated
{n} unit(s) increased — {role titles, brief rationale}
{n} unit(s) decreased — {role titles, brief rationale}
{n} unit(s) unchanged (insufficient data)
Search performance summary written to tracker.json
Top converting role types: {list}
Top converting industries: {list}
Signals to avoid: {list}
Data confidence: {Preliminary / Directional / Moderate / High} ({n} applications with outcomes)
If weights could not be updated for any unit due to insufficient data, note it. Do not suppress this — the user should know when the dataset is too small to support a change.
"Run
/career-navigator:reportfor the full analyst report, or/career-navigator:tailor-resumeto use the updated weights in your next resume."