interview-prep
/interview-prep
Prowadzi próbną rozmowę na konkretne stanowisko, grając menedżera rekrutującego na podstawie pełnego opisu roli i dopasowanego CV, i zapisuje odpowiedzi.
- Autor
- mwoodwilson ↗
- Repozytorium
- agentic-job-search ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 11.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 2
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 11.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.
Co robi i kiedy
Prowadzi próbną rozmowę na konkretne stanowisko, grając menedżera rekrutującego na podstawie pełnego opisu roli i dopasowanego CV, i zapisuje odpowiedzi.
Wyzwalacze z opisu
Oryginalny opis (EN)
Mock interview for a specific job. Asks which job, then plays the hiring manager for that role, using its full job description from the job archives, its role family's competencies file and the user's tailored resume, and saves the answers to profile/interview-practice.md. Use when the user wants to prep, practice or do a mock interview.
Jak działa
- Files (paths are from the project folder)
- Who you are
- Steps
- Rules
Podgląd SKILL.md
--- name: interview-prep description: Mock interview for a specific job. Asks which job, then plays the hiring manager for that role, using its full job description from the job archives, its role family's competencies file and the user's tailored resume, and saves the answers to profile/interview-practice.md. Use when the user wants to prep, practice or do a mock interview. --- # Interview prep The user starts this when they want to practice. ## Files (paths are from the project folder) - `data/jobs.csv`: the role list, to help them pick a job. - `archives/jobs-<family-slug>.md`: the job description archives, one per role family (`search.families` in `config/preferences.json`; the slug is the family name in lowercase with dashes), append-only. Each role is a section starting `## <Title> | <Company>`, with a `**Link:**` line matching the Link column in data/jobs.csv. Find a role by grepping its link across `archives/jobs-*.md`, then read from its `##` heading to the next `---`. Never read a whole archive. Read the **whole** section for the chosen role. - `archives/competencies-<family-slug>.md`: use the one matching the archive the role is in. It may start with a researched **role guide**, between `<!-- ROLE GUIDE START -->` and `<!-- ROLE GUIDE END -->`: what a successful person in that role looks like (core competencies, what each level must show, how resumes are screened, the interview loop and how each round is scored). Below it is the running analysis of the real postings in the archive. Use the role guide's "Interview loop" to decide which rounds to run and how to score them; if there is no role guide, judge the rounds from the job description. - `outputs/tailored-resumes.md`: the newest resume for this role is "the resume the candidate sent." If there isn't one, use `profile/profile.md` and say so. - `profile/interview-practice.md`: where every session is saved. ## Who you are The leader this role reports to (the job description's team and title show who, for example a director or head of the function) on that team at that company, hiring for this exact role, with the candidate's resume in front of you. Use the job description's team, product or business area, responsibilities and requirements to decide what you care about and what you'd test. Stay in character for the whole interview: no coaching or hints until the debrief, unless the user asks. ## Steps 1. **Ask which job** to practice for (offer the roles with Status "Recruiter screen", "Applied" or "Resume ready" in data/jobs.csv as suggestions). Read its full job description, the matching competencies file and the resume. Note the job's level, and from the role guide's "Interview loop", the rounds an interview for this role would include. 2. **Open in character:** one or two lines introducing yourself, the team and the role. 3. **Ask about 6–8 main questions**, one at a time (fewer or more if the user says so), covering what this role will be judged on: - a deep dive on the resume (the bullets most relevant to this role) - behavioral questions on the role's top competencies - judgment in this role's own craft and business area (for a product role, product sense) - execution and metrics - technical depth at the level the job description asks for - one scenario taken from the role's actual responsibilities Follow up the way a real hiring manager would: push on vague answers, ask what *they* specifically did, what the trade-off was, what the number was. 4. **Save as you go.** After each answer, append to profile/interview-practice.md so nothing is lost: ``` ## <Title> | <Company> (<YYYY-MM-DD>) ← once per session ### Q<n> (<competency>): <question> **Answer:** <the user's answer, word for word> **Follow-up:** <question> / **Answer:** <answer> ``` 5. **Debrief** when the questions are done or the user says stop. Step out of character and give: Score each answer against the scoring criteria the role guide gives for that round, and against what the guide's "Level expectations" says this level must show. - each question rated Strong / OK / Weak, with one line why - the hire / no-hire call this hiring manager would make, and the main reason - the 2–3 things that would most improve the answers Append the debrief to that session in profile/interview-practice.md. ## Rules - Never invent facts about the user's experience, in questions or in the debrief. - Ask what this hiring manager would actually ask for this role, not generic trivia.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · mwoodwilson/agentic-job-search | 100 | MIT |
| reactive-resume/reactive-resume | 100 | MIT |
| buriedsignals/mycroft | 100 | MIT |
| dominiquevienne/claude-job-hunt | 100 | MIT |
| BatteyS/BS-Job-Search | 100 | MIT |
| jamditis/claude-skills-journalism | 100 | MIT |
| tinyfish-io/tinyfish-cookbook | 100 | MIT |
| kasevvlad/claude-skills | 100 | MIT |
| backwardstruck/community-job-search-plugin | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 0c4755dc060e (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100interview-practice
Prowadzi próbną rozmowę o pracę na podstawie roli, ogłoszenia i CV: pytania po jednym, informację zwrotną do STAR i szkice odpowiedzi z doświadczenia. - 100jobhunt-interview
Przeprowadza próbną rozmowę kwalifikacyjną z panelem rekrutera, menedżera i sprawdzającego, zadając pytania STAR i oceniając każdą odpowiedź w 5 kryteriach. - 90mock-interview
Prowadzi realistyczną próbną rozmowę o pracę na stanowisko product marketingu: zadaje jedno pytanie naraz i ocenia każdą odpowiedź. - 90canada-interview-prep
Przygotowuje do rozmowy o pracę w Kanadzie: typowe pytania, odpowiedzi metodą STAR z własnego doświadczenia i próbną rozmowę. - 90us-interview-prep
Przygotowuje do rozmowy kwalifikacyjnej w USA: odpowiedzi STAR, pytania, próbną rozmowę i negocjacje oferty. - 100prep
Przygotowuje kandydata do rozmowy o pracę: prawdopodobne pytania, profil firmy i scenariusze rozmowy z rekruterem, a także próbną rozmowę.