plain_talk

Rewrites AI output to remove jargon, filler, and enforce conclusion-first phrasing.

5|1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/WissingChen/my_code_config --skill plain-talk-wissingchen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plain_talk
Source: https://github.com/WissingChen/my_code_config/tree/main/my_skills/plain_talk
Command: npx skills add https://github.com/WissingChen/my_code_config --skill plain-talk-wissingchen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI responses often contain buzzwords, self-coined terms, empty affirmations, and repetitive summaries that obscure the actual answer. This Skill enforces a plain-language output contract so every reply leads with the conclusion and uses concrete everyday words. ## Core Features & Use Cases - Jargon Replacement Table: Maps common buzzwords (e.g., "empower", "closed loop", "alignment") to direct plain-language equivalents, and bans self-invented terms entirely. - Pre-Send Checklist: Every reply is checked for conclusion-first structure, unexplained terminology, filler phrases, and unnecessary length before being sent. - Honest Uncertainty Marking: External facts and numbers must carry sources; unverified claims are explicitly marked as "not yet verified" or "my guess". - Use Case: A researcher asks for a project status update. Instead of a long report full of process narration and buzzwords, the reply opens with the decision-relevant conclusion in three sentences, with sources attached to any external claims. ## Quick Start Load the plain_talk skill at the start of the session and ask the assistant to answer all subsequent questions in plain, conclusion-first language.

Frequently Asked Questions about plain_talk

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

FAQPage Schema
How do I make AI responses less jargon-heavy?▼

Load this Skill at session start so every reply passes a jargon filter before being sent. It replaces buzzwords with direct equivalents from a fixed mapping table and bans self-invented terms, forcing concrete wording instead.

How to enforce conclusion-first answers from an AI assistant?▼

The Skill's output contract requires the first sentence of every reply to be the conclusion or answer, followed only by necessary evidence and next steps. A pre-send checklist rewrites any reply that fails this rule.

Does this Skill change the factual content of answers?▼

No, it only changes how answers are phrased and structured. External facts, paper conclusions, and numbers must still carry sources, and uncertain statements are explicitly labeled as unverified or speculative.

When should the plain language rule be relaxed?▼

Technical terms are allowed when they are more accurate than plain wording, provided they are explained on first use. Detailed expansions are also permitted when the user explicitly asks for more detail.

What are the limitations of a prompt-based style enforcer?▼

It relies on the model following the checklist consistently and cannot mechanically guarantee compliance in every reply. It also does not verify factual accuracy of sources, only that claims are attributed or marked as unverified.