communicating

Enforce concise, unambiguous team messages with one accountable person per task.

8|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/usurobor/cnos --skill communicating
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: communicating
Source: https://github.com/usurobor/cnos/tree/main/src/packages/cnos.core/skills/agent/communicating
Command: npx skills add https://github.com/usurobor/cnos --skill communicating

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Every word carries weight and must be chosen deliberately to reduce ambiguity and prevent unnecessary chatter, ensuring clear and accountable team communication.

Core Features & Use Cases

  • Establish clear responsibility and accountability via RACI before any task.
  • Enforce concise, honest communication with no fluff, hedging, or hype, and encourage direct, respectful language.
  • Apply to intra-team updates, task briefings, and external communications to maintain coherence and trust.

Quick Start

Draft a one-sentence update that states the task and who is responsible, with clear next steps and no fluff.

Frequently Asked Questions about communicating

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I improve team communication clarity and enforce accountability in task updates?

To improve team communication clarity, you must ensure every word is purposeful by assigning exactly one accountable person per task using RACI and eliminating fluff or hedging in status updates. This prevents ambiguity and unnecessary chatter.

What is the best way to write a concise team briefing without unnecessary chatter?

The best way to write a concise team briefing is to draft a one-sentence update stating the task and the responsible person, followed by clear next steps, using direct language with no fluff, hype, or hedging.

How does RACI accountability improve internal message brevity?

RACI accountability improves internal message brevity by establishing clear responsibility before any task begins, which removes the need for excessive explanation and enforces one accountable person per task to maintain direct, unambiguous communication.

Can I use this approach for both internal status updates and external communications?

Yes, you can use this approach for both internal status updates and external communications. Applying concise, honest language with no fluff and clear accountability maintains coherence and trust across all intra-team and external messages.

When should I not use direct, concise language in team messages?

You should not avoid direct, concise language in team messages when communicating task briefings or status updates, as this approach enforces honesty and respect while preventing unnecessary chatter and ambiguity in all teamwork communications.