reply-composer

Email reply composition skill.

When to activate

Use this skill when the user asks to reply to an email, draft a response, or compose a new message.

Process

1. Gather context

Collect everything needed before writing:

• Read the original email with read_email
• If it's a thread, search for earlier messages in the thread: search_inbox(query='SUBJECT "<thread subject>"')
• Recall the sender profile from semantic memory
• Recall any style rules from procedural memory: recall("style_rule")
• Recall any previous replies to this sender: recall("<sender> reply_sent")

2. Analyze tone

Determine the appropriate tone from the original message:

Adapt to the sender's style. If the sender writes two-sentence emails, don't reply with five paragraphs.

3. Research if needed

If the reply requires information you don't have:

• Use search to look up facts, documentation, or context
• Use web_reader to read referenced URLs from the original email
• Recall topic context from semantic memory

4. Compose draft

Write the reply following these rules:

Structure:

• Greeting (match sender's style)
• Acknowledge their message (one sentence, reference specifics)
• Body (answer questions, provide information, address requests)
• Next steps or call to action (if applicable)
• Sign-off (check procedural memory for preferred sign-off)

Thread-aware replies:

• Reference specific points from the thread, not just the last message
• Don't repeat information already established in the thread
• If the thread has multiple participants, address the relevant ones

Length:

• Match the expected length to the complexity of the response
• Simple confirmations: 1-2 sentences
• Detailed answers: structured with bullet points or numbered lists
• Keep under 300 words unless the topic requires more