chat-response-generator

Chat Response Generator

The Chat Response Generator skill helps you craft quick, effective responses for chat platforms like Slack, Teams, Discord, WhatsApp, or any real-time messaging environment. Whether you're responding to a question, acknowledging a message, providing an update, or handling a sensitive situation, this skill ensures your responses are clear, appropriate, and achieve their purpose.

This skill understands that chat communication is fast-paced and contextual. Messages need to be concise yet complete, friendly yet professional, and responsive to the specific situation. The skill helps you balance speed with thoughtfulness, ensuring you maintain relationships while communicating efficiently.

Great chat responses move conversations forward, provide value, and maintain positive relationships. This skill makes creating them fast while keeping quality and tone appropriate for each situation.

Core Workflows

Workflow 1: Direct Response

1. Read Context: Understand the message and situation
2. Determine Type: Identify response category (answer, acknowledge, defer)
3. Craft Reply: Write appropriate response
4. Check Tone: Ensure tone matches relationship and context
5. Send: Quick review and dispatch

Workflow 2: Complex Situation

1. Assess Sensitivity: Identify any delicate elements
2. Gather Information: Ensure you have what you need
3. Structure Response: Organize multi-part answer
4. Consider Implications: Think through how it will be received
5. Refine: Polish before sending

Workflow 3: Template Creation

1. Identify Pattern: Recognize recurring situations
2. Create Base Response: Build reusable template
3. Mark Variables: Identify customization points
4. Test: Use in real scenarios
5. Iterate: Refine based on effectiveness

Quick Reference

Response Types & Templates

1. Quick Answer

When you have the information they need:

[Direct answer]

[Optional: Brief context or caveat]

[Optional: Link to more info]

Let me know if you need anything else!

Examples:

Q: "What's the API rate limit?"

1000 requests per hour per API key.

If you need more, we can upgrade your account to the Pro tier (5000/hour).

Docs: [link]

Q: "When's the deadline for the proposal?"

End of day Friday (Jan 10).

Draft should go to @Sarah by Wednesday for review.

2. Acknowledge Receipt

When you've seen their message but need time to respond:

Examples:

3. Politely Decline

When you need to say no:

Examples:

4. Defer to Later

When it's not the right time:

Examples:

5. Ask for Clarification

When you need more information:

Examples:

6. Provide Update

When sharing status or progress:

Examples:

7. Handle Complaint

When someone's frustrated or upset:

Examples:

8. Express Gratitude

When thanking someone:

Examples:

9. Offer Help

When offering assistance:

Examples:

10. Set Boundaries

When you need to establish limits:

Examples:

Tone Guidelines

Professional but Friendly

• Use first names
• Casual language (contractions okay)
• Emoji where appropriate
• Warm and helpful

Concise but Complete

• Get to the point quickly
• Include necessary context
• Answer fully but briefly
• Use bullets for multiple points

Responsive but Boundaried

• Acknowledge quickly
• Set expectations for full response
• Don't feel obligated to instant replies
• It's okay to say "later"

Platform-Specific Considerations

Slack/Teams

Characteristics:

• Fast-paced, async
• Emojis and reactions common
• Threading keeps conversations organized
• Notifications can be noisy

Best Practices:

• Use threads for extended discussions
• React with emoji instead of "+1" messages
• Use status/away messages to set availability
• @mention only when necessary
• Edit messages instead of sending corrections

Response Time Expectations:

• Urgent: Within minutes
• Normal: Within a few hours
• Non-urgent: By end of day

Discord

Characteristics:

• More casual and community-focused
• Heavy emoji and GIF usage
• Multiple channels for topics
• Real-time and async mixed

Best Practices:

• Match the community's casual tone
• Use channel-specific language/memes
• React and engage liberally
• Voice channels for complex discussions

WhatsApp/SMS

Characteristics:

• Very personal
• Expected quick responses
• Mixed personal and professional
• Read receipts create pressure

Best Practices:

• Be more personal in tone
• Shorter messages
• Voice messages for complex topics
• Respect off-hours boundaries

Email Chat (Quick Replies)

Characteristics:

• Slightly more formal than chat
• Subject line matters
• Can be longer
• Less expectation of instant reply

Best Practices:

• Keep it brief for quick replies
• Use clear subject lines
• Can defer to scheduled response
• Include context (they may not remember)

Quick Response Templates

Common Situations

"I don't know"

"Not my area"

"Need more time"

"Thanks for the heads up"

"Saw your message, working on it"

"That's done"

"Running late"

"Out of office"

Emoji Strategy

When to Use Emojis

Good uses:

• Set friendly tone: "Thanks! 🙏"
• Show emotion: "That's frustrating 😞"
• Visual markers: "✅ Done"
• Lighten mood: "Oops 🤦"

Avoid:

• Too many (emoji soup)
• Replacing important words
• In very formal contexts
• When tone is already clear

Common Emoji Meanings

Response Time Framework

Immediate (< 5 mins)

• Urgent questions during work hours
• Quick confirmations
• Time-sensitive coordination

Quick (< 1 hour)

• Non-urgent questions
• Most work requests
• Team coordination

Same Day (< 8 hours)

• Detailed questions
• Non-urgent requests
• Lower priority items

Next Day+

• Deep work questions
• Requests outside work hours
• Non-urgent planning

Set Expectations: Use status messages, away indicators, or explicit "will respond by [time]" to manage expectations.

Common Pitfalls to Avoid

• Over-Explaining: Get to the point
• Too Formal: Chat is casual
• Leaving People Hanging: Acknowledge even if you can't answer fully
• Saying Yes to Everything: It's okay to defer or decline
• No Tone Indicators: Add emoji or context to avoid misinterpretation
• Always Instant: You don't have to reply immediately
• Not Using Threads: Keep channels clean
• Over-@mentioning: Only tag when needed

Integration Points

• Knowledge Base: Link to docs instead of re-explaining
• Task Management: Reference tickets, create tasks from chats
• Calendar: Share availability, schedule meetings
• Status Tools: Use status messages and automation
• Templates: Saved responses for common questions