From career-navigator
Lists all generated artifacts in the artifact inventory with metadata: type, date created, target role and company, ATS score if available, and linked application outcome if known. Fires when the user asks to see their generated documents or artifact history. Also invocable via /career-navigator:list-artifacts.
npx claudepluginhub tmargolis/career-navigator --plugin career-navigatorThis skill uses the workspace's default tool permissions.
Display the user's artifact inventory in a readable format.
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.
Display the user's artifact inventory in a readable format.
Read {user_dir}/CareerNavigator/artifacts-index.json. If the file does not exist or the artifacts array is empty:
"No artifacts yet. Run
/career-navigator:tailor-resumefor a resume, or/career-navigator:content-suggestand ask for a full post draft to save a LinkedIn draft to disk."
Read {user_dir}/CareerNavigator/tracker.json. For each artifact, check whether it appears in any application's artifacts[] array. If so, note the application's current status — this lets the user see which resumes and cover letters are attached to live applications and what outcome (if any) they produced.
Group artifacts by type: resumes first, then cover letters, then linkedin_post (saved post drafts from writer), then any other types. Within each group, sort by date_created descending (most recent first).
Format for each artifact:
{n}. {filename}
Target: {Company} — {Role} (or "Base / unattached" if no target; for linkedin_post use "—" or notes topic)
Created: {date_created}
ATS score: {ats_score}/100 (omit if not available or not applicable)
Used in: {Company — Role, status: {status}} (omit if not linked to any application)
For type: "linkedin_post", omit ATS and usually Used in; show notes or path if helpful so the user can find the draft on disk.
Summary line at the top (before the list):
Artifacts: {total_resume_count} resume(s), {total_cover_letter_count} cover letter(s), {total_linkedin_post_count} LinkedIn post draft(s)
After the list, show relevant actions based on what's there:
"Some resumes aren't linked to an application yet — run
/career-navigator:track-applicationto log them."
"No cover letter on file for some roles — run
/career-navigator:cover-letterto generate one."