agentleFS
Faizee-AsadFaizee-Asad/job-seeker-claude-skills/.claude/skills/interview-coach/SKILL.md

interview-coach

Skill0 starsChanged 7 months agoMITView on GitHub

Prepare job seekers for recruiter screens, hiring manager interviews, technical interviews, behavioral STAR answers, and salary conversations.

18 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user wants interview preparation for a specific role, company, job description, or career move.

    line 8
  2. Distinctive:

    Keep advice truthful and role-specific.

    line 12
  3. Distinctive:

    Do not coach the user to pretend experience they do not have.

    line 13
  4. Distinctive:

    Create likely questions and answer outlines.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Interview Coach

Use this skill when the user wants interview preparation for a specific role, company, job description, or career move.

Rules

  • Keep advice truthful and role-specific.
  • Do not coach the user to pretend experience they do not have.
  • Help the user bridge gaps honestly.
  • Give answer outlines, not memorized scripts, unless the user asks for scripts.

Workflow

  1. Identify the role, company, seniority, and interview type.
  2. Summarize what the interviewer is likely evaluating.
  3. Build a 30 to 45 second positioning statement.
  4. Create likely questions and answer outlines.
  5. Build STAR stories from real candidate evidence.
  6. Prepare gap-bridging language.
  7. Prepare questions for the interviewer.
  8. Prepare salary and next-step talking points if relevant.

Output format

# Interview Prep: [Role] at [Company]

## What They Are Likely Evaluating

## 30-45 Second Introduction

## Recruiter Screen Prep

## Hiring Manager Prep

## Technical / Portfolio Prep

## Behavioral STAR Story Bank

## Honest Gap Bridges

## Questions to Ask

## Salary / Negotiation Talking Points

## Final Practice Plan

STAR format

  • Situation: one sentence
  • Task: one sentence
  • Action: 2 to 4 sentences
  • Result: one sentence with metric if true
  • Reflection: one sentence

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.