| name | interview-intelligence |
| description | Interview Preparation Mode - Generates a strategic "Intelligence Pre-Interview Sheet" by synthesizing the Job Description, Company news, and Candidate history. Use this when preparing for an interview or researching a target role. |
CRITICAL INSTRUCTION: There are model and runtime-specific variances for agents running in this environment. If you are a Gemini Agent in Gemini CLI, you will use Gemini_Tasks. If you are an OpenAI Agent running under Codex, you will use Codex_Tasks.
Interview Intelligence Workflow
This skill prepares the candidate ([Your Name]) for a high-stakes interview by generating a structured Markdown dossier that maps candidate assets to company pains.
Prerequisites
- Job Description (JD) saved as a
.txt file.
- Python virtual environment:
./venv/bin/python3.
Execution
Run the interview prep orchestrator using the following command:
./venv/bin/python3 AGENT_Tasks/Orchestrator/generate_interview_prep.py --jd <path_to_jd.txt> --company "<Company Name>" --position "<Position Title>"
Strategy: The "Dating" Metaphor
The orchestrator uses a specific strategy to ensure alignment:
- The Attraction: Identifies what the company is truly looking for (e.g., Scale, Stability, Disruption).
- The Spark: Maps [First Name]'s specific stories (from
CV-Data and past resumes) to the company's problems.
- The Compatibility: Aligns [First Name]'s core values (Curiosity, Creativity, Forward-Thinking) with the company culture.
Output Format
The generated dossier (cv-data/resumes/[Position]-[Company]-Interview-Prep.md) includes:
- Intelligence Brief: Culture vibe, recent news, and "Love Language" (key phrases to echo).
- Strategic Talking Points: Problem/Solution/Hook mappings.
- Strategic Questions: Deep research, cultural fit, and technical depth questions for the candidate to ask.
- Red Flags: Cultural "Icks" to avoid.
CRITICAL: After generation, you MUST explicitly restate the absolute file:// URI to the generated PDF on a single line in your final response to the user so it is easily clickable/copyable.
Post-Processing
After generation, it is common to:
- Review the Markdown in
cv-data/resumes/.
- Convert to PDF using
pandoc or chrome --headless if a portable version is needed.
