agentsclimarketplace
Sign in

Interview system designer

Skill sinhoneyy/master-skills/skills/interview-system-designer

This skill should be used when the user asks to "design interview processes", "create hiring pipelines", "calibrate interview loops", "generate interview questions", "design competency matrices", "analyze interviewer bias", "create scoring rubrics", "build question banks", or "optimize hiring systems". Use for designing role-specific interview loops, competency assessments, and hiring calibration systems.From its SKILL.md

Install
npx -y skills add sinhoneyy/master-skills --skill interview-system-designer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, 363 tokens by cl100k_base, as published. Nobody here has run it

Interview System Designer

Comprehensive interview loop planning and calibration support for role-based hiring systems.

Overview

Use this skill to create structured interview loops, standardize question quality, and keep hiring signal consistent across interviewers.

Core Capabilities

  • Interview loop planning by role and level
  • Round-by-round focus and timing recommendations
  • Suggested question sets by round type
  • Framework support for scoring and calibration
  • Bias-reduction and process consistency guidance

Quick Start

# Generate a loop plan for a role and level
python3 scripts/interview_planner.py --role "Senior Software Engineer" --level senior

# JSON output for integration with internal tooling
python3 scripts/interview_planner.py --role "Product Manager" --level mid --json

Recommended Workflow

  1. Run scripts/interview_planner.py to generate a baseline loop.
  2. Align rounds to role-specific competencies.
  3. Validate scoring rubric consistency with interview panel leads.
  4. Review for bias controls before rollout.
  5. Recalibrate quarterly using hiring outcome data.

References

  • references/interview-frameworks.md
  • references/bias_mitigation_checklist.md
  • references/competency_matrix_templates.md
  • references/debrief_facilitation_guide.md

Common Pitfalls

  • Overweighting one round while ignoring other competency signals
  • Using unstructured interviews without standardized scoring
  • Skipping calibration sessions for interviewers
  • Changing hiring bar without documenting rationale

Best Practices

  1. Keep round objectives explicit and non-overlapping.
  2. Require evidence for each score recommendation.
  3. Use the same baseline rubric across comparable roles.
  4. Revisit loop design based on quality-of-hire outcomes.

What ships with it: 15 files

281.0 KB alongside SKILL.md, 4 of them executable

assets/

expected_outputs/

references/

scripts/

Gives 0 of the 12 instructions most design frontend skills give in 363 tokens

Counted across 1,169 of the 1,878 authors here whose files we hold, read 2026-08-07

  • Use CSS variables for color consistencyin 72 of 1169, across 23 files
  • Commit to one bold aesthetic direction before codingin 72 of 1169, across 27 files
  • Match implementation complexity to the aesthetic visionin 70 of 1169, across 20 files
  • Add atmospheric background effects and texturesin 57 of 1169, across 9 files
  • Use unexpected spatial compositions and layoutsin 56 of 1169, across 8 files
  • Implement real working codein 55 of 1169, across 7 files
  • Vary themes and aesthetics across different designsin 48 of 1169, across 7 files
  • Launch chromium in headless modein 47 of 1169, across 4 files
  • Close the browser when donein 47 of 1169, across 4 files
  • Run provided scripts with help flag firstin 47 of 1169, across 4 files
  • Wait for network idle statein 47 of 1169, across 4 files
  • Use descriptive selectors for elementsin 47 of 1169, across 4 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,834. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.