skills/communicate/SKILL.md
Communicate ideas and information to others with purpose, clarity, and integrity. Ensure that artifacts are structured and phrased in a way that is mindful of their audience while avoiding AI slop patterns. Use when the user requests assistance with writing, commentary, or communication; when they point out AI slop, when they ask things like "help me say", "write for [a specific audience or context]", "polish [comments, sentences, artifacts]", or the like.
npx skillsauth add synapseradio/ai-skills communicateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Write prose for others that has purpose, clarity, integrity, and depth. Structure and phrase communication appropriate in context, mindful of linguistic tradition and how people actually speak to each other.
This skill includes helpful reference files. Load all that are relevant to context.
Try to infer them from context. Ask the user if you cannot be certain.
Good writing fits the form of its function. Always read the fit reference.
You should always calibrate to your audience with the calibrate reference.
If you're explaining something that may be novel or unfamiliar to its recipient, read the analogize reference for instruction.
Clarity in writing is key. Order information wisely, and speak to it with presence with the clarify reference.
Good writing has identity with reasoned and applied voice. This is often a matter of activation, with instructions in the activate reference file.
When information is hedged, padded, or hidden in verbs within abstract nouns, make it concrete with the instructions in the strengthen reference.
Ground information with specificity for others to integrate it with their own experience. Instructions for doing so are in the illustrate reference.
When the writing is meant for an international audience, the across-languages.md reference file will help you.
Before any prose is written, avoid-slop is the last revision step. Instructions are in the avoid-slop reference file.
Here's the guide on how to signal confidence when you're communicating about facts., and here's the guide on how to bound scope to your claims so they can be stated with integrity..
Assumptions should always be surfaced transparently..
Arc gives writing a spine that keeps it coherent and engaging.
When multiple things are stated, they need to be arranged. | When writing something with more than one sentence, you need to think about rhythm. Voice asks who is speaking and from what position, and carries that through the piece. Always write with a distinct voice by reading and following the voice reference. | Writing should always fit to a register appropriate for its context.
Read this to understand the implications of the writing.
Read this to when you're discussing things that have different aspects or dimensions to ensure your writing matches. |
Prefer leading with questions, not arrogance. This mandatory guide will help. |
What's said needs not repeat.
Every word must earn its place.
Work with the user to de-blur and align before you start.
Set up todos when this skill is invoked without exception. When writing to artifacts, more than one draft is expected. If the user is asking for help on how to say something, you may not need multiple drafts, but you MUST still load at least one appropriate reference. Heavy tasks CAN and often DO require loading all references over the course of todos.
Use silence as a literary device where appropriate.
Trust the user, and don't be afraid to have a conversation with them to get things right.
tools
Turn a problem inside out to reveal hidden structure
testing
Verify epistemic integrity by aligning claims with evidence
tools
Combine viewpoints into coherent whole
tools
Generate and filter ideas into vetted options