agentleFS
ronedgecombronedgecomb/anything/skills/interview/SKILL.md

interview

Skill1 starsChanged 9 days agoApache-2.0View on GitHub

Clarify a topic, goal, decision, or requirements through an adaptive conversation. Use when the user asks to be interviewed, when important ambiguity blocks useful work, or when project setup needs preference discovery. Works for software, research, writing, planning, and other topics without requiring a plan file.

104 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

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

  • 0

    Common

    Most of the 89 edited versions we read keep these.

  • 6

    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:

    Read available context before asking for facts it already contains.

    line 14
  2. Distinctive:

    Ask one to three related questions at a time by default, using fewer when an answer will shape the next question.

    line 20
  3. Distinctive:

    Use options for meaningful alternatives and free text for discovery.

    line 24
  4. Distinctive:

    Ask follow-up questions when an answer reveals an important gap.

    line 26
  5. Distinctive:

    Do useful independent work while answers are pending.

    line 28
  6. Distinctive:

    Keep explicitly approved wording intact when the user has made exact wording a requirement.

    line 36

“Common” is measured: kept by at least 6 in 10 of the 89 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

Interview

Help the user reach a useful understanding or decision. Match the depth and pace to the topic. Follow their stated preferences and applicable project instructions; do not turn every task into an interview.

Prepare

  • Identify the question being explored and the outcome the conversation should support.
  • Read available context before asking for facts it already contains. If discovery tools are unavailable, state the gap and ask for the context that matters.
  • Separate consequential unknowns from routine choices. Make reasonable, reversible implementation choices within the user's request.
  • For a broad idea, start with a concrete example, desired outcome, and current pain points. For a narrow decision, focus on what changes the answer.

Ask in useful rounds

Ask one to three related questions at a time by default, using fewer when an answer will shape the next question. Adapt to the user and the actual question interface's limits. Use ordinary conversation when no question tool is available.

  • Make each question understandable on its own.
  • Offer a recommendation when you have enough evidence, with its consequence and trade-off. Do not manufacture certainty.
  • Use options for meaningful alternatives and free text for discovery. Leave room for a different answer.
  • Show a sketch, example, or draft when it makes the choice concrete. Match the format to the available interface.
  • Ask follow-up questions when an answer reveals an important gap. Do not impose a single-round limit on discovery.

Do useful independent work while answers are pending. Do not proceed with dependent work when the answer is required. Silence, elapsed time, or a preselected option is not an answer or authorization.

Consolidate

Summarize confirmed decisions, assumptions, and remaining questions separately. Check the interpretation when a misunderstanding would matter; avoid a ritual approval round for routine summaries.

Return the result in the form the caller needs: a conversational conclusion, requirements, a decision record, setup preferences, or additions to an existing plan. Use a task-plan skill if helpful and installed, but do not require a plan or write files merely because an interview occurred.

Keep explicitly approved wording intact when the user has made exact wording a requirement. Ordinary drafting does not require a word-for-word approval table for every string.

Revisit when needed

Accept corrections and update the affected conclusions. Explain a newly discovered constraint before asking the user to reconsider a settled choice.

A separate adviser can help a difficult decision when delegation is available, permitted, and worth its cost. Give it neutral context and distinguish its evidence from its judgment. Without that capability, examine alternatives directly and do not claim an independent opinion.

See references/question-patterns.md for examples.

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.