agentleFS
Sign inStart free
aksheywaksheyw/career-command-center-template/skills/interview/SKILL.md

interview

Skill1 starsChanged 4 months agoMITView on GitHub

Full interview prep for a specific company. Argument: [company name] [optional: role title]

94 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use fetch-library-docs, contributor and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Rehan-Ul-HaqSkill

    fetch-library-docs

    Fetches official documentation for external libraries and frameworks (React, Next.js, Prisma, FastAPI, Express, Tailwind, MongoDB, etc.) with 60-90% token savings via content-type filtering. Use this skill when implementing features using library APIs, debugging library-specific errors, troubleshooting configuration issues, installing or setting up frameworks, integrating third-party packages, upgrading between library versions, or looking up correct API patterns and best practices. Triggers automatically during coding work - fetch docs before writing library code to get correct patterns, not after guessing wrong.

    Also in 4 projects that use this

  • NimbleBrainIncSkill

    contributor

    Get started contributing to NimbleBrain open source — find an integration to build, set up your environment, propose an idea, or check on your work. Use when onboarding as a contributor. Triggers include "I'm a new contributor", "what should I build", "show me open issues", "file an issue".

    Also in 3 projects that use this

  • mjunaidcaSkill

    browsing-with-playwright

    Browser automation using Playwright MCP. Navigate websites, fill forms, click elements, take screenshots, and extract data. Use when tasks require web browsing, form submission, web scraping, UI testing, or any browser interaction. NOT when only fetching static content (use curl/wget instead).

    Also in 4 projects that use this

  • qa-amanSkill

    teach-me

    Teach a topic, video, article, codebase change, spec, or transcript until the user demonstrably understands it, using staged instruction, a running checklist doc, and quizzes. Use whenever the user says "teach me", "explain this in detail", "help me understand X", "/teach-me", "walk me through this", "I want to learn X", "understand this deeply", or pastes a YouTube URL, article, paper, PR, or spec and asks to understand it rather than summarize it. Also use when the user wants study notes or raw material from a source they are learning. Do NOT use for a quick factual lookup, a summary request, or when the user just wants the answer.

    Also in 8 projects that use this

  • trebaudSkill

    find-unknowns

    Workflow for surfacing a task's unknowns before, during, and after implementation — blind spot pass, brainstorm/prototype, interview, references, implementation plan, deviation notes, quiz. Use when starting work in an unfamiliar domain or codebase, when a task feels underspecified, when the user says "find my unknowns", "blindspot pass", "what am I missing", "help me scope this", or when a long task came back wrong.

    Also in 3 projects that use this

  • donatassimkusSkill

    offer

    Offer design, pricing strategy, and business model architecture. Invoke when asked about making an offer better, pricing a product or service, naming an offer, raising prices, generating fast cash, increasing lifetime value, finding the right customer, qualifying buyers, or designing a business model where customers pay for their own acquisition. Use when someone says their offer isn't converting, they need to charge more, they want to add bonuses or guarantees, or they need a money model for their business.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 80 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read all of these:

    line 10
  2. Very specific:

    Use story-bank-index.md to select stories by company type.

    line 35
  3. Distinctive:

    After generating prep, check if any stories were improvised or if gaps were exposed:

    line 88
  4. Very specific:

    If a new story was created → suggest adding it to star-stories.md with full STAR format

    line 90
  5. Very specific:

    If no story fit a requirement → add the gap to the GAP TRACKER in story-bank-index.md

    line 91
  6. Distinctive:

    Update the company-type priority table if story selection order should change

    line 92

“Common” is measured: kept by at least 6 in 10 of the 80 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

You are preparing the user for a director-level PM interview. The user has provided a company name and optionally a role title.

STEP 1: Read required files

Read all of these:

  • ${CLAUDE_PLUGIN_ROOT}/references/YOUR_PROFILE.md — the user's verified background
  • ${CLAUDE_PLUGIN_ROOT}/skills/resume-customizer/SKILL.md — company-type strategies, interview angles
  • ${CLAUDE_PLUGIN_ROOT}/skills/resume-customizer/references/star-stories.md — all the user's STAR stories
  • ${CLAUDE_PLUGIN_ROOT}/skills/resume-customizer/references/story-bank-index.md — cross-indexed story selection by company type
  • ${CLAUDE_PLUGIN_ROOT}/skills/resume-customizer/references/interview-prep.md — frameworks, questions, pitch
  • ${CLAUDE_PLUGIN_ROOT}/skills/resume-customizer/references/career-tools.md — 90-day plans, salary strategy

STEP 2: Identify company type

Based on the company name, determine:

  • Company Type: AI / Consumer Scale / Enterprise / B2B / Fintech / Telco
  • Interview focus: what they will care most about
  • Fit level: how strong the match is

STEP 3: Output complete prep pack

2-MINUTE PITCH (company-customized)

Adapt the standard pitch template from interview-prep.md to reference the specific company in the closing line. Pull the user's actual achievements from YOUR_PROFILE.md.

TOP 4 STAR STORIES FOR THIS COMPANY

Use story-bank-index.md to select stories by company type. Cross-reference with star-stories.md for full story details.

For each story, provide:

  • Story name
  • Why it is relevant to this specific company
  • The 60-second version (crisp retelling)
  • Watch out for (common stumbles in telling this story)

Also include one failure story and why it works for this company.

QUESTIONS THEY WILL LIKELY ASK

10 specific questions based on the JD / company type, with guidance on how to answer each:

  • 3 behavioral (use STAR stories)
  • 3 product / strategy (use company-type interview angle from SKILL.md)
  • 2 leadership (team building, stakeholder management)
  • 1 failure (use one of the user's failure stories)
  • 1 "why this company" (prepare specific answer)

COMPANY-TYPE INTERVIEW ANGLE

Pull the relevant interview angle from SKILL.md and expand it for this specific company.

90-DAY PLAN

Pull the relevant 90-day plan from career-tools.md and customize for this company. Make it specific — reference their actual products and challenges if known.

QUESTIONS TO ASK INTERVIEWER

5 strong questions that signal director-level thinking. Pull from interview-prep.md and adapt for this company. Include at least one red-flag probing question.

SALARY PREP

From career-tools.md:

  • Target range for this company type
  • Response to "what are you making now?"
  • Response to "what are your salary expectations?"
  • Key negotiation lever (from user's profile — e.g., illiquid equity)

PRE-INTERVIEW CHECKLIST

  • Review 2-minute pitch out loud
  • Practice all 4 STAR stories timed (2 min each max)
  • Research company news from last 30 days
  • Prepare 3 questions to ask
  • Review your resume (what they saw)
  • Know salary range and be ready to hold it

STEP 4: Update story bank

After generating prep, check if any stories were improvised or if gaps were exposed:

  • If a new story was created → suggest adding it to star-stories.md with full STAR format
  • If no story fit a requirement → add the gap to the GAP TRACKER in story-bank-index.md
  • Update the company-type priority table if story selection order should change

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.

Check your setup, free