professional-communication

Guide technical communication for software developers. Covers email structure, team messaging etiquette, meeting agendas, and adapting messages for technical vs non-technical audiences. Use when drafting professional messages, preparing meeting communications, or improving written communication.

1.04x

Quality

81%

Does it follow best practices?

Impact

95%

1.04x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Evaluation results

97%

Communicating a Release Delay to Executives

Email structure and audience adaptation

Criteria

Without context

With context

Subject line format

80%

100%

Key message upfront

90%

100%

What-Why-How present

100%

Scannable formatting

100%

No unexplained technical jargon

100%

Business impact framing

90%

100%

Clear action or decision

80%

70%

Active voice

90%

100%

No filler words

90%

100%

Proper email sign-off

100%

98%

10%

Drafting Team Chat Messages for a Distributed Engineering Team

Team chat messaging etiquette

Criteria

Without context

With context

No Hello in DM

86%

100%

Direct request to Maya

70%

100%

PR context in DM

100%

Working-out-loud status post

100%

Status post is async-friendly

100%

Follow-up in thread

66%

86%

No unnecessary @mention in status

100%

No Slack Novel

80%

100%

Correct channel choice

100%

92%

-1%

Preparing Meeting Communication for an Architecture Decision

Meeting agenda and summary communication

Criteria

Without context

With context

Agenda: clear objective

100%

Agenda: timed items

100%

Agenda: preparation section

100%

Agenda: expected outcome

100%

Summary: attendees listed

100%

Summary: key decisions

100%

Summary: action item checkboxes

53%

Summary: next steps

100%

Summary: heading format

100%

80%

Documentation-before-meeting

100%

Scannable formatting

100%

Repository: softaworks/agent-toolkit
Commit: 3027f20

Evaluated: 30 days ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Communicating a Release Delay to Executives Drafting Team Chat Messages for a Distributed Engineering Team Preparing Meeting Communication for an Architecture Decision

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.