agentleFS
Sign inStart free
FirzusFirzus/agent-skills/skills/stack/interview/SKILL.md

interview

Skill4 starsChanged 19 days agoMITView on GitHub

Settle open decisions with the user through short rounds of questions until both share the same understanding of what will be built. Use when a request leaves product choices open, when the user asks to be interviewed or challenged on a plan, or when another skill hands over decisions to settle.

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

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 80 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before asking, walk through the normal case and the cases that matter for this work: empty or invalid input, failure halfway, repetition, …

    line 21
  2. Distinctive:

    Ask every independent question in one round, most consequential first.

    line 28
  3. Distinctive:

    Wait for the answers. Keep partial answers and leave the rest open.

    line 31
  4. Distinctive:

    When the user says "you choose", take the decision and record it as yours with its reason.

    line 32
  5. Distinctive:

    When nothing consequential remains open, summarize the decisions, including yours, and what stays out of scope, and ask the user to confirm …

    line 35

“Common” is measured: kept by at least 6 in 10 of the 80 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Settle decisions by interview

Reach a shared understanding of what will be built, with every decision the user owns taken by the user and every other choice taken by you. Return the result to the caller, or to the user when run on its own.

What to ask

A question is for the user only when its answer changes what gets built and the user owns it: behavior, scope, cost, what happens when things go wrong, or a step that is hard to undo. Look up anything the code, history, or documentation can tell you. Make routine and technical choices yourself and record them with their reason. A choice that an experiment or research could settle is a need for the caller, not a question.

Before asking, walk through the normal case and the cases that matter for this work: empty or invalid input, failure halfway, repetition, two people acting at once, existing data, and who is allowed to do what. Ask only where the answer is not already evident.

Rounds

  1. Ask every independent question in one round, most consequential first. Keep a question that depends on an unanswered one for a later round. Prefer fewer, sharper questions: if a question would not change the work, drop it.
  2. Wait for the answers. Keep partial answers and leave the rest open.
  3. When the user says "you choose", take the decision and record it as yours with its reason.
  4. Trace each answer's consequences; ask the follow-up questions they open.
  5. When nothing consequential remains open, summarize the decisions, including yours, and what stays out of scope, and ask the user to confirm it. A caller may merge this summary into its own agreement message.

What each question contains

Give each question what the user needs to decide from the message alone: the question, its context written to the decision format of the operating policy, the options, each on its own line and lettered so the user can answer briefly (such as 1b), and your recommendation with its reason.

Return

Return the accepted decisions with their consequences and who took each, the exclusions, open questions, needs for research or an experiment, and out-of-scope findings kept apart.

Done: the user confirmed the summary. Waiting: a question or the confirmation is unanswered. Stopped: the user ended it; return the partial result with its open questions.

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.

Check your setup, free