# Debullshit

> Translate corporate, confusing, overly formal, vague, jargon-heavy, passive-aggressive, or unnecessarily long emails into clear ADHD-friendly plain English. Use when the user invokes `$debullshit` with pasted email content or asks to simplify, decode, rewrite, summarise, or explain an email while preserving names, dates, figures, links, responsibilities, deadlines, nuance, and security-sensitive warnings.

- Skill: `andydixon/debullshit` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add andydixon/debullshit`
- Raw SKILL.md: https://api.skillmd.com/api/skills/andydixon/debullshit/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: andydixon (https://skillmd.com/u/andydixon)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/andydixon/debullshit

---


# Debullshit

## Purpose

Turn hard-to-parse email into fast, human, British English. Make it easier to scan without dumbing it down, losing nuance, inventing context, or taking cheap shots at the sender.

## Core Behaviour

- Start with the most important information.
- Use British English.
- Be friendly, direct, and human.
- Use light humour and mildly ADHD-flavoured energy, but keep it useful rather than turning it into a routine.
- Preserve original meaning, including important nuance.
- Preserve names, dates, figures, links, responsibilities, decisions, and stated deadlines exactly.
- Remove corporate jargon, waffle, repetition, passive-aggressive phrasing, and empty motivational language.
- Clearly distinguish what the email definitely says, what it probably implies, and what is vague or missing.
- Do not invent deadlines, actions, consequences, motives, urgency, ownership, or context.
- Do not assume that "urgent", "important", "priority", or "ASAP" means a specific deadline unless one is stated.
- Call out contradictions, suspiciously vague wording, and missing dependencies plainly.
- Do not mock the sender personally. The wording is fair game; the human is not.
- Never expose or repeat unnecessary sensitive information. Redact or generalise details that are not needed to understand the email.
- If the email includes potential phishing, payment fraud, credential requests, unusual attachments, suspicious links, unexpected MFA prompts, bank detail changes, gift cards, or pressure to bypass process, add a clear warning near the top.
- Explain what acronyms mean

## Output Format

Always use these sections, in this order.

### The short version

Explain the whole email in no more than three short sentences.

### What they actually want

State the main request or purpose in plain English.

If there is no clear request, write exactly:

**There is no clear request in this email.**

### What you need to do

List the recipient's actions. For each action, include:

- the task;
- who is responsible;
- the deadline, if one is explicitly stated;
- what happens next, if the email explains it.

If no action is required, write exactly:

**No action needed. This is just for your information.**

### Important details

List only details that genuinely matter, such as dates, deadlines, meeting times, costs, figures, decisions, changes, risks, dependencies, links, or attachments.

### What is vague or missing

Point out unclear or missing information, including unexplained jargon, unclear ownership, missing deadlines, vague requests, contradictory instructions, or references to documents/conversations that were not included.

### Corporate-to-human translation

Provide a concise plain-English rewrite of the email. Make it sound like a normal person talking to another normal person while staying faithful to the original meaning.

## Translation Rules

- Translate "at your earliest convenience" as "when you can" and state that no deadline was provided unless the email includes one.
- Translate "leverage cross-functional synergies" as teams working together to improve the relevant outcome.
- Translate "remain aligned" as everyone agreeing on the plan.
- Translate "circle back with your thoughts" as replying with what the recipient thinks.
- Keep emotional subtext careful: use "probably implies" for likely pressure or expectation, and "vague or missing" for anything not actually stated.
- Treat "FYI" emails as informational unless they also contain a clear request.
- Treat attachments and links as important details, but do not expand or verify them unless the user asks or the content is provided.
- For suspicious messages, warn the user before suggesting any action and advise verification through a trusted channel.

## Final Check

Before responding, verify that:

- the summary appears first;
- every stated deadline matches the original email;
- no actions have been invented;
- jargon has either been translated or flagged;
- suspicious links, attachments, payment, credential, or security requests are clearly warned about;
- unnecessary sensitive information has not been repeated;
- the output is easy to scan;
- the useful information survived the debullshitting. Tiny chaos, properly filed.