AI Skill Report Card
Managing Communications
Communication Management
Quick Start12 / 15
Python# Communication draft template draft = { "type": "email|slack|text", "to": "recipient", "subject": "clear subject line", "body": "concise, purposeful message", "tone": "professional|casual|urgent", "action_required": "yes|no", "send_permission": "pending" }
Recommendation▾
The Quick Start template is too abstract - provide an actual message draft example instead of a data structure
Workflow13 / 15
Progress:
- Review incoming messages - Check texts, emails, Slack for priority
- Draft responses - Create appropriate tone and content
- Update contact info - Note any changes in communication preferences
- Request send permission - Present draft for approval
- Send approved messages - Execute only after explicit permission
- Log communication - Track sent messages and follow-ups needed
Message Triage:
- Urgent (respond within 1 hour)
- Important (respond same day)
- Routine (respond within 48 hours)
- FYI (acknowledge receipt)
Recommendation▾
Add concrete input/output examples for contact updates and different communication platforms beyond just email and Slack
Examples17 / 20
Example 1: Email Draft Input: "Need to decline meeting invitation from Sarah about Q4 planning" Output:
Subject: Unable to attend Q4 planning meeting
Hi Sarah,
Thank you for the meeting invitation. Unfortunately, I won't be able to attend the Q4 planning session due to a scheduling conflict.
Could you share the meeting notes afterward? I'm happy to provide input asynchronously.
Best regards,
[Permission needed to send]
Example 2: Slack Response Input: "Team asking about project timeline in #dev-updates" Output:
@channel Current timeline for the API integration:
• Phase 1: Complete by Friday
• Phase 2: Starting Monday, ETA 2 weeks
• Testing: Final week of month
Will update if any blockers arise.
[Permission needed to send]
Recommendation▾
Include specific templates for common scenarios (meeting requests, status updates, follow-ups) rather than just general principles
Best Practices
- Default to concise: Respect recipient's time
- Lead with action items: Put requests/decisions first
- Match communication style: Mirror formality level of incoming message
- Include context: Reference previous conversations when relevant
- Set clear expectations: Specify next steps or timeline
- Always request permission: Never send without explicit approval
Common Pitfalls
- Don't auto-send: Always get permission first
- Don't over-explain: Avoid unnecessary background
- Don't ignore tone: Match the urgency and formality of the situation
- Don't forget follow-up: Track responses needed
- Don't mix multiple topics: One message per main topic
- Don't update contacts without verification: Confirm changes before updating records