Ship the analysis: the CRM update, the post, the email.
“The analysis is done. How do I get it into the CRM and out to the team?”
Takes a read's output and drafts what goes out, draft-first and fully logged, ready to paste or write directly when connected.
What this skill does
This is the write-side. The other skills read and analyze; this one ships the result. Hand it an account verdict, a usage story, or a ranked list and it drafts what goes out: the CRM field update, the channel post, the personalized follow-up email, the next-touch sequence. Everything is a draft first and everything is logged, so nothing leaves the loop without your eyes on it.
Inputs
- Works today with: the analysis output plus where it should go (a field, a channel, a person). The skill returns ready-to-paste copy and the exact record or field to drop it in.
- More powerful connected to a CRM: it writes the field update and the contact record directly, with duplicate checking.
- More powerful connected to a channel tool: it posts or drafts the message in the right place.
- Sharper with an outreach tool: drafts a multi-touch sequence in your voice from a style guide you provide.
How it works
- 1Operation types
One of: crm_field_update, crm_contact_writeback, channel_post, channel_draft, direct_message, outreach_draft, sequence. The skill routes each request to the right operation and returns a structured confirmation.
- 2Draft-first by default
Email drafts and channel messages are created as DRAFTS, not sends, so the person can review before it goes out. Autosend is an explicit, per-workflow opt-in, never the default.
- 3Idempotent CRM writes
Before creating a contact, the skill checks for a duplicate. If one exists, it updates instead of creating, so you never pollute the CRM with duplicate records. Field updates capture the before and after value.
- 4Full auditability
Every write logs a row: timestamp, operation type, target (record and field, or channel and message), before and after values, and which workflow called it. No silent writes, ever.
- 5Honest connector failure
If a step asks to post to a channel but the channel tool is not connected, the skill says so and aborts that operation. It never fabricates a success.
Output format
CRM WRITE-BACK COMPLETE · 12 contacts processed
Name Operation Notes
Contact A CREATED verified email + phone written
Contact B UPDATED existed, added mobile + profile
Contact C UPDATED existed, updated title
Contact D EXISTING (skip) all fields already populated
Contact E SKIPPED email not found, not written
Summary: 4 created · 6 updated · 1 unchanged · 1 skipped
Audit trail: 12 rows appended to your log
---
CHANNEL POST (DRAFT) · #gtm-pipeline
Mode: draft (autosend off) - review and send when ready
Message: THE DAILY DROP - Friday... [full copy ready to post]
Audit: 1 row appended
Tips
- Draft-first is the default. Autosend requires an explicit opt-in.
- No silent writes. Every operation logs an audit row with before and after values.
- Idempotency on contact writes. Check for a duplicate, update instead of creating.
- Honest failure. A missing connector returns "not connected, operation aborted," never a fake success.
Read how an account actually uses you.
Turns raw usage into per-capability adoption tiers, a 12-week trend on each, power-user IDs, and a ghost-active flag.
Get a structured account read straight from your CRM.
A sixty-second summary, a multi-source activity audit, a qualification-vs-stage gap check, and an 8-state deal-risk verdict.