Remind
davidondrej/skills
Rewrite the last response simpler and shorter in plain English, prefixed with a 3-5 sentence TLDR of the conversation so far.
Explains the last message, or a file, link or passage you give it, in plain language so you can say what it means and what you must decide without rereading the source.
Install WTF Plain-Language Explainer
$ npx skills add EveryInc/compound-engineering-plugin --skill wtf -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install EveryInc/compound-engineering-plugin wtf --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/wtf .claude/skills/wtf && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "wtf" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/wtf into .claude/skills/wtf/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wtf", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/wtfType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add EveryInc/compound-engineering-plugin --skill wtf -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install EveryInc/compound-engineering-plugin wtf --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/wtf .agents/skills/wtf && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "wtf" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/wtf into .agents/skills/wtf/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wtf", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add EveryInc/compound-engineering-plugin --skill wtf -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install EveryInc/compound-engineering-plugin wtf --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/wtf .cursor/skills/wtf && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "wtf" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/wtf into .cursor/skills/wtf/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wtf", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/EveryInc/compound-engineering-plugin.git --path skills/wtf--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add EveryInc/compound-engineering-plugin --skill wtf -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install EveryInc/compound-engineering-plugin wtf --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/wtf .gemini/skills/wtf && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "wtf" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/wtf into .gemini/skills/wtf/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wtf", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install EveryInc/compound-engineering-plugin wtfInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add EveryInc/compound-engineering-plugin --skill wtf -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/wtf .github/skills/wtf && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "wtf" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/wtf into .github/skills/wtf/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wtf", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add EveryInc/compound-engineering-plugin --skill wtf -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install EveryInc/compound-engineering-plugin wtf --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/wtf .opencode/skills/wtf && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "wtf" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/wtf into .opencode/skills/wtf/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wtf", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
wtf- GitHub stars
- 25k
- Token cost
- ~549 tokens
- SKILL.md length
- 313 words
- Files
- 2
- Skills in repo
- 37
- Repo updated
- First seen
- Licence
- MIT
At a glance
Explains the last message, or a file, link or passage you give it, in plain language so you can say what it means and what you must decide without rereading the source.
- You did not understand the agent's last reply
- SKILL.md covers What to explain and How to explain
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- A long document, link or pasted passage needs a short plain explanation
What it does
When you invoke it because you did not follow something, the agent decides the target from what you passed: nothing means its own most recent message, a path or link is read first, a pasted passage is used as is, and a short pointer such as a step number narrows it to that part of the conversation. If the target is still unclear, it asks one short question instead of guessing.
The explanation opens with the point in a sentence or two, then says what it means for you: what happened, what state things are in and what you need to decide or do. It explains rather than rewrites, stays shorter than the source, uses everyday words while keeping needed technical terms, file names, commands and values, and never sounds more certain or more positive than the source. It flags vague or self-contradicting sources, corrects the agent's own earlier mistakes, and avoids forced analogies or talking down.
When your agent uses it
- You did not understand the agent's last reply
- A long document, link or pasted passage needs a short plain explanation
- You need to know what a message wants you to decide or do
Example prompts
- “/wtf explain the migration part of your last message”
- “Explain this outage report in plain language: ./reports/outage.md”
- “I didn't follow step 3, so say it again simply.”
What it can do on your machine
Read from SKILL.md and the folder at commit cef001f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
WTF Plain-Language Explainer loads about 549 tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 313 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from EveryInc/compound-engineering-plugin at commit cef001f, republished under its MIT licence (© EveryInc). 313 words, ~549 tokens.
Download SKILL.mdSave it as
.claude/skills/wtf/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- wtf
- description
- Explain the last message, or a supplied file, link, or passage, in plain language a person follows on the first read. Use when the user invokes wtf because they did not follow something. Use ce-explain to investigate how or why code works, and ce-noslop to rewrite prose.
- disable-model-invocation
- true
- argument-hint
- [file path, URL, pasted text, or which part lost you; blank for the last message]
wtf
The user did not follow something. Explain it the way you would to a smart colleague who was not in the room.
Done: the user can say what the source means and what, if anything, they need to decide or do, without going back to the source.
What to explain
The text the user passed with the invocation decides the target:
- Nothing passed: your most recent message.
- A file path or a link: read it, then explain it.
- A pasted passage: that passage.
- A short pointer such as "the migration part" or "step 3": only that part of the conversation.
If the target is still unclear, ask one short question instead of guessing.
How to explain
- Open with the point in one or two sentences: what this says and why the user should care. Write no preamble and no apology for the earlier wording.
- Then say what it means for them: what happened, what state things are in, and anything they need to decide or do.
- Explain the source; do not rewrite it. The explanation is shorter than the source because it leaves out whatever the user does not need in order to understand it or act on it. Do not walk a document section by section.
- Use everyday words. When a technical term matters, keep it and say what it means once, in passing. Keep the exact file names, commands, and values the user will need to use.
- Keep everything that changes what the user would do: failures, caveats, open questions, and requests. The explanation must not sound more positive or more certain than the source.
- Add no claims the source does not make. If the source is vague or contradicts itself, say so. If re-reading your own message shows it was wrong, say that and correct it.
- Plain does not mean childish. Do not force analogies, cheerlead, or talk down.
© EveryInc, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/wtf of EveryInc/compound-engineering-plugin.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit cef001f
Compare with similar skills
WTF Plain-Language Explainer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| WTF Plain-Language Explainer this skillEveryInc/compound-engineering-plugin | 25k | — | ~549 | Automated safety check: Pass | MIT | |
| Reminddavidondrej/skills | 4.1k | — | ~266 | Automated safety check: Pass | MIT | |
| Science Communicationbrycewang-stanford/Auto-Empirical-Research-Skills | 4.5k | — | ~3.1k | Automated safety check: Pass | Custom licence | |
| Reportkv0906/pm-kit | 138 | — | ~1.7k | Automated safety check: Notes | MIT | |
| Stakeholder Summarytestdouble/han | 279 | — | ~6.3k | Automated safety check: Pass | MIT | |
| Contextpilot SavingsEfficientContext/ContextPilot | 140 | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Science Communication
brycewang-stanford/Auto-Empirical-Research-Skills
Translating technical findings for non-technical audiences. An agent skill from brycewang-stanford/Auto-Empirical-Research-Skills.
Report
kv0906/pm-kit
Executive briefing in plain language — report to me like I'm the CEO or product owner.
Stakeholder Summary
testdouble/han
Produces a plain-language stakeholder summary from an existing feature specification, for sharing with non-technical stakeholders before implementation kicks off.
Contextpilot Savings
EfficientContext/ContextPilot
A skill your agent uses when a user asks how many tokens (or how much context/cost) ContextPilot has saved, or wants a ContextPilot savings status/summary inside Hermes Agent — e.g.
Client Report Narratives
irinabuht12-oss/marketing-skills
Takes your raw campaign performance data and writes the executive summary paragraph that goes at the top of the report.
More from EveryInc/compound-engineering-plugin
All 37 skills in this repoCompound Learning Writer
EveryInc/compound-engineering-plugin
Records one solved and verified problem as a durable learning in the repository, but only when the reasoning is not already clear from the final code, tests or docs.
Compound Learnings Refresh
EveryInc/compound-engineering-plugin
Audits a repo's stored learnings against the current codebase, fixes stale, overlapping or superseded docs and reports on every document.
Compound Engineering Prototype
EveryInc/compound-engineering-plugin
Builds a throwaway prototype at just the fidelity needed to settle a specific how-it-should-work-or-feel question, before committing to an approach other work will treat as fixed.
Compound Engineering Setup
EveryInc/compound-engineering-plugin
Checks Compound Engineering plugin health and repo-local config, or scaffolds a Compound Pack when you ask for one by id.
PR Babysitter
EveryInc/compound-engineering-plugin
Watches an open GitHub pull request over time, routing review comments and CI failures to other skills until the PR is ready to merge.
CE Brainstorm
EveryInc/compound-engineering-plugin
Turns a vague or ambitious feature idea into a requirements-only plan through dialogue with you, sized to the work, before any code is written.
Related
Categories
Questions about WTF Plain-Language Explainer
What does WTF Plain-Language Explainer do?
Explains the last message, or a file, link or passage you give it, in plain language so you can say what it means and what you must decide without rereading the source. When you invoke it because you did not follow something, the agent decides the target from what you passed: nothing means its own most recent message, a path or link is read first, a pasted passage is used as is, and a short pointer such as a step number narrows it to that part of the conversation. If the target is still unclear, it asks one short question instead of guessing.
When should I use WTF Plain-Language Explainer?
WTF Plain-Language Explainer fits situations like: you did not understand the agent's last reply; A long document, link or pasted passage needs a short plain explanation; you need to know what a message wants you to decide or do.
How do I install WTF Plain-Language Explainer in Claude Code?
Run `npx skills add EveryInc/compound-engineering-plugin --skill wtf -a claude-code`. Or copy the skill folder (skills/wtf in EveryInc/compound-engineering-plugin) into .claude/skills/wtf in your project. Claude Code loads it when a task matches its description.
How do I install WTF Plain-Language Explainer in Codex?
Run `npx skills add EveryInc/compound-engineering-plugin --skill wtf -a codex`. Or copy the skill folder (skills/wtf in EveryInc/compound-engineering-plugin) into .agents/skills/wtf in your project. Codex loads it when a task matches its description.
Can I use WTF Plain-Language Explainer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add EveryInc/compound-engineering-plugin --skill wtf -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wtf, .gemini/skills/wtf, .github/skills/wtf and .opencode/skills/wtf in your project.
What does WTF Plain-Language Explainer need to run?
SKILL.md names no scripts, command-line tools or credentials: WTF Plain-Language Explainer is instructions for the agent only.
Does WTF Plain-Language Explainer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is WTF Plain-Language Explainer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does WTF Plain-Language Explainer use?
WTF Plain-Language Explainer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does WTF Plain-Language Explainer use?
About 549 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to WTF Plain-Language Explainer?
Skills that share tags, products or a category with WTF Plain-Language Explainer: Remind (davidondrej/skills, 4.1k stars), Science Communication (brycewang-stanford/Auto-Empirical-Research-Skills, 4.5k stars), Report (kv0906/pm-kit, 138 stars) and Stakeholder Summary (testdouble/han, 279 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains WTF Plain-Language Explainer?
EveryInc (a GitHub organization) maintains it in EveryInc/compound-engineering-plugin, which has 25,412 GitHub stars. The repository holds 37 skills in this directory. The repository was last updated on October 7, 2026.
Source: EveryInc/compound-engineering-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.