Token导航 LogoToken导航

Agent Skill · 待分类

conducting-interviews(进行采访)

conducting-interviews 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

conducting-interviews 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 4,088。

总安装 816周安装 34GitHub Stars 3下载 272核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:conducting-interviews(进行采访)
来源仓库:https://github.com/oldwinter/skills
仓库路径:skills/conducting-interviews
安装命令:
npx skills add https://github.com/oldwinter/skills --skill conducting-interviews
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/oldwinter/skills --skill conducting-interviews

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

conducting-interviews 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理。通过 npx skills add 命令从指定仓库安装并使用。

使用前需确认权限范围、维护状态,避免触发联网或文件读写操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/conducting-interviews

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/oldwinter/skills --skill conducting-interviews;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

conducting-interviews 怎么安装?

在终端执行 npx skills add https://github.com/oldwinter/skills --skill conducting-interviews。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

conducting-interviews 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

conducting-interviews 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

conducting-interviews 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

conducting-interviews 用的人多吗?

公开数据是累计安装 816 次,近一周安装 34 次,下载 272 次,GitHub 3 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

conducting-interviews 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

待分类类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
infsh-cli

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
conducting-interviews

进行采访 · 本页

8163只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Conducting Interviews (Structured, Behavioral)

Scope

Covers

  • Preparing and running structured interviews (screen + loop) with consistent criteria
  • Behavioral interviewing mapped to competencies/values
  • Getting to “substance over polish” (avoiding “confident but shallow” signal)
  • Capturing evidence, scoring consistently, and writing a debrief-ready summary

When to use

  • “Help me conduct interviews for a.”
  • “Create an interview script / interview question set / scorecard for.”
  • “Design an interview loop and structured rubric for.”
  • “Improve interviewer consistency and reduce bias.”

When NOT to use

  • You need to define the role outcomes or write the job description (use writing-job-descriptions first)
  • You need legal/HR compliance guidance or to adjudicate complex employment risk (this skill is not legal advice)
  • You need compensation/offer strategy or negotiation coaching

Inputs

Minimum required

  • Role + level + function (e.g., “Senior PM”, “Engineering Manager”)
  • Interview stage(s) to design/run (screen, hiring manager, panel, etc.) + duration(s)
  • Evaluation criteria: 4–8 competencies/values to measure (or your existing rubric)
  • Company/team context candidates should know (mission, what’s hard, why now)
  • Candidate materials (resume/portfolio) + any areas to probe

Missing-info strategy

  • Ask up to 5 questions from references/INTAKE.md.
  • If criteria aren’t provided, propose a default criteria set and clearly label it as an assumption.

Outputs (deliverables)

Produce an Interview Execution Pack in Markdown (in-chat; or as files if requested):

  1. Interview plan (stage purpose, criteria, agenda, timeboxes)
  2. Question map (questions → competency/value → what good looks like → follow-up probes)
  3. Interviewer script (opening, transitions, probes, close)
  4. Notes + scorecard (rating anchors + evidence capture)
  5. Debrief summary template (evidence-based strengths/concerns + hire/no-hire signal + follow-ups)
  6. Risks / Open questions / Next steps (always included)

Templates: references/TEMPLATES.md Expanded guidance: references/WORKFLOW.md

Workflow (7 steps)

1) Intake + define the stage

  • Inputs: user request; references/INTAKE.md.
  • Actions: Confirm role, stage(s), duration, and who else interviews. Identify must-measure criteria and any “must not” red flags.
  • Outputs: Interview brief + assumptions/unknowns list.
  • Checks: You can state the stage goal in one sentence (e.g., “screen for X; sell Y; decide Z”).

2) Lock evaluation criteria (don’t improvise later)

  • Inputs: competencies/values; role context.
  • Actions: Choose 4–8 criteria; define 1–2 “strong” and “weak” anchors per criterion. Ensure each criterion is observable via evidence.
  • Outputs: Criteria table with anchors.
  • Checks: Every criterion has a definition + evidence hints; no criterion is “vibe”.

3) Build the question map (behavioral first)

  • Inputs: criteria table.
  • Actions: Write 1–2 primary questions per criterion (behavioral: “tell me about a time…”). Add probes that force specifics (role, constraints, trade-offs, results, what you’d do differently). Add two global questions: “How did you prepare?” and “Why here?”
  • Outputs: Question map table.
  • Checks: Each question maps to exactly one primary criterion; no double-barreled questions.

4) Write the interviewer script (runbook)

  • Inputs: question map; timeboxes.
  • Actions: Assemble an interview flow: opening (set context + structure), question sequence, note-taking reminders, and a consistent close: “Is there anything else you want to make sure we covered?”
  • Outputs: Interviewer script with timestamps.
  • Checks: Script fits in time; includes “sell” moments appropriate to stage; includes candidate questions time.

5) Prepare for “substance over polish”

  • Inputs: question map; candidate materials.
  • Actions: Add “substance checks” for polished communicators (ask for concrete examples, counterfactuals, and specific decisions). Add “structure help” for less polished candidates (rephrase, clarify what’s being asked) without leading.
  • Outputs: Substance-vs-delivery guardrails embedded in the script.
  • Checks: The plan reduces false positives from confident delivery and false negatives from imperfect structure.

6) Score using evidence (immediately after)

  • Inputs: notes; scorecard template.
  • Actions: Fill the scorecard with evidence snippets before discussing with others. Rate each criterion with anchors. Write a 5–8 sentence evidence-based summary and list follow-up questions.
  • Outputs: Completed notes + scorecard + summary.
  • Checks: Every rating has supporting evidence; the overall recommendation is consistent with criterion ratings.

7) Debrief + quality gate + finalize pack

  • Inputs: completed scorecard; debrief template.
  • Actions: Produce the debrief-ready packet; run references/CHECKLISTS.md and score with references/RUBRIC.md. Include Risks/Open questions/Next steps.
  • Outputs: Final Interview Execution Pack.
  • Checks: Clear recommendation + uncertainty; fair process; next steps defined (additional interview, reference check, work sample, etc.).

Quality gate (required)

Examples

Example 1 (Screen): “Create a 30-minute phone screen for a Senior Product Manager. I want to evaluate product sense, execution, and collaboration. Output the Interview Execution Pack with a question map and scorecard.” Expected: timeboxed script, behavioral questions, clear anchors, and a scorecard that captures evidence.

Example 2 (Loop): “Design a structured interview loop for a Staff Engineer, including a hiring manager interview and a cross-functional panel. Map questions to our values and include a debrief template.” Expected: stage goals, consistent criteria across interviewers, and artifacts that make debriefs evidence-based.

Boundary example: “Just tell me if this candidate is good; I don’t have criteria or notes.” Response: require criteria + evidence; propose default criteria and ask the user to paste notes or run a structured interview first.

平台分布

Codex

37.42%
按下载量换算102

Claude

27.63%
按下载量换算75

Cursor

18.29%
按下载量换算50

Gemini CLI

8.48%
按下载量换算23

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills