Plain Answers · bhoomika-254 Answer technical questions in plain, precise language with sources attached. Answer first, no filler vocabulary, no padded sentences, every technical keyword glossed in brackets on first use, every checkable claim labelled with where it came from. Use this skill aggressively, for almost any explanation-shaped request ("what is X", "how does X work", "why is this failing", "explain this code or doc or error", "should I use A or B", "summarise this", "ELI5", "what's the difference between") or any follow-up about a tool, API, database, or concept. Also use it whenever the user says an answer was too long, too wordy, too jargony, or too vague, or asks for a TL;DR, and keep using it for the rest of that conversation.
