agentleFS
Sign inStart free
mykytasomykytaso/claude-skills/skills/wtf/SKILL.md

wtf

Skill0 starsChanged 2 months agoMITView on GitHub

Explains the last answer again in simple words. Use when the last answer was not clear.

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

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

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 9

    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 you wrote no message before this one, tell the user, and stop.

    line 11
  2. Distinctive:

    Start with the context. Say what you were doing and why, before you say what you did.

    line 21
  3. Distinctive:

    Write in ASD-STE100 Simplified Technical English.

    line 23
  4. Distinctive:

    Keep the name of a file, a function, or a command the same.

    line 25
  5. Distinctive:

    Do not say the same words again with more words.

    line 30
  6. Distinctive:

    Do not apologize. Do not speak about this instruction.

    line 31
  7. Distinctive:

    Do not do more work, and do not change any file.

    line 32
  8. Distinctive:

    Do not ask a question before you give the explanation.

    line 33
  9. Distinctive:

    Write the explanation in the chat.

    line 37

“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

Precondition

  1. If you wrote no message before this one, tell the user, and stop.

Task

Your last message was not clear. $ARGUMENTS

Say it again in a different way.

Rules:

  1. Start with the context. Say what you were doing and why, before you say what you did.
  2. Give the result first, then the details.
  3. Write in ASD-STE100 Simplified Technical English. Use short sentences. Use one thought for each sentence.
  4. Replace each jargon word, abbreviation, and internal name with plain words, or explain it at the first use.
  5. Keep the name of a file, a function, or a command the same. Do not change it.
  6. Keep it short.

Do not:

  • Do not say the same words again with more words.
  • Do not apologize. Do not speak about this instruction.
  • Do not do more work, and do not change any file. Only explain.
  • Do not ask a question before you give the explanation.

Output

Write the explanation in the chat. Do not change any file.

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