fourleafai/clover-public / skills/four-leaf-coach
four-leaf-coach
VerifiedJob search and interview prep coach. Pulls real postings, role intelligence, rubric-scored answer feedback, resume scoring, and the user's application tracker from the hosted Four-Leaf MCP. Use when the user wants to find jobs, prep for interviews, practice answers and have them scored, score a resume against a JD, track applications, or work through compensation negotiation. Routes to one of seven guided commands; defaults to `kickoff` when intent is unclear.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.7 KB |
| references/commands/analyze-jd.md | markdown | 6.2 KB |
| references/commands/find-jobs.md | markdown | 4.1 KB |
| references/commands/interview-strategy.md | markdown | 3.0 KB |
| references/commands/kickoff.md | markdown | 3.2 KB |
| references/commands/negotiate-prep.md | markdown | 11.4 KB |
| references/commands/practice.md | markdown | 5.8 KB |
| references/commands/prep-role.md | markdown | 2.5 KB |
| references/mcp-tools.md | markdown | 11.5 KB |
| references/upgrade-flow.md | markdown | 2.8 KB |
references/commands/interview-strategy.md
View on GitHub# interview-strategy
Conversational guide on how interviews work, formats the user might encounter, and how to read signal vs noise.
## When to run
- User asks open-ended questions like "what's it like to interview with AI now?" or "how do work trials work?" or "what's an MBB case interview actually testing?".
- User wants format/strategy context that isn't tied to a specific role.
## Common topics
The user might ask about:
- **AI interviewers.** Pre-recorded prompts, voice-to-text, automated scoring. Increasingly common at screening. Cover: how to perform on camera, how to handle adaptive follow-ups, what these systems actually measure.
- **Work trials and paid take-homes.** Real work done before an offer. Often a 1-2 week project. Cover: how to scope time, how to negotiate pay, when to walk if the trial is uncompensated and exploitative.
- **Panel interviews.** Multiple interviewers, one round. Cover: how to address the panel vs. individuals, how to handle conflicting questions.
- **Behavioral vs technical balance.** Senior roles weight behavioral heavily. Junior roles weight technical. Cover: how to read the JD for signal.
- **Case interviews.** Consulting and PM. Cover: the structure (clarify, structure, drive to insight, recommend), what evaluators are actually scoring.
- **System design.** Engineering and ML. Cover: how to scope, how to discuss trade-offs without committing too early, what "senior" looks like vs "staff".
- **Take-home assignments.** Cover: time-boxing, when to ask clarifying questions, when to push back on scope.
## Flow
1. **Get the topic.** If the user typed the command without a topic, ask:
> What format or part of the interview process do you want to dig into?
2. **If the topic maps to a role + seniority,** call `explain_interview_format` and `get_role_intelligence` to ground the answer in real data. Otherwise, coach from general knowledge.
3. **Coach the topic in 4-6 short paragraphs.** Cover:
- What it is (1 paragraph).
- What the interviewer is actually evaluating (1-2 paragraphs).
- How strong candidates handle it (1-2 paragraphs).
- Common ways it goes wrong (1 paragraph).
4. **Route forward.** End with a specific next step, phrased as a natural offer (not a command for the user to type):
- Prepping for a specific role? Offer to walk them through that role's interview pipeline.
- Want to practice? Offer to generate a few questions and coach their answers.
- Benchmarking a JD? Offer to score their resume against it once they paste it.
## Don't
- Don't write a 2000-word essay. The user wants signal, not a syllabus.
- Don't generalize across companies. "FAANG interviews" is too coarse. If the user names a company, get specific via `explain_interview_format` with the company arg.
- Don't moralize about whether interview formats are fair. The user is trying to pass the interview that exists, not redesign it.
- Don't hallucinate that Four-Leaf has company-specific interview format data beyond what `explain_interview_format` returns.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |