agentleFS
eyeixeyeix/skills/interview/SKILL.md

interview

Skill1 starsChanged 30 days agoMITView on GitHub

Relentless interview that sharpens a plan or design while settling terms and decisions into .agentdocs/ (glossary, ADRs) as they crystallize. Use when the user wants to stress-test their thinking, uses any 'grill' / '拷问' trigger phrases, or needs requirements aligned before a task.

94 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use fetch-library-docs, contributor and 10 more.

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.
  • Rehan-Ul-HaqSkill

    fetch-library-docs

    Fetches official documentation for external libraries and frameworks (React, Next.js, Prisma, FastAPI, Express, Tailwind, MongoDB, etc.) with 60-90% token savings via content-type filtering. Use this skill when implementing features using library APIs, debugging library-specific errors, troubleshooting configuration issues, installing or setting up frameworks, integrating third-party packages, upgrading between library versions, or looking up correct API patterns and best practices. Triggers automatically during coding work - fetch docs before writing library code to get correct patterns, not after guessing wrong.

    Also in 4 projects that use this

  • NimbleBrainIncSkill

    contributor

    Get started contributing to NimbleBrain open source — find an integration to build, set up your environment, propose an idea, or check on your work. Use when onboarding as a contributor. Triggers include "I'm a new contributor", "what should I build", "show me open issues", "file an issue".

    Also in 3 projects that use this

  • mjunaidcaSkill

    browsing-with-playwright

    Browser automation using Playwright MCP. Navigate websites, fill forms, click elements, take screenshots, and extract data. Use when tasks require web browsing, form submission, web scraping, UI testing, or any browser interaction. NOT when only fetching static content (use curl/wget instead).

    Also in 4 projects that use this

  • qa-amanSkill

    teach-me

    Teach a topic, video, article, codebase change, spec, or transcript until the user demonstrably understands it, using staged instruction, a running checklist doc, and quizzes. Use whenever the user says "teach me", "explain this in detail", "help me understand X", "/teach-me", "walk me through this", "I want to learn X", "understand this deeply", or pastes a YouTube URL, article, paper, PR, or spec and asks to understand it rather than summarize it. Also use when the user wants study notes or raw material from a source they are learning. Do NOT use for a quick factual lookup, a summary request, or when the user just wants the answer.

    Also in 8 projects that use this

  • trebaudSkill

    find-unknowns

    Workflow for surfacing a task's unknowns before, during, and after implementation — blind spot pass, brainstorm/prototype, interview, references, implementation plan, deviation notes, quiz. Use when starting work in an unfamiliar domain or codebase, when a task feels underspecified, when the user says "find my unknowns", "blindspot pass", "what am I missing", "help me scope this", or when a long task came back wrong.

    Also in 3 projects that use this

  • donatassimkusSkill

    offer

    Offer design, pricing strategy, and business model architecture. Invoke when asked about making an offer better, pricing a product or service, naming an offer, raising prices, generating fast cash, increasing lifetime value, finding the right customer, qualifying buyers, or designing a business model where customers pay for their own acquisition. Use when someone says their offer isn't converting, they need to charge more, they want to add bonuses or guarantees, or they need a money model for their business.

    Also in 3 projects that use this

The file

Files
SKILL.md

访谈与沉淀

无情访谈用户,直到达成共享理解;过程中产生的术语与决策当场沉淀进 .agentdocs/。

访谈:设计树与轮次

把讨论映射为设计树:每个决策分叉出挂在它下面的决策。

按轮次推进。前沿(frontier)是前置已定的每个决策:现在就能问、不用猜测未听到答案的问题。一轮问完整条前沿:每题编号,附你的推荐答案。等用户回答后再进入下一轮。

每轮格式:

❓ **Q1** - **<问题标题>**: <问题正文,可多段,含候选项>

➡️ <你的推荐答案>

---

❓ **Q2** - **<问题标题>**: <问题正文>

➡️ <你的推荐答案>

用户的每个回答都重塑这棵树:已定的决策把前沿向外推,解锁依赖它的问题。重算前沿,问下一轮。答案依赖本轮仍未决问题的,留给更晚的轮次,不塞进本轮。

查事实是你的工作,永远不是用户的。前沿问题需要环境事实(文件系统、工具、代码)时,派子代理去查;不问用户任何你自己查得到的东西。不为它阻塞:运行中的探索是一条未定的前置,只有它下游的问题等它回报,前沿的其余照问。决策是用户的:逐条交给他们,等。

沉淀:当场写,不攒批

访谈中每确定一个术语或一个决策,当场调 Skill 工具执行 agent-docs 的"写:知识沉淀"纪律:

  • 术语精确化(一词多义被拆清)→ .agentdocs/glossary.md;
  • 满足三条门槛的决策(难逆转、无上下文会困惑、真实权衡)→ .agentdocs/adr/;
  • 后续轮次的提问使用已沉淀的术语,巩固共享语言。

主动挑战,不等人问:用户用词与术语表冲突时当场指出;模糊词要求区分;领域概念间关系用边界场景压测;用户说法与代码矛盾时指出。

退化与完成

  • 所在仓库没有 .agentdocs/ 时,沉淀部分自动跳过,退化为纯访谈,不提示初始化;
  • 访谈完成的条件:前沿为空——设计树的每个分支都已走过,没有任何默默假设留下。在用户确认达成共享理解之前,不开始动手实现。

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.

Reviews can't be read right now.

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.