面试题库

7 天 Agent Skills：把经验做成可复用能力

D4 带脚本的 skill：可执行附件、依赖与沙箱、跨平台，以及文档处理类 skill 的拆解

• 什么逻辑该写成脚本放进 skill 的 scripts 目录，什么该留在 SKILL.md 正文里？Which logic belongs in a skill's scripts directory and which belongs in the SKILL.md body?

  国内高频海外高频基础#agent-skills#scripts

  分析过程 · 先想清楚再作答

  1. 这题在考分工感。答「复杂的写脚本」等于没答，因为复杂是个没有边界的词。面试官要听的是可判定的信号。
  2. 给三条信号，命中任意一条就写脚本：同一段逻辑在执行轨迹里被重新发明了第三次；结果必须逐字一致（校验、格式转换、哈希）；一条命令复杂到第一次很难敲对。
  3. 把第二条展开成分工原则，这是本题的核心句：**确定性任务交给代码，判断性任务留给模型**。让模型「按指令做」意味着每次都有偏移的可能，让它跑脚本意味着结果确定。
  4. 再给反面：只是调一个现成工具加两三个参数，直接在正文写这条命令就行，不必建 scripts 目录。很多生态有免安装的一次性运行方式，用它们时**版本必须钉死**，否则上游一发版你的 skill 行为就变了。
  5. 补一条成本视角：脚本是长期资产，要维护、要跟模板同步、要有人看得懂。三条信号一条都不命中的时候，写正文更划算。
  6. 可预期的追问是「怎么发现模型在重新发明轮子」。答案是读执行轨迹而不是只看最终产出——同一个辅助函数在几次运行里反复出现，就是该沉淀成脚本的信号。

  How to reason about it · think before answering

  1. This tests a sense of division of labor. Saying complex logic goes in scripts says nothing, because complex has no boundary. The interviewer wants decidable signals.
  2. Give three: the same logic gets reinvented a third time across execution traces; the result must be byte-identical (validation, format conversion, hashing); or a command is complex enough to be hard to get right first try.
  3. Expand the second into the core principle: deterministic work goes to code, judgment work stays with the model. Following instructions leaves room for drift; running a script does not.
  4. Give the other side: invoking an existing tool with two or three flags belongs inline in the body. Many ecosystems offer install-free one-off runners, and versions must be pinned or an upstream release silently changes your skill's behavior.
  5. Add the cost view: a script is a long-lived asset that must be maintained and kept in sync. When none of the three signals fire, prose is cheaper.
  6. Expected follow-up: how do you notice reinvention? Read execution traces rather than final outputs; the same helper appearing across runs is the signal.

  答题要点

  • 三条信号命中任一条就写脚本：重复发明第三次、结果必须逐字一致、命令复杂到难以一次敲对。
  • 分工原则是确定性任务交给代码，判断性任务留给模型。
  • 只加两三个参数调现成工具的，直接在正文写命令，但版本要钉死。
  • 脚本是长期资产，有维护成本，三条都不命中就写正文。
  • 发现重复发明要靠读执行轨迹，不是看最终产出。

  Key points

  • Write a script when any of three fire: third reinvention, byte-identical results required, or a command hard to get right first try.
  • Deterministic work to code, judgment work to the model.
  • A tool invocation with a couple of flags stays inline, with the version pinned.
  • Scripts are long-lived assets with maintenance cost; if no signal fires, write prose.
  • Spot reinvention by reading execution traces, not final outputs.