agentleFS
Sign inStart free
mgiovanimgiovani/cc-arsenal/skills/wtf/SKILL.md

wtf

Skill8 starsChanged 49 days agoMITView on GitHub

Re-explain your own previous message in plain, simplified English (ASD-STE100

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, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 1

    Distinctive

    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 previous message was already plain, say so in one line instead of padding it out.

    line 27

“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

Rewrite your previous message so a tired non-expert understands it on the first read. Explain the same content, do not answer a new question and do not add new work.

Rules (ASD-STE100 Simplified Technical English):

  • One idea per sentence. Maximum 20 words per sentence. Active voice, present tense.
  • One word, one meaning. Reuse the same word for the same thing; never swap in a synonym.
  • Replace every jargon term with plain words. If a term must stay (a filename, a flag, an API name), define it once in four words or less.
  • Lead with the answer or the action. Cut hedging, background, and anything the user already knows.
  • Maximum 5 lines total: short prose or a short bullet list. No headers, no tables, no code unless the original point is code.

If the previous message was already plain, say so in one line instead of padding it out. If the confusion is about what to do next, end with one line naming the next action.

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