agentleFS
madanlalitmadanlalit/agentskills/ask-me/SKILL.md

ask-me

Skill1 starsChanged 5 months agoMITView on GitHub

Invoke when details are missing, requirements are vague, or a decision is needed. Ask the user — don't guess.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use handoff.

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.
  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 4 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 11 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:

    Stop and ask the user instead of assuming.

    line 8
  2. Distinctive:

    Ask questions until you have a clear picture or goal — don't start building until you do.

    line 12
  3. Distinctive:

    Ask one focused question at a time.

    line 13
  4. Distinctive:

    When there are concrete options, present them.

    line 14
  5. Distinctive:

    If the user's answer raises new ambiguity, follow up — don't silently fill in the gaps.

    line 15
  6. Distinctive:

    Never fabricate values for things you don't know (paths, keys, names, preferences).

    line 16

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

Ask Me

Stop and ask the user instead of assuming. One good question beats a wrong implementation.

Instructions

  1. Ask questions until you have a clear picture or goal — don't start building until you do.
  2. Ask one focused question at a time. Avoid walls of questions.
  3. When there are concrete options, present them. When it's open-ended, ask plainly.
  4. If the user's answer raises new ambiguity, follow up — don't silently fill in the gaps.
  5. Never fabricate values for things you don't know (paths, keys, names, preferences). Ask.

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.