# Confrontational Rhetoric > A methodology for speaking uncomfortable truths plainly, stripping away euphemism to make reality undeniable. This skill transforms diplomatic vagueness into direct naming that forces engagement wi... - Skill: `sethmblack/confrontational-rhetoric` (Agent Skill) - Install (CLI): `npx skillmds add sethmblack/confrontational-rhetoric` - Raw SKILL.md: https://api.skillmd.com/api/skills/sethmblack/confrontational-rhetoric/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - License: MIT - Author: sethmblack (https://skillmd.com/u/sethmblack) - Updated: 2026-09-08 - Page: https://skillmd.com/skills/sethmblack/confrontational-rhetoric --- # Confrontational Rhetoric A methodology for speaking uncomfortable truths plainly, stripping away euphemism to make reality undeniable. This skill transforms diplomatic vagueness into direct naming that forces engagement with what actually is. ## When to Use - When polite language obscures the truth of a situation - When euphemisms serve to maintain unjust arrangements - When audiences need to confront realities they prefer to avoid - When clarity would be more effective than diplomacy - When naming something directly would shift power dynamics - When comfortable framing prevents necessary action ## Inputs | Input | Required | Description | |-------|----------|-------------| | input_data | Yes | The primary data or content to analyze | | context | No | Additional background or constraints (default: none) | | output_format | No | Preferred format for results (default: structured markdown) | ## Workflow ### Step 1: Gather and Review Inputs Collect all relevant information: - Review the provided data and context - Identify key parameters and constraints - Clarify any ambiguities or missing information - Establish success criteria ### Step 2: Analyze the Situation Perform systematic analysis: - Identify patterns and relationships - Evaluate against established frameworks - Consider multiple perspectives - Document key findings ### Step 3: Generate Recommendations Create actionable outputs: - Synthesize insights from analysis - Prioritize recommendations by impact - Ensure recommendations are specific and measurable - Consider implementation feasibility ## Core Methodology ### Step 1: Identify the Euphemism Find the polite language that masks reality: - What words are people using to make the situation sound neutral? - What framing makes injustice or dysfunction seem natural? - What terms would change if the powerful were the ones affected? - What is being called something other than what it actually is? ### Step 2: Name It Plainly Replace euphemism with direct description: - Use concrete, specific language instead of abstract terms - Call actions what they are, not what they're marketed as - Describe effects, not intentions - Choose words that create accurate mental pictures ### Step 3: Make It Undeniable Build your case so it cannot be dismissed: - Connect the plain name to observable facts - Show the gap between what's said and what's done - Use their own logic against comfortable narratives - Ask questions that force acknowledgment ### Step 4: Address Directly Speak TO your audience, not about the situation: - Use "you" to create accountability - Make it personal without making it an attack - Channel intensity through disciplined language - Every word chosen, every phrase measured ### Step 5: Hold the Ground Maintain the plain naming despite pushback: - Expect discomfort and do not retreat from it - Refuse to return to euphemistic framing - Let the discomfort do its work of prompting change - Remember: comfort is often the enemy of truth ## Examples of Application ### Corporate Context **Euphemism:** "We're rightsizing the organization for efficiency." **Plain naming:** "We're firing 500 people to increase shareholder returns. Let's call layoffs what they are and discuss who benefits and who pays." ### Political Context **Euphemism:** "Enhanced interrogation techniques." **Plain naming:** "Torture. The reason they invented new words is because the old word accurately describes what they're doing and makes people uncomfortable." ### Social Context **Euphemism:** "We have a diversity problem." **Plain naming:** "We have an exclusion practice. The problem isn't that diverse people don't exist - it's that our systems weren't built for them and we haven't changed those systems." ### Personal Context **Euphemism:** "I'm not sure it's the right time." **Plain naming:** "I'm afraid. Let me name my fear instead of hiding behind timing." ## Key Principles 1. **Euphemism serves power** - When language softens reality, ask who benefits from the softening 2. **Clarity is not cruelty** - Being direct about hard truths is not the same as being unkind; sometimes it's the kindest thing 3. **Controlled intensity** - Passion channeled through disciplined language is more powerful than unfocused anger 4. **The truth sounds like anger** - When people have been lied to long enough, honesty becomes unrecognizable 5. **Name to change** - The goal isn't confrontation for its own sake; it's confrontation that forces engagement with reality ## Calibration Notes This skill exists on a spectrum. Not every situation requires maximum directness. The question is always: does the current framing serve truth or obscure it? Sometimes diplomatic language builds necessary bridges. But when diplomacy becomes a way to avoid necessary confrontations, plain naming becomes essential. The measure of success is not whether people are uncomfortable - it's whether they can no longer pretend they don't understand what's actually happening. ## Outputs **Primary Output:** A structured analysis document that identifies and articulates patterns, insights, and actionable recommendations based on the input data. **Format:** ```markdown ## Analysis: [Topic] ### Key Findings - [Finding 1] - [Finding 2] - [Finding 3] ### Recommendations 1. [Action 1] 2. [Action 2] 3. [Action 3] ``` **Example output:** See the Example section below for a complete demonstration. ## Constraints - Do not use this analysis as the sole basis for critical decisions - Do not apply this framework to situations outside its intended scope - Acknowledge that analysis is based on available data, which may be incomplete - Honor the complexity of real-world situations that resist simple categorization - Present findings with appropriate confidence levels - Recognize the limits of the methodology ## Example **Input:** - input_data: [Specific example input] - context: [Relevant background] **Output:** [Detailed demonstration of the skill in action - showing the complete process and final result] **Why this works:** This example demonstrates the key principles of the skill by [explanation of what makes it effective].