Full-lifecycle job search co-pilot with persistent memory. Captures your preferences, finds matching jobs via web search, researches companies, tailors resumes and cover letters, drafts outreach to hiring managers, preps you for interviews, helps negotiate offers, and tracks your entire pipeline. Trigger whenever someone mentions job hunting, career change, finding a new role, job applications, interview prep, salary negotiation, resume help, LinkedIn outreach to recruiters, or anything related to switching jobs. Also trigger on phrases like 'I want to leave my company', 'looking for new opportunities', 'help me find a job', 'I have an interview at', 'got an offer from', 'should I take this job', or 'update my resume'. This skill should be used proactively even when the user doesn't explicitly say 'job search' — if they mention companies they'd like to work at, ask about salaries, or talk about career moves, this skill is relevant.
Manages the entire job search process from finding roles to negotiating offers with persistent memory and proactive assistance.
npx claudepluginhub gmanchanda31/job-search-pluginThis skill inherits all available tools. When active, it can use any tool Claude has access to.
assets/pipeline.htmlreferences/application-toolkit.mdreferences/intake-questions.mdreferences/interview-prep.mdreferences/job-discovery.mdreferences/negotiation.mdscripts/analytics.pyscripts/briefing.pyscripts/export_materials.pyscripts/init.pyscripts/match_score.pyscripts/memory_sync.pyscripts/pipeline.pyYour personal career agent with long-term memory. Handles everything from finding roles to negotiating offers, and remembers context across sessions.
Working Directory/
├── JOBSEARCH.md ← Profile + preferences (hot cache, loaded every session)
├── PIPELINE.md ← Opportunity tracker (loaded every session)
├── CLAUDE.md ← Memory hot cache (top companies, contacts, terms)
├── pipeline.html ← Visual Kanban dashboard
└── memory/ ← Deep storage (loaded on demand)
├── glossary.md ← Decoder ring: companies, contacts, acronyms
├── companies/ ← Cached research per company (company-slug.md)
├── contacts/ ← Recruiter/HM profiles + interaction history
├── applications/ ← Tailored materials per application
│ └── company-role/
│ ├── resume_tailored.docx
│ ├── cover_letter.md
│ ├── fit_analysis.md
│ ├── outreach_email.md
│ ├── interview_prep.md
│ └── negotiation_strategy.md
└── analytics/ ← Tracking patterns over time
├── applications.md
├── interviews.md
├── offers.md
└── briefings.md
| Command | What It Does |
|---|---|
/job-search:start | Run intake interview, set up profile, pipeline, and memory |
/job-search:find | Search for matching roles across the web |
/job-search:research [company] | Deep-dive a target company |
/job-search:apply [url] | Analyze posting, tailor resume, draft cover letter + outreach |
/job-search:prep [company] | Interview prep — questions, STAR answers, research |
/job-search:negotiate [company] | Salary research and negotiation scripts |
/job-search:status | Pipeline dashboard — what needs attention |
/job-search:briefing | Weekly digest — new matches, news, follow-ups due |
/job-search:update | Sync memory, triage stale items, refresh context |
See commands/ for detailed instructions per command.
Tier 1: Hot Cache (loaded every session)
Three files loaded automatically to provide instant context:
Tier 2: Deep Storage (loaded on demand)
_archived_ if no longer activeDetailed methodology docs loaded on demand by specific commands:
| Reference | Used By | Purpose |
|---|---|---|
references/intake-questions.md | /start | Conversational intake framework |
references/job-discovery.md | /find | Search templates, match scoring, de-dup |
references/application-toolkit.md | /apply | JD analysis, resume tailoring, outreach |
references/interview-prep.md | /prep | STAR prep, question banks, day-of checklist |
references/negotiation.md | /negotiate | Salary research, scripts, Indian CTC |
Automation utilities called by commands:
| Script | Purpose |
|---|---|
scripts/init.py | Initialize workspace, create files and directories |
scripts/match_score.py | Score jobs against profile (0-100 with breakdown) |
scripts/pipeline.py | Pipeline CRUD: status, add, move, followups, export |
scripts/briefing.py | Generate weekly briefing from pipeline state |
scripts/export_materials.py | Package application materials for a company |
scripts/memory_sync.py | Rebuild CLAUDE.md hot cache from deep storage |
scripts/analytics.py | Compute conversion rates and time-in-stage stats |
The skill should be proactive, not just reactive:
At the beginning of every session where job search context is relevant:
CLAUDE.md (hot cache)PIPELINE.md for urgent items (offers expiring, interviews this week)Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.