handle-reply

Instructions

State check. This skill assumes a CRM is connected, at least one sender is configured with instructions, and the org has approved message examples to anchor voice. Check the CRM connection, load sender instructions, and pull message examples before drafting. If no sender instructions exist, ask the user to define voice once so every reply lands consistent — don't fall back to a generic tone. If no CRM is connected, the skill still runs for the draft itself, but skip the CRM write steps and tell the user.

Step 1 — Load the thread and the sequence context

Pull the sequence and the latest reply:

• swan-search-sequences filtered to the contact or company to find the active sequence.
• swan-get-sequence for the full thread and the original outbound message.
• hubspot-search-objects on Contacts + Companies to confirm CRM state (lifecycle stage, owner, deal associations).

If the response is large, read the full JSON from files/tool-outputs/swan-get-sequence_<callId>.json in swan-execute-code and print only the last 2-3 thread turns plus the sequence goal.

Step 2 — Classify intent

Read the reply once and pick exactly one bucket. Keep the classification one line.