@di-atomic/customer-comms-reader

@di-atomic/customer-comms-reader

Name
@di-atomic/customer-comms-reader
Tagline
What happened with this client last week, with every line traceable to a record you can open.
Hero subhead
It reads one authenticated Google Workspace account for a named client over a bounded window and returns what was said, decided, promised and left unanswered. Reads only. Never replies, sends or files.
Who it's for
Anyone running several client relationships whose real state lives in Gmail, Calendar and Drive, and nowhere else.
Version
0.1.0
Tier
beta
Path type
guidance-only
Hero image
Hero image
Diagram image
Diagram image
Install command
opvs-skills install @di-atomic/customer-comms-reader
Trigger phrase
what happened with this week
Marketplace URL
https://market.opvs.ai/v/di-atomic/customer-comms-reader
Blog URL
https://di-atomic.com/blog/shipping-di-atomic-customer-comms-reader
Stat 1 value
201 vs 35
Stat 1 label
what Gmail's result count claimed, against what was actually there
Stat 2 value
44 of 44
Stat 2 label
action items Google's note-taker had already tagged with an owner
Stat 3 value
3
Stat 3 label
scripts that gate every extract with PASS or FAIL and a number
Stat 4 value
0
Stat 4 label
replies, sends, files or archives. It reads and nothing else
What headline
A readout that would rather say "I cannot see it" than guess
Cap 1 icon
🔗
Cap 1 title
Every claim resolves, or it does not ship
Cap 1 desc
Harvest writes a manifest before any reasoning happens, so each claim can be checked against a record that provably exists. An id that does not resolve is treated as fabricated, not as a lookup miss.
Cap 2 icon
🕳️
Cap 2 title
Absence is a finding
Cap 2 desc
"No transcript available" is never rendered as "no decisions were made." A meeting with no notes is a recorded fact carrying its own source id, because the first phrasing tells you an account is quiet when it may be deciding things without you.
Cap 3 icon
📉
Cap 3 title
Drift measured against that person's own baseline
Cap 3 desc
Escalation is a delta, not a level. A permanently terse engineer is not an alarm; a warm client turning terse is. Six structural signals read RSVP shifts, reply-length collapse and latency stretch, so they need no language understanding at all.
Showcase headline
The demo is the product
Showcase before caption
Naive: "Quiet week with VayaPin, nothing to report."
Showcase after caption
Actual: zero emails, one meeting with all five invitees accepted, no notes doc. A meeting ran, and what was decided is not visible from here.
Diagram caption
Two phases with a file between them. Harvest reads Gmail, Calendar and Drive and writes harvest.json using Google's own field names. Reasoning runs over that file and reads nothing.
Worked title
Three ways the tooling lied, each one exiting 0
Worked example
resultSizeEstimate reported 201 for a true paginated count of 35, measured by re-running one query while varying only maxResults. The --output flag exits 0 and writes no file, while escaping the working directory fails loudly, which is what trains you to trust it. And 1 message in 35 was an unsent draft whose id is genuine, so attribution checking cannot catch it.
Worked framing
All three return success. None raise. The only way any of them surfaced was checking the result against something known independently, which is the same discipline the skill imposes on its own output one layer down.
Rel 1 icon
🔁
Rel 1 name
@di-atomic/retention
Rel 1 desc
Decides a save move from signals someone else supplies. This produces the signals and decides nothing.
Rel 1 url
https://di-atomic.com/skills/retention
Rel 2 icon
📊
Rel 2 name
@di-atomic/sales-pipeline
Rel 2 desc
Operates the CRM boards behind the deal. This reads the correspondence around it.
Rel 2 url
https://di-atomic.com/skills/sales-pipeline
Rel 3 icon
🧭
Rel 3 name
@di-atomic/kpi-advisor
Rel 3 desc
Reads the numbers a business reports. This reads the relationship those numbers sit inside.
Rel 3 url
https://di-atomic.com/skills/kpi-advisor
CTA headline
Stop reconstructing a client week by scrolling
CTA description
Guidance-only, so there is no backend and no API key to hand over. Action-item recall for this task class measures around 77%, so every extract closes with counts per surface and what it could not reach.
Upstream license
MIT