interview-prep
- Repo stars 19,014
- Author updated Live
- Author repo knowledge-work-plugins
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @anthropics · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: interview-prep
description: Create structured interview plans with competency-based questions and scorecards. Trigger with "…
category: engineering
runtime: no special runtime
---
# interview-prep output preview
## PART A: Task fit
- Use case: Create structured interview plans with competency-based questions and scorecards. Trigger with "interview plan for", "interview questions for", "how should we interview", "scorecard for", or when the user is preparing to interview candidates..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Interview Design Principles / Interview Plan Components / Role Competencies” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Create structured interview plans with competency-based questions and scorecards. Trigger with "interview plan for", "interview questions for", "how should we interview", "scorecard for", or when the user is preparing to interview candidates.”.
- **02** When the source has headings, the agent prioritizes “Interview Design Principles / Interview Plan Components / Role Competencies” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Interview Design Principles / Interview Plan Components / Role Competencies”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: interview-prep
description: Create structured interview plans with competency-based questions and scorecards. Trigger with "…
category: engineering
source: anthropics/knowledge-work-plugins
---
# interview-prep
## When to use
- Create structured interview plans with competency-based questions and scorecards. Trigger with "interview plan for", "…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Interview Design Principles / Interview Plan Components / Role Competencies” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "interview-prep" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Interview Design Principles / Interview Plan Components / Role Competencies
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Interview Prep
Create structured interview plans to evaluate candidates consistently and fairly.
Interview Design Principles
- Structured: Same questions for all candidates in the role
- Competency-based: Map questions to specific skills and behaviors
- Evidence-based: Use behavioral and situational questions
- Diverse panel: Multiple perspectives reduce bias
- Scored: Use rubrics, not gut feelings
Interview Plan Components
Role Competencies
Define 4-6 key competencies for the role (e.g., technical skills, communication, leadership, problem-solving).
Question Bank
For each competency, provide:
- 2-3 behavioral questions ("Tell me about a time...")
- 1-2 situational questions ("How would you handle...")
- Follow-up probes
Scorecard
Rate each competency on a consistent scale (1-4) with clear descriptions of what each level looks like.
Debrief Template
Structured format for interviewers to share findings and make a decision.
Output
Produce a complete interview kit: panel assignment (who interviews for what), question bank by competency, scoring rubric, and debrief template.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review