communication

Enforce audience-aware tone and [ai] markers in human-facing prose.

6|2|Updated Jul 8, 2012

Search Tags:#documentation #tone #communication #audience-awareness #prose-style #ai-authorship #humble-inquiry

Ready to run

npx skills add https://github.com/athal7/dotfiles --skill communication-athal7

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: communication
Source: https://github.com/athal7/dotfiles/tree/main/skills/communication
Command: npx skills add https://github.com/athal7/dotfiles --skill communication-athal7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to writing human-facing prose with audience awareness and AI-authorship markers, ensuring consistent tone and clear attribution.

Core Features & Use Cases

Audience-aware tone for chat messages, reviews, emails, and docs.
Humble Inquiry to surface assumptions through questions.
Informal and concise voice to reduce fluff and increase clarity.
AI-authorship marker guidelines: prefix [ai] for AI-generated content; omit when relaying user words verbatim.
Use Case: A product update email tailored to a non-technical stakeholder while indicating AI assistance.

Quick Start

Draft your next human-facing message using audience-aware tone and prefix AI-authored text with [ai] when applicable.

Frequently Asked Questions about communication

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

FAQPage Schema

How do I make AI-generated prose more audience-aware for stakeholder emails?▼

Audience-aware prose is structured by enforcing tone rules like Humble Inquiry and Concise voice, tailoring content to specific readers. This approach refines human-facing text such as stakeholder emails, ensuring clarity and reducing unnecessary fluff for non-technical recipients.

When should I use AI-authorship markers in documentation and chat messages?▼

AI-authorship markers should be used by prefixing [ai] to AI-generated content in documentation and chat messages. You omit the marker when relaying user words verbatim, ensuring clear attribution and transparency for human-facing text across teams.

What is the Humble Inquiry tone for review comments and merge request descriptions?▼

Humble Inquiry is a communication tone that surfaces assumptions through questions rather than statements. Applied to review comments and merge request descriptions, it structures prose to clarify intent and foster collaborative dialogue across technical teams.

Can I use this approach to write informal and concise ticket descriptions?▼

Yes, you can apply informal and concise voice rules to write ticket descriptions. This approach reduces fluff and increases clarity, ensuring human-facing communication remains direct and audience-aware while maintaining appropriate AI-authorship attribution.

Does this method work for tailoring product update emails to non-technical stakeholders?▼

Yes, the method works for product update emails by applying audience-aware tone guidelines to tailor the message. It ensures the prose is accessible to non-technical stakeholders while indicating AI assistance through the appropriate authorship markers.