interview-analysis

What This Skill Does

The interview-analysis skill acts as an intelligent hiring auditor, designed to cut through the noise of rehearsed interview answers to find candidates with authentic experience. Unlike standard ATS tools that look for keywords, this skill utilizes a dynamic expert routing system. It pairs domain-specific masters (such as Marty Cagan for Product or Linus Torvalds for Engineering) with rigorous hiring methodologies (Geoff Smart and Lou Adler) to stress-test a candidate's narrative. By focusing on 'Battle Scars' rather than 'Methodology Recitation,' the tool reconstructs career timelines, identifies logical inconsistencies in project descriptions, and flags attribution fallacies where candidates take credit for external market success.

Installation

To integrate this skill into your OpenClaw agent, execute the following command in your terminal: clawhub install openclaw/skills/skills/mikonos/interview-analysis Ensure your agent has the necessary permissions to access interview transcript files or clipboard content where the candidate data resides.

Use Cases

• Technical Vetting: Distinguishing between engineers who repeat design patterns and those who have navigated high-scale architectural crises.
• Leadership Assessment: Evaluating if a Product Manager truly drove a product launch or if they were merely an observer of team success.
• Inconsistency Detection: Identifying candidates who provide conflicting accounts of their tenure or key project outcomes across multiple interview rounds.
• High-Stakes Hiring: Providing a second-opinion audit on finalist candidates where the risk of a 'bad hire' is high.

Example Prompts

1. "Analyze the provided transcript for the Senior Backend Engineer role. Use the John Carmack expert profile to determine if the candidate's claims about latency optimization hold up to technical scrutiny."
2. "Compare the candidate's answers from the HR screen and the technical round. Highlight any discrepancies in the project timeline or attribution of the core feature development."
3. "Evaluate this Product Manager candidate using the Julie Zhuo framework. Are they demonstrating genuine product sense, or are they just reciting design thinking methodology?"

Tips & Limitations

• Context is Key: Provide the transcript as a clean text file or structured JSON for better attribution mapping.
• Human-in-the-Loop: The expert routing is a guide for analysis, not a final decision-maker. Use the insights as talking points for your final evaluation committee.
• Expert Selection: While the tool defaults to standard domain masters, don't hesitate to override the agent if the role requires a specialized niche (e.g., Cybersecurity vs. General Software Engineering).