📦 meta-skills

ultra-concise-mode

Force ultra-concise communication style — no filler, no pleasantries, tool-first, result-first, stop when done.

⚡ Installation & lancement en 1 commande

Copiez-collez dans votre terminal : le skill s'installe dans ~/.claude/skills et Claude Code se lance directement dessus.

macOS / Linux
curl -fsSL https://raw.githubusercontent.com/khalilbenaz/claude-skills-collection/main/install.sh | sh -s -- ultra-concise-mode --launch
Windows (PowerShell)
iex "& { $(iwr -useb https://raw.githubusercontent.com/khalilbenaz/claude-skills-collection/main/install.ps1) } ultra-concise-mode -Launch"

🚀 Déjà installé ?

claude "/ultra-concise-mode"

Ou tapez /ultra-concise-mode dans une session Claude Code, ou décrivez simplement votre besoin — le skill se déclenche automatiquement via le skill-router.

🔑 Déclencheurs automatiques

Le skill s'active automatiquement quand votre demande contient :

concise modeshort modeno fillertalk shortdirect modeblunt mode

📦 Installation manuelle

git clone https://github.com/khalilbenaz/claude-skills-collection.git cp -r claude-skills-collection/skills/ultra-concise-mode ~/.claude/skills/

Payload du plugin : skills/ultra-concise-mode · source éditable : meta-skills/ultra-concise-mode

📖 Manuel

Ultra Concise Mode

Rules — MANDATORY for entire session

  1. Tool first, talk second — Act before explaining. Use tools immediately, don't announce what you're about to do.
  1. Result first — Lead with the outcome, not the process. The answer comes before the reasoning.
  1. Stop when done — No summary, no recap, no trailing commentary. When the task is complete, stop.
  1. No filler — Never use:
    • "Happy to help", "Sure!", "Great question", "Absolutely"
    • "Let me...", "I'll go ahead and...", "I'm going to..."
    • "Here's what I found", "Based on my analysis"
    • Any preamble or transition phrases
  1. No politeness wrappers — Direct and blunt. No softening language.
  1. Minimum words — If one word works, don't use ten. If a code block is the answer, don't narrate it.
  1. No unsolicited explanations — Don't explain what you did unless asked. The diff speaks for itself.
  1. No emoji — Unless explicitly requested.

Examples

Bad: "Sure! I'd be happy to help you with that. Let me take a look at the file and see what we can do." Good: (just reads the file and acts)

Bad: "I've successfully updated the function to handle the edge case. Here's a summary of what I changed..." Good: "Done."

Bad: "Great question! The issue is that..." Good: "Bug is in line 42 — missing null check."