job-hunt-copilot MCP — Use Cases, Install & Live Demo

Why use it

Key features

Project library as a single source of truth
Per-role resume tailoring without rewriting history
Pitch script generation aligned to role signals
Mock interview mode using role-specific questions
Keeps honesty — edits framing, not facts

Live Demo

What it looks like in practice

job-hunt-copilot-skill.replay ▶ ready

0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "job-hunt-copilot-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/spontaneousai/job-hunt-copilot",
        "~/.claude/skills/job-hunt-copilot"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "job-hunt-copilot-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/spontaneousai/job-hunt-copilot",
        "~/.claude/skills/job-hunt-copilot"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "job-hunt-copilot-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/spontaneousai/job-hunt-copilot",
        "~/.claude/skills/job-hunt-copilot"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "job-hunt-copilot-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/spontaneousai/job-hunt-copilot",
        "~/.claude/skills/job-hunt-copilot"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "job-hunt-copilot-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/spontaneousai/job-hunt-copilot",
        "~/.claude/skills/job-hunt-copilot"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "job-hunt-copilot-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/spontaneousai/job-hunt-copilot",
          "~/.claude/skills/job-hunt-copilot"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add job-hunt-copilot-skill -- git clone https://github.com/spontaneousai/job-hunt-copilot ~/.claude/skills/job-hunt-copilot

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use job-hunt-copilot

Tailor your resume to a specific JD without starting over

👤 Job seekers who send 5+ applications a week ⏱ ~15 min beginner

When to use: You found a role, you have a base resume, you don't want to rewrite from scratch.

Prerequisites

Project library set up — Follow SKILL.md to populate projects.md with detailed project notes once
Skill installed — git clone https://github.com/spontaneousai/job-hunt-copilot ~/.claude/skills/job-hunt-copilot

Flow

Paste the JD

Use job-hunt-copilot. Here's the JD: [...]. Tailor my resume to it using my project library.✓ Copied

→ Resume with bullets reshuffled and reworded to match JD keywords — without inventing experience
Verify honesty

Show me any bullet where the framing is a stretch from my actual project notes.✓ Copied

→ Flags for review, not a clean 'all good'
Export

Save as resume-acme-senior-pm.md and also convert to PDF.✓ Copied

→ File saved with clean filename

Outcome: A tailored resume per role in ~10 minutes, same facts, different emphasis.

Pitfalls

Hallucinated accomplishments — Always use the honesty-check step; your project library is the source of truth

Combine with: filesystem

Generate a 2-minute 'tell me about yourself' pitch for a role

👤 Interviewees preparing for first-round screens ⏱ ~20 min beginner

When to use: You have a screen in 24 hours.

Flow

Align pitch to JD

Use job-hunt-copilot. Write my 2-min pitch for this role [JD]. Emphasize the projects that map to their top 3 requirements.✓ Copied

→ Script with natural flow, not a resume readout
Practice variants

Now give me a 45-second version and a 5-minute version.✓ Copied

→ Three lengths, same core

Outcome: A pitch that sounds like you, tuned to the role.

Pitfalls

Sounding robotic — Read aloud; trim anything that feels LinkedIn-flavored

Run a mock interview for a specific role

👤 Candidates with a real interview soon ⏱ ~45 min intermediate

When to use: You want to rehearse the likely questions.

Flow

Set up the role context

Use job-hunt-copilot. Act as a hiring manager for this role [JD] doing a behavioral interview. Ask me questions one at a time.✓ Copied

→ One question, waits for answer, then probes
Get feedback

After we finish, critique my answers — structure, specificity, signal.✓ Copied

→ Per-answer feedback with improvement hooks

Outcome: A rehearsed set of stories for the interview.

Pitfalls

Mock becomes chummy and doesn't probe — Tell Claude to be skeptical and ask follow-up 'why' questions

Combinations

Pair with other MCPs for X10 leverage

job-hunt-copilot-skill + filesystem

Keep a structured folder per role: JD, resume version, pitch, notes

For every new role, create jobs/<company>/<role>/ with JD, resume, pitch, and interview notes.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call
tailor_resume	JD, base resume, project library	Per role application
pitch_script	JD, focus projects	Before a screen
mock_interview	role type, rounds	Rehearsal
honesty_check	resume draft	After tailoring, before sending

Cost & Limits

What this costs to run

API quota: None
Tokens per call: Modest per role; the library doc is the biggest token cost
Monetary: Free
Tip: Keep projects.md well-organized — smaller, dense entries beat long narratives.

Security

Permissions, secrets, blast radius

Credential storage: None

Data egress: Project library and JDs sent to Claude API

Don't put current-employer confidential information into your project library. Your own accomplishments are fair game; their trade secrets aren't.

Troubleshooting

Common errors and fixes

Tailored resume invents claims

Your project library may be too sparse; expand it so tailoring has real material to pull from

Verify: Open projects.md and check each entry has metrics and details

Pitch sounds LinkedIn-y

Prompt for 'natural spoken words, not buzzwords'; read aloud

Alternatives

job-hunt-copilot vs others

Alternative	When to use it instead	Tradeoff
ChatGPT + manual tailoring	One-off applications	No persistent library; you repeat yourself
Teal / JobScan	Keyword matching only	No narrative tailoring

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills