Interview Bank
328 questions total; 1 shown with current filters.
CourseAllFrom Frontend Engineer to Agent Engineer in 30 DaysPrompt Engineering From Scratch in 5 DaysMastering Claude: From Conversation to Claude Code in 5 DaysMastering Codex and the OpenAI Agents SDK in 5 DaysMCP in 7 Days: Wire Tools Into Any AgentAgent Skills in 7 Days: Turn Experience Into Reusable CapabilityContext Engineering in 5 DaysRAG in 14 Days: From Retrieval to Trustworthy AnswersBuild an AI Short-Drama Production Pipeline With Agents in 14 Days
Tag
All#skill-design1#architecture8#cost4#multi-agent4#agent-skills3#context3#evaluation3#llm-basics3#pipeline-design3#security3#system-design3#tool-design3
125 more tagsShow fewer tags
#abstention2#agent-loop2#behavioral2#claude-md2#coding-agent2#consistency2#context-engineering2#context-window2#distributed-systems2#embeddings2#framework-design2#interview-prep2#interview-process2#mcp2#memory2#observability2#orchestration2#prompt-engineering2#provider-abstraction2#rag2#resume2#scalability2#scheduling2#skills2#sse2#streaming2#structured-output2#tool-calling2#agent-basics1#agent-design1#agent-sdk1#agentic-rag1#agents-md1#api-design1#async-task1#auth1#backoff1#bi-encoder1#build-vs-buy1#career1#chunking1#communication1#concurrency1#configuration1#consistent-hashing1#content-safety1#context-assembly1#context-management1#coreference1#cost-accounting1#cost-analysis1#cross-encoder1#data-quality1#encoding1#failure-analysis1#fairness1#few-shot1#ffmpeg1#fine-tuning1#frontend1#global-market1#golden-set1#hooks1#human-in-the-loop1#hybrid-search1#image-generation1#ingestion1#json-schema1#jwt1#langgraph1#long-context1#long-term-memory1#maintenance1#mcp-basics1#media-pipeline1#mental-model1#message-bus1#messages-api1#migration1#model-routing1#moderation1#modularity1#multi-turn1#normalisation1#openai1#operations1#ordering1#overlap1#primitives1#prioritization1#priority-queue1#proactive-messaging1#product-engineering1#project-storytelling1#prompt1#prompt-basics1#prompt-bloat1#prompt-design1#prompt-injection1#prompt-surface1#prompt-techniques1#prompting1#protocol1#query-rewriting1#rag-basics1#rate-limiting1#redis-streams1#reliability1#responses-api1#retrieval1#routing1#sampling1#schema-validation1#scripts1#server-design1#sharding1#similarity1#stakeholder-communication1#star1#state-machine1#system-prompt1#test-set1#token-budget1#tts1#workflow-engine1
Agent Skills in 7 Days: Turn Experience Into Reusable Capability
D3 A Design Method: Distilling From Repeated Tasks, Checklist Style vs. Reference-Manual Style, Four Anti-Patterns, and Trigger Testing
Which tasks are worth turning into a skill and which are not? Give me a test I can apply on the spot.什么样的任务适合做成 skill,什么样的不适合?给我一套能当场用的判断标准。
Common in ChinaCommon overseasBasic#agent-skills#skill-designHow to reason about it · think before answering
- The lazy answer is repetitive and complex tasks, which anyone can say. The interviewer wants a falsifiable test plus the reasoning behind each part.
- Give three criteria and insist all three must hold: repetition (done at least three times and will recur), correction (you interrupted the model the first time), and checkable results (you can tell afterwards whether it was right).
- Explain each. Correction is the strongest, because it simultaneously proves the model does not know and that you do. Without correction history you produce generic filler like handle errors appropriately.
- Checkability is the one people skip, and it decides not whether you can write the skill but whether you can iterate on it. If correctness only surfaces in three months, you are guessing.
- Then state the failure modes: without repetition nobody uses it, without correction it is filler, without checkability you cannot improve it.
- Expected follow-up: how wide should one skill be? Scope it like a function: one coherent unit that composes with others. Two skills always activated together were one skill; if the description needs and so on, the scope is too wide.
分析过程 · 先想清楚再作答
- 这题最容易答成「重复的、复杂的任务」,那是所有人都会说的话,没有区分度。面试官想听的是一套能证伪的判据,以及每一条判据背后的道理。
- 给三条,并且强调三条都要成立:重复(干过至少三次且还会干)、有纠正(模型第一次做时你打断过它)、结果可检验(做完能判断对错)。
- 逐条解释为什么。「有纠正」是最硬的一条,因为它同时证明模型确实不会、你确实会——没有纠正记录的 skill 写出来大概率是「妥善处理错误」这类正确的废话。
- 「可检验」这条常被忽略但很关键:它决定的不是这个 skill 能不能写,而是**你能不能迭代它**。对错要三个月后才知道的任务,你写完只能凭感觉觉得有用。
- 然后给反面:不满足这三条会怎样——不重复的没人用,没纠正的是废话,不可检验的没法改进。这一句把判据从清单变成了论证。
- 可预期的追问是「那范围多大合适」。答案是像拆函数一样:一个内聚的工作单元,且能与别的 skill 组合。两个总是一起激活的 skill 本来就是一个;描述里忍不住写「等等」说明范围太大了。
Key points
- All three must hold before you start: repetition, correction, checkable results.
- Correction is the strongest signal because it proves both the gap and your expertise.
- Checkability decides whether you can iterate, not whether you can write it.
- Scope to one coherent unit; two skills that always activate together should be merged.
- If the description needs and so on, the scope is already too wide.
答题要点
- 三条判据全部成立才动手:重复、有纠正、结果可检验。
- 有纠正是最硬的一条,它同时证明模型不会而你会。
- 可检验决定的不是能不能写,而是能不能迭代。
- 范围按内聚工作单元切,总是一起激活的两个 skill 应该合并。
- 描述里出现「等等」「以及相关的」,说明范围已经太大,该拆。