agentleFS
stijnvanhullestijnvanhulle/agents/.agents/skills/ask/SKILL.md

ask

Skill2 starsChanged 55 days agoMITView on GitHub

Puts a decision to the user through the client's native picker, or a lettered list when none exists. Use for any question with discrete answers, such as a push, a version bump, or which findings to fix, even when no other skill says to ask.

72 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use daily-arxiv, exp-eval 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.
  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • skyllwtSkill

    exp-pilot-eval

    Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.

    Also in 4 projects that use this

  • skyllwtSkill

    exp-pilot-run

    Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.

    Also in 4 projects that use this

  • phanghonghaoSkill

    poster

    HTML/CSS A4 海报生成。从沙龙/活动 Markdown 文件生成科技风 A4 海报 PDF/PNG。Use when user mentions: poster, 海报, 海报生成, make poster, generate poster, 活动海报, 沙龙海报.

    Also in 4 projects that use this

  • +6 more from Lambenthan
  • +1 more from skyllwt

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 60 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:

    Put a decision to the user and wait for the answer before the step it decides.

    line 8
  2. Distinctive:

    Use the first one the session has.

    line 12
  3. Distinctive:

    Read only the file for the tool you use: those pickers have their own limits.

    line 22
  4. Distinctive:

    Never put a secret or credential in an option.

    line 53
  5. Distinctive:

    Ask before the step, not after: do not write the file, commit, or push that the answer decides until it arrives.

    line 57

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

Put a decision to the user and wait for the answer before the step it decides.

1. Pick the tool

Use the first one the session has. Never call a tool that is not available.

ToolClientRead first
AskUserQuestionClaude Code, Claude Desktop
AskQuestionCursor
request_user_input_asyncPaseo, or Codex when the mode exposes itreferences/paseo.md
request_user_inputCodex Plan modereferences/codex.md
NoneLettered options in chat, same order plus Other. Ask for the letter

Read only the file for the tool you use: those pickers have their own limits.

2. Summarize in bullets

In the same reply as the picker call, and before it, write one bullet per decision: what it changes and why. The picker has no room for detail and covers the chat on mobile, so the bullets are the only place the user can judge each decision. A prose paragraph or a line such as "findings will follow" is not a summary.

- `render.tsx:14`: the comment still says "@kubb/ast pin". Reword to "Studio's Kubb pin", since
  `@kubb/ast` is no longer a direct dependency. Recommend Apply.
- `render.tsx:31`: `as ApiMeta` repeats the inferred type. Remove the cast. Recommend Apply.

3. Shape the questions

  • Each question stands alone. Mobile clients hide the chat behind the picker, so name the thing (Duplicated 402 logic in billing.ts?) and never point at a number or letter only the chat defines (Fix 3?).
  • Offer 2 to 4 real options, likely answer first. Mark the one you think is best (Recommended) and give the reason in its description.
  • One question per independent decision, sent together. AskUserQuestion takes four per call, so send the rest in a follow-up call rather than dropping any. Merge questions only when their answers settle one decision.
  • Per-item decisions, such as review findings, get one single-select question each, offering Apply, Skip, or a concrete alternative. Never a bundle such as All (1-7), None, or Apply both.
  • Allow multiple selection only when several answers can be true, never for per-item decisions.
  • For an open question, offer likely answers and allow custom input, unless the calling skill forbids guessed options.
  • Never put a secret or credential in an option. Ask for it in prose and never echo it.

4. Wait

Ask before the step, not after: do not write the file, commit, or push that the answer decides until it arrives. When the question is skipped or unanswered, do not choose for the user, and do not guess now and report the guess later. Stop at that decision, say what is missing, and finish only the work that does not depend on it. A push or a version bump always waits.

Output

The bullets, then the picker. After the answer, one bullet per decision naming the choice, then the work it unlocked.

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.