By channel
The same standard, tuned to the context
Note
This is the actual guidance the skill uses. This page is generated from the skill’s context rules. Read the exact source, context-modes.md, on GitHub (opens in a new tab).
Channel 1
Executive communication
- Keep background subordinate to the conclusion.
- Identify business impact, risk, owner, and timing.
- Avoid generic leadership language and motivational framing.
- Do not dilute uncomfortable findings with ceremonial praise.
Channel 2
Technical documentation
- Preserve commands, identifiers, paths, parameters, product names, and version details exactly.
- State assumptions, prerequisites, dependencies, and failure modes.
- Separate architecture decisions from implementation steps.
- Prefer explicit causal language over rhetorical simplification.
- Use passive voice where the object or state matters more than the operator.
- Do not replace precise terms with plainer but less accurate language.
Channel 3
Governance, risk, compliance, and policy
- Use
mustfor mandatory requirements,shouldfor recommendations, andmayfor permission. - Define scope, owner, evidence, exception handling, and review frequency.
- Preserve legal and standards terminology.
- Avoid claims of compliance without evidence.
Channel 4
Incident and security communication
Organize around:
- confirmed facts;
- current impact;
- containment and recovery status;
- unresolved risks and dependencies;
- owner, next action, and update time.
Do not speculate without labelling the statement as an inference or hypothesis. Avoid false certainty and premature declarations of resolution.
Channel 5
- Use a subject that names the issue or required decision.
- Open with the purpose or ask.
- Keep paragraphs short.
- Make ownership and deadlines explicit.
- Omit greetings and closings when the channel or relationship does not require them.
- Do not add an invitation to continue the discussion unless it serves a purpose.
Channel 6
Teams, Slack, SMS, and LinkedIn
- Use plain text unless the platform supports and benefits from richer formatting.
- Keep the message immediately pasteable.
- Avoid Markdown syntax in LinkedIn copy.
- Use compact paragraphs and minimal line breaks.
- Do not add a detached signature block when the user requests a single continuous message.
Channel 7
Reports and memoranda
- Use descriptive headings.
- Put the executive conclusion first.
- Separate evidence, interpretation, recommendation, and residual uncertainty.
- Use tables for comparison, ownership, status, or decision criteria.
- Avoid executive-summary language that merely repeats section titles.
Channel 8
Humour and sarcasm
- Match the requested darkness and bluntness.
- Preserve professional acceptability when requested.
- Target conduct, process failure, or absurdity rather than protected characteristics.
- Avoid language likely to create legal, HR, or reputational exposure when the output is intended for work circulation.