agentleFS
JhCircleJhCircle/Defense-ASu-skills/skills/probe/SKILL.md

probe

Skill4 starsChanged 3 months agoMITView on GitHub

面试反酥化追问技能:根据简历或酥化文案生成「第二个问题」级追问、期望证据与不合格回答信号;当用户输入“/probe”“面试追问”“模拟面试官”或要求准备深挖问题时使用。

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use triage and review.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Google CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

The file

Files
SKILL.md

/probe:面试追问脚本

酥化能过关键词筛选,过不了懂行人的第二个问题。/probe 专门生产那第二个问题。

适用角色

  • 求职者自测:先回答,再对照「不合格信号」,决定删改简历。
  • 面试官 / 互助面:按模块抽问,记录证据是否闭环。

工作流程

  1. 读取简历或 /deasu、/resume-audit 输出;确认目标岗位与面试轮次(筛选 / 技术一面 / 二面 / HR)。
  2. 按模块挑选高风险主张,为每条生成 1 个主问 + 2 个追问。
  3. 写明期望听到的证据类型(时间线、接口名、指标口径、个人 vs 团队、失败与取舍)。
  4. 列出不合格回答信号(空泛框架名、改口、把团队成果说成个人、无法画出架构、回避 diff)。
  5. 可选:输出 15—20 分钟模拟面试流程(开场 → 深挖 2 个项目 → 开源/数字突击 → 收尾)。
  6. 用户要将追问结果回流改简历时,转入 /deasu 或 /honest-resume。

提问原则

  • 先问具体,再问抽象:先「你改了哪几个文件 / 哪个接口」,再「你如何理解架构」。
  • 对开源贡献问到 diff 级:改动意图、验证方式、maintainer 反馈、是否合并。
  • 对数字问口径:样本、时间窗、对比基线、是否个人可归因。
  • 对「主导」问决策:你拍板了什么、反对意见是什么、上线责任在谁。
  • 不使用侮辱性措辞;锋利不等于嘲讽。

默认输出

对每条高风险主张输出:

字段内容
原文主张…
主问…
追问 A/B…
期望证据…
不合格信号…
若答不上建议删 / 降级 / 补证据

最后给一张「10 分钟速挖」清单(最多 5 问)。

边界

  • 不泄露或索取密码、验证码、内部未公开数据作为「证据」。
  • 不把模拟面试录音要求写进 skill;是否录音由用户自定。
  • 对明显欺诈内容,建议停止包装并删除条目,而不是教用户圆谎。

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.