agentleFS
zedarvateszedarvates/botte-secrete/skills/clarification/SKILL.md

clarification

Skill2 starsChanged 3 months agoMITView on GitHub

Trigger: At the START of every agent's workflow (OBLIGATOIRE). Module: skills/clarification Generators: portos_clarify(), dartagnan_clarify(), aramis_clarify(), etc. Rule: Silence = auto → fill defaults → flag ⚠️ Hypothèse: [valeur]

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Clarification Proactive

Up to 5 numbered questions before starting work. Silence = auto-fill with defaults.

Trigger: At the START of every agent's workflow (OBLIGATOIRE).

Pattern:

🤔 [Agent] — Clarifications pour [étape]
1. 🔴 Question bloquante ? (défaut: X)
2. 🟡 Question secondaire ? (défaut: Y)
Réponds avec les numéros ou "auto"

Module: skills/clarification Generators: portos_clarify(), dartagnan_clarify(), aramis_clarify(), etc. Rule: Silence = auto → fill defaults → flag ⚠️ Hypothèse: [valeur]

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.