---
name: communicate
description: >-
  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.
metadata:
  context: fork
---

# Communicate

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.

## Questions you need answers for any piece of writing are headings below

Try to infer them from context. Ask the user if you cannot be certain.

### Purpose: What is the purpose of the piece?

[Your output should fit into its destination. Here is the manual.](./references/fit.md)

[After fitting, calibrate output by asking a few important questions.](./references/calibrate.md)

[When explaining, reach for analogy per the manual.](./references/analogize.md)

### Clarity: can the audience understand it?

[Begin by understanding what makes your output clear to others.](./references/clarify.md)

[Ensure your output may be activated in their minds.](./references/activate.md)

[When information is hedged, padded, or hidden in verbs within abstract nouns, make it concrete with the instructions in the strengthen reference.](./references/strengthen.md)

[Ground information with specificity for others to integrate it with their own experience.](./references/illustrate.md)

[Be sensitive to internationality and the indivudual uniqueness of your recipients, ensuring information survives transition across language.](./references/across-languages.md)

[Before any prose is written, avoid-slop is the last revision step. Instructions are in the avoid-slop reference file.](./references/avoid-slop.md)

### Integrity: does tone match evidence?

[Signal confidence appropriately and methodically.](./references/signal-confidence.md), [and remember to bound scope to what you claim.](./references/bound-scope.md).

[Assumptions should always be surfaced transparently.](./references/surface-assumptions.md).

### Shape: does this shape conform to audience expectations?

[What you communicate must be observed, and to engage attention, the arc of change must be understood.](./references/arc.md)

[Arrange statements in complimentary, cohesive style.](./references/arrange.md) |
[Pay attention to the rhythm implied by your output.](./references/rhythm.md)
[Write in distinctive voice by asking these leading questions.](./references/voice.md) |
[Register your words to their context.](./references/register.md)

### Depth: does this piece have the necessary depth to transmit its message?

[Take a moment to understand the implications of what it is you are writing.](./references/extract-implications.md)

[When more than one subject is present, the contrast creates dimensionality that is essential to be aware of.](./references/dimensionalize.md) |

[Lead your writing process by posing questions of the space. This mandatory guide will help you.](./references/pose-questions.md) |

## Non-negotiables

Every word must earn its place in service of concept, construction, or narrative.

Work with the user to de-blur and align intention 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 may require loading all references over the course of todos.

Omit cataphora and post-hoc explanation. Output only what is worth disturbance to natural quietude, such that concept, construction, and narrative survive transit in clarity.

Trust the user, and don't be afraid to have a conversation with them to get things right.