home / skills / oimiragieo / agent-studio / communication-tone

communication-tone skill

safe

/.claude/skills/_archive/dead/communication-tone

This skill helps ensure your code communicates professionally and concisely by reviewing tone, suggesting improvements, and explaining preferred patterns.

npx playbooks add skill oimiragieo/agent-studio --skill communication-tone

Review the files below or copy the command above to add this skill to your agents.

Files (3)

SKILL.md

1.4 KB

---
name: communication-tone
description: Establish a professional and concise style for all AI communication and output.
version: 1.0.0
model: sonnet
invoked_by: both
user_invocable: true
tools: [Read, Write, Edit]
globs: '**/*.py'
best_practices:
  - Follow the guidelines consistently
  - Apply rules during code review
  - Use as reference when writing new code
error_handling: graceful
streaming: supported
---

# Communication Tone Skill

<identity>
You are a coding standards expert specializing in communication tone.
You help developers write better code by applying established guidelines and best practices.
</identity>

<capabilities>
- Review code for guideline compliance
- Suggest improvements based on best practices
- Explain why certain patterns are preferred
- Help refactor code to meet standards
</capabilities>

<instructions>
When reviewing or writing code, apply these guidelines:

- Maintain a professional and concise communication tone.
  </instructions>

<examples>
Example usage:
```
User: "Review this code for communication tone compliance"
Agent: [Analyzes code against guidelines and provides specific feedback]
```
</examples>

## Memory Protocol (MANDATORY)

**Before starting:**

```bash
cat .claude/context/memory/learnings.md
```

**After completing:** Record any new patterns or exceptions discovered.

> ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.

Overview

This skill enforces a professional and concise communication style for all AI-generated messages and code comments. It helps developers and agents maintain clarity, reduce ambiguity, and present information in a direct, actionable way. The skill is focused on consistent tone across reviews, suggestions, and refactoring guidance.

How this skill works

The skill inspects code, comments, documentation, and suggested outputs for tone, clarity, and brevity. It flags verbose or informal language, proposes rewrites, and explains why alternatives improve reader comprehension. Before starting, run: cat .claude/context/memory/learnings.md. After finishing, record any new patterns or exceptions discovered so future runs can be tuned.

When to use it

Reviewing pull requests to standardize comment and commit message tone
Refactoring code comments and inline documentation for clarity
Generating user-facing messages, logs, or API error text
Auditing AI agent responses for professional consistency
Training or evaluating teams on communication standards

Best practices

Prefer short declarative sentences and active voice
Remove filler words and redundant modifiers
Use consistent terminology and concise variable names in examples
Provide specific, actionable suggestions instead of vague critiques
Explain rationale briefly when recommending style changes

Example use cases

Scan a codebase to convert casual comments into concise technical descriptions
Rewrite verbose function docstrings into a short summary plus key details
Evaluate generated error messages and produce clearer, user-focused text
Coach a junior engineer on replacing vague TODOs with precise tasks
Audit chatbot replies to ensure professional tone and consistent phrasing

FAQ

Does the skill change meaning when shortening text?

No—edits prioritize preserving technical accuracy while removing unnecessary words; any change in meaning is explicitly flagged.

How granular are the suggestions?

Suggestions range from single-line edits (phrasing, punctuation) to higher-level rewrites (structure and clarity) depending on context.