wtf

Re-explains the previous LLM response in plain UK English while preserving every detail.

3|Updated Nov 8, 2014
One-click install
npx skills add https://github.com/mintuz/.dotfiles --skill wtf-mintuz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wtf
Source: https://github.com/mintuz/.dotfiles/tree/main/agents/.agents/skills/wtf
Command: npx skills add https://github.com/mintuz/.dotfiles --skill wtf-mintuz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLM responses are often dense, jargon-heavy, or hard to follow. This Skill re-explains the immediately previous response in clearer, simpler language without losing any detail that changes how it should be understood. ## Core Features & Use Cases - Faithful Re-explanation: Rewrites the previous response with clearer structure and simpler wording while preserving every condition, value, identifier, and caveat. - Terminology Alignment: Reads project glossary files (CONTEXT.md, GLOSSARY.md, UBIQUITOUS_LANGUAGE.md, *.glossary.yml) to use canonical domain terms consistently. - Controlled Style: Follows ASD-STE100-inspired Simplified Technical English rules: active voice, short sentences, UK English, and defined abbreviations. - Use Case: After receiving a dense technical explanation of a deployment pipeline, invoke the Skill to get the same content restated in plain language with all constraints and warnings intact. ## Quick Start Use the wtf skill to re-explain the previous response clearly.

Frequently Asked Questions about wtf

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get a clearer explanation of a confusing AI response?

Invoke the wtf skill immediately after the confusing response. It rewrites that response in plain UK English with simpler structure while keeping every condition, value, and warning that affects how it should be understood.

How does the re-explanation handle technical jargon and domain terms?

The skill looks for CONTEXT.md, GLOSSARY.md, UBIQUITOUS_LANGUAGE.md, and *.glossary.yml files in the project and uses their canonical terms. Uncommon abbreviations and specialist terms are defined when they first appear.

What happens if there is no previous response to explain?

The skill states there is nothing to re-explain and asks which response or text to explain. It does not invent, quote, or guess a previous response.

Does re-explaining a response also carry out the task it describes?

No. The skill only re-explains; it attributes operational actions to the previous response and never starts new work or writes a new document from the content.

When should I not use this re-explanation approach?

Do not use it when you want the described work executed or a fresh document written. It is strictly for clarifying the immediately previous response, not for performing tasks or summarizing unrelated text.