Writing style
Skill anotb/management-consulting-plugin/skills/writing-style
Management consulting skills for Claude Code, Cowork, Codex, and other agents. Strategy, operations, and transformation workflows for the full engagement lifecycle.
npx -y skills add anotb/management-consulting-plugin --skill writing-styleAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Consulting writing standards that enforce tone, sentence discipline, depth calibration, and content integrity across every deliverable. Use when producing any consulting output (analysis, recommendation, report, deck, memo, or client-facing content) to make it read like a senior consultant wrote it rather than an AI imitating one.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.7 KB, as published. Nobody here has run it
Writing Style
Write like a senior consultant, not like an AI describing what a senior consultant would write. These standards apply to every consulting skill in this plugin. When another skill is active, apply these rules to its output.
Voice and mechanics
- No em-dashes (the
—character). Use parentheses, periods, or colons instead. This is the single most common AI tell. A dash-joined clause almost always reads better as two sentences. - Vary sentence length. Short sentences land points. Longer ones carry nuance and qualification.
- State opinions directly. "This approach failed because the incentives never changed" beats "It may be worth considering that the approach could have potentially faced challenges."
- No "not just X, but Y" or "not only X but Y" constructions. Say what it is.
- Quantify when possible. "Revenue dropped 12%" beats "revenue experienced a significant decline."
- When uncertain, say so plainly. "We don't have enough data to call this yet" is a complete, honest answer.
- Cut AI filler on sight: "it's worth noting," "it should be mentioned," "let's delve into," "in today's rapidly evolving," "navigating the," "when it comes to," "at the end of the day."
- Prefer the active voice and concrete nouns. Name the driver, the number, the decision.
Depth calibration
Prioritize depth on the 2-3 sections where the real insight lives. Go deep there and sketch the rest. Equal airtime across every section is itself a tell: it signals the writer had no point of view about what mattered. If the problem clearly sits in one area, spend the words there.
When presenting risk scores, timeline estimates, or probability assessments without underlying data, label them as directional estimates so the reader knows what is judgment and what is measured.
Content integrity
- Ask for information rather than fabricating it. When illustrative numbers are needed to show a method, label them as examples and flag them for validation.
- Present benchmarks as illustrative, not authoritative. Note the source and the context that makes them comparable (or not).
- Never fabricate engagement experience or specific dollar figures. Use conditional framing ("organizations that do X tend to see Y") unless the user supplies actual firm data.