agentleFS
Sign inStart free
YassimbaYassimba/loom/skills/wtf/SKILL.md

wtf

Skill9 starsChanged 2 months agoApache-2.0View on GitHub

Restate the last message so it lands - plain language, a picture when the it helps and a from-scratch explanation when the concept is new.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ce-skill-work, ce-explain 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.
  • kieranklaassenSkill

    ce-skill-work

    Applies this repository's skill-authoring standard as a procedure. Use for any change to, or judgment about, a file under skills/** — a SKILL.md, a reference, a persona prompt, a bundled script's instructions: creating a skill, editing one, reviewing a skill change, or acting on review feedback (human or bot) about one. Not for src/, tests/, or scripts/ code.

    Also in 5 projects that use this

  • kieranklaassenSkill

    ce-explain

    Explain how and why something has its current shape, or what happened over a window of work, grounded in evidence. Use when the user asks for an explanation. Use ce-pov for a judgment or recommendation.

    Also in 5 projects that use this

  • PdbjorkSkill

    ce-commit

    Create a git commit with a clear, value-communication message. Use when the user asks to commit/save staged or unstaged changes with a repo-appropriate, value-communicating message.

    Also in 5 projects that use this

  • PdbjorkSkill

    ce-simplify-code

    Simplify recently changed code for clarity, reuse, quality, and efficiency while preserving behavior. Use for tidy/refactor passes; use ce-debug for bugs.

    Also in 5 projects that use this

  • +4 more from kieranklaassen
  • +4 more from Pdbjork

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Teach it when the concept is new: If the reader does not know the underlying idea at all — not your message, the thing itself — invoke the …

    line 15

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

WTF

The reader lost the thread on your last message. Give it back in a form they can act on, without asking them to re-read the original.

  1. Find the sticking point. $ARGUMENTS names it; with no arguments, the whole last message is the target. Say in one line what you are restating.
  2. Restate in the register. Invoke the write-simply skill (via the Skill tool) and use its compact prose register. One line of context, then the point in one sentence that stands alone, then at most five short beats. Keep the real terms the reader needs to search or discuss the topic; define each in bold the moment it is used.
  3. Draw it when the shape is the point. A flow, a call path, a file layout, a before-and-after: invoke the show-me skill (via the Skill tool) and pick its smallest chat view — pseudocode, tree, or diff. Chat only; no files, no HTML.
  4. Teach it when the concept is new. If the reader does not know the underlying idea at all — not your message, the thing itself — invoke the explain-simply skill (via the Skill tool) on that concept and let it take over.

Done means: the reader can act on the restatement alone. Stop there; no summary, no menu of next topics.

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.

Check your setup, free