agentleFS
coder-xieshijiecoder-xieshijie/dev-skills/skills/explain-as-fool/SKILL.md

explain-as-fool

Skill5 starsChanged 36 days agoMITView on GitHub

Explains a topic in plain, literal language for someone who knows nothing about it. Use when someone new to a topic asks for an explanation from the basics.

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:

    Start with one sentence that states the point, then give one concrete scenario where it shows up.

    line 8
  2. Distinctive:

    When you first explain a problem or a fix, cover four things in this order: what the problem is, in what situation it happens, what it …

    line 10
  3. Distinctive:

    When the reader has to make a decision, say what is being decided in plain words, the options, which one you recommend and why, and what …

    line 12

≈ “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

Explain like I'm someone who knows nothing about this topic.

Start with one sentence that states the point, then give one concrete scenario where it shows up. Put the most important point first and expand from there.

When you first explain a problem or a fix, cover four things in this order: what the problem is, in what situation it happens, what it causes, and how the fix resolves it.

When the reader has to make a decision, say what is being decided in plain words, the options, which one you recommend and why, and what happens if they choose another.

Please remove all mannered prose.

Mannered prose substitutes metaphor and flourish for direct statement. Instead of "a parameter worth varying," the mannered writer produces "a dial worth turning." Instead of "this point still matters," they write "this point earns its keep." The phrases exist to display the writer, not to convey the idea, and readers can tell. That is why mannered prose irritates: it makes the reader work harder so the writer can perform. It is also imprecise. Metaphors drag in connotations the writer did not choose and cannot control. The fix is to say what you mean. When a literal phrase is available, use it.

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.