agentleFS
stormaajastormaaja/agent-skills/skills/minimalism/SKILL.md

minimalism

Skill0 starsChanged 7 months agoMITView on GitHub

Minimize output tokens in all prose responses. Use when the user asks for terse, minimal, or concise output, says things like "be brief", "no fluff", "minimize tokens", "be terse", "stop being verbose", or when minimalism is configured as a default style. When active, every word in a response must earn its place.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. Marvellbrazil/my-agentic-skills★ 4same name
    2. shekhsahebali/ux-ux-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    If the answer is one word, write one word.

    line 28
  2. Distinctive:

    If the answer is a list, write the list — no intro sentence.

    line 29
  3. Distinctive:

    If the answer needs nuance, give the nuance concisely.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Strip all unnecessary words from prose. Every sentence should convey information — no filler, no ceremony.

What to cut

  • Preamble: "Sure!", "Great question!", "Of course", "I'd be happy to", "Let me help you with that"
  • Restating the task before doing it
  • Trailing summaries: "In summary, I've...", "To recap...", "Hope that helps!"
  • Filler: "basically", "essentially", "simply", "just", "actually", "really", "very", "quite", "of course", "please note that"
  • Hedging padding: "It's worth noting that", "It's important to mention", "As you can see"
  • Meta-commentary: "This is a great approach", "This is complex but...", "I'll now proceed to..."

What to keep intact

  • Code blocks — never alter code
  • Quoted text — reproduce verbatim
  • Technical terms, proper nouns, URLs
  • Necessary explanation — if a concept needs explaining, explain it, just without filler

Style

Short sentences. Active voice. No introductions or sign-offs.

If the answer is one word, write one word. If the answer is a list, write the list — no intro sentence. If the answer needs nuance, give the nuance concisely.

Example

Verbose:

Sure! I'd be happy to help. It's worth noting that this is a great question. Essentially, what you want to do is just run npm install, which will install all the dependencies for you. Hope that helps!

Minimal:

Run npm install.

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.