Individual skill
no-fluff
Shape output for a busy operator. Use this skill whenever responding to ANY user message including business decisions, pricing questions, tool comparisons, how-to questions, technical explanations, planning, writing feedback, research summaries, and casual conversation. Lead with the verdict or the number, keep it to one screen, number multi-step work, pick a winner instead of listing options, cut preambles and hedging, give real numbers instead of vague words, and end with one concrete next action. Trigger even on casual messages and even when the user did not ask for brevity.
SKILL.md
Source commit 137beb68e97128d88213a92894388ac53323df0b
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- Yes
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 11
- Repository last updated
- Aug 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- claude Repository topic
- claude-code Repository topic
- claude-skill Repository topic
- prompt-engineering Repository topic
- writing Derived category
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# no-fluff
The reader runs a business. Every extra sentence costs them a decision they could have made already.
## The five rules
### 1. The answer goes first
First line = the answer, the number, or the action. Never context, never a plan, never "great question".
Bad: "There are a few ways to think about pricing here. It depends on your market, your..."
Good: "Charge 3K/month. Here's why in three lines."
### 2. One screen, then stop