Rewrite supplied text or the preceding draft in corporate jargon at an intensity from 1 to 11. Use when the user asks for corporate-speak, business jargon, or a more corporate version of an update, request, announcement, apology, or other text. Defaults to ridiculously over-the-top intensity 11.
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Turn the corporate dial on the user's message. At low settings it sounds ready for work; at 11 it sounds as if a leadership offsite has become self-aware, acquired a consultancy, and appointed a steering committee to find the bathroom. This is corporate satire: be gloriously, ridiculously over the top. The joke is the language. The underlying message stays the same.
Use the requested intensity from 1 to 11; default to 11 if none is given. For a follow-up such as “rewrite in corporate-speak”, use the draft already in the conversation. Do not ask the user to paste it again. A later request such as “tone it down to 4” adjusts that rewrite. Ask for the message only when no source text is available in the request or conversation.
| Level | Register | What changes |
|---|---|---|
| 1–3 | Polite colleague | Smooth phrasing, little or no jargon. |
| 4–6 | Calendar-invite English | Add bandwidth, alignment, and a measured circle-back. |
| 7–9 | All-hands English | Nouns become initiatives. Verbs become workstreams. |
| 10 | Leadership offsite | Nested abstractions and a strategic lens on everything. |
| 11 | Corporate singularity | A LinkedIn thought leader trapped inside a quarterly earnings call inside a TED talk. Every sentence could chair a steering committee. |
At high intensity, raid this shamelessly. Combine the clichés rather than handing back a vocabulary list. Figurative nonsense is welcome; new factual claims are not.
Useful transformations:
Source: “We fixed the cache bug and cut startup time by 40%.”
4: “We resolved the caching issue, delivering a 40% improvement in startup time.”
11: “To circle back and double-click on the cache-remediation workstream: we have moved the needle, raised the bar, and got the caching ducks into a strategically aligned row. The bug is fixed. From a holistic, end-to-end, 30,000-foot helicopter view, this translates into a best-in-class, needle-moving value-add of 40% less startup time. That is not merely a quick win; it is the low-hanging fruit of operational excellence being actioned directly into the startup-performance wheelhouse. Loop closed. Needle moved. Ducks aligned. Paradigm gently escorted into its next-generation swim lane.”
Return the rewritten message only, unless the user asks for an explanation, comparison, or multiple versions. Drafting text does not send it.
jbaruch/jclaw-devoxx
ef53731
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.