agentleFS
Sign inStart free
PaulRBergPaulRBerg/dot-agents/skills/interview-me/SKILL.md

interview-me

Skill6 starsChanged 6 days agoMITView on GitHub

This skill is coordination-exempt: skip the ai-coord gate for its declared work. Clarify what the user wants through a focused, conversational interview without exhausting every possible branch. 1. Extract the current objective, audience, constraints, assumptions, and already-made choices. Investigate facts available from the conversation, codebase, or supplied evidence instead of asking for them. 2. Ask exactly one concise question per turn in plain conversational language. Format every question turn as ### 💬 Question <N> — <topic>, followed by **🧭 Context**,…

98 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use constraint-driven-development, idea-refine 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.
  • MrCipherSmithSkill

    constraint-driven-development

    Use when a project needs a persistent, measurable quality bar — starting a project without documented standards, 'set up constraints', or when coverage/perf/a11y thresholds get re-debated per-PR. Produces CONSTRAINTS.md with enforceable numbers, ratchets, and a guard against silent weakening. NOT for throwaway prototypes or a one-off CI setup.

    Also in 16 projects that use this

  • LLl0k0laDSkill

    idea-refine

    Refine ideas through structured divergent and convergent thinking. Use "idea-refine" or "ideate" to trigger.

    Also in 42 projects that use this

  • LLl0k0laDSkill

    using-agent-skills

    Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.

    Also in 32 projects that use this

  • HK-hubSkill

    observability-and-instrumentation

    Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.

    Also in 32 projects that use this

  • orenluxySkill

    implementation-notes

    Maintain an IMPLEMENTATION_NOTES.md decision log during any multi-step implementation session. Use this in EVERY session that involves writing or modifying code across more than one file, or any session expected to run longer than a few tool calls. Records decisions, deviations from plan, and open questions so nothing is silently guessed.

    Also in 3 projects that use this

  • HK-hubSkill

    deprecation-and-migration

    Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.

    Also in 29 projects that use this

  • +6 more from LLl0k0laD

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 83 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Ask exactly one concise question per turn in plain conversational language.

    line 20
  2. Distinctive:

    Treat three to five questions as a soft target, not a quota or hard cap.

    line 25

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

This skill is coordination-exempt: skip the ai-coord gate for its declared work.

Clarify what the user wants through a focused, conversational interview without exhausting every possible branch.

Workflow

  1. Extract the current objective, audience, constraints, assumptions, and already-made choices. Investigate facts available from the conversation, codebase, or supplied evidence instead of asking for them.
  2. Ask exactly one concise question per turn in plain conversational language. Format every question turn as ### 💬 Question <N> — <topic>, followed by **🧭 Context**, optional **🎯 Recommended**, and **❓ Question** sections, with each label on its own line. Keep the context brief. Include a recommended default only when it makes the question easier to answer. Put exactly one question in the final section. Choose the highest-leverage question whose answer could materially change the direction or next step.
  3. Treat three to five questions as a soft target, not a quota or hard cap. Stop earlier when the direction is already clear. Continue beyond five only when the next answer could still materially change the result. Otherwise, record the uncertainty for the summary.
  4. Favor intent, scope, success criteria, audience, and key tradeoffs. Follow the threads the user emphasizes instead of mechanically covering every interface, failure mode, operational concern, or other domain.
  5. Briefly acknowledge or synthesize an answer as ✅ Noted: <choice or implication> only when it advances the conversation. Do not use decision cards, progress counts, exhaustive checklists, repeated recaps, or a formal decision record. Do not reopen settled choices unless new evidence conflicts with them.
  6. Finish immediately when the user asks to stop or when further questions would add little value. Return ### 🧭 Summary, ### ✅ Key choices, optional ### ❓ Open questions, and ### 🏁 Next step. Keep the final response concise. Do not end with another question.

Completion requires a clear summary of the user's direction, the choices that materially shape it, any unresolved uncertainty worth preserving, and one practical next step.

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