Diagnose slow Attio requests and growing sync queues by measuring query complexity, pagination, concurrency, retries, and cache behavior. Compare a targeted change against a representative baseline while checking data correctness, freshness, and rollback thresholds.
Analyze and improve Attio integration latency and throughput from measured query shape, pagination, concurrency, retry, and cache evidence while preserving correctness. Use when Attio requests are slow or queues are backing up. Trigger with "Attio performance", "speed up Attio sync", or "Attio query tuning".
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
This skill tunes observed bottlenecks without promising a universal latency target. It keeps query complexity, rate limits, freshness, and mutation safety visible.
Use Read, Glob, and Grep to inspect query construction, pagination, concurrency, caches, and telemetry. Use WebFetch only for current official Attio documentation. Use Write or Edit after a measured hypothesis and rollback threshold are stated.
Use the workload's existing least-privilege Bearer token. Performance measurement does not justify additional scopes or access to broader CRM data.
Do not trade away correctness, auditability, or data freshness for latency without owner approval. Do not raise concurrency merely because the published global ceiling is higher.
Return baseline metrics, segmented bottleneck evidence, the selected hypothesis and change, correctness checks, comparable after-metrics, and the explicit rollback decision.
| Condition | Response |
|---|---|
| No representative baseline | Instrument and wait for usable evidence. |
| Query gets 429 despite low count | Inspect score-based complexity and shared workspace traffic. |
| Optimization changes results | Roll back and restore correctness first. |
| Cache serves stale schema | Invalidate it and tighten the freshness policy. |
Input:
symptom=query queue age; endpoint=record query; window=representative peak
Expected handoff:
bottleneck=filter-score; change=simplified-query; correctness=pass; p95=improved
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add a synthetic-data CI gate for customer-owned Abridge integration code. Test consent handling, note-review handoffs, redaction, and rollback behavior with mocked vendor boundaries, without connecting CI to a live Abridge or EHR tenant.
Triage Abridge recording, note review, Epic handoff, and access problems using observed symptoms and approved guidance. Identify the affected workflow stage, organize a minimal timeline, and prepare a redacted escalation record for the responsible team.
Map and review an Abridge clinical documentation workflow from consent and recording through draft review, evidence checks, edits, and final disposition. Keep clinician approval explicit, identify failure exits, and separate verified facts from tenant-specific details and pending approvals.
Audit how clinician-reviewed Abridge note sections map into Epic templates and downstream workflows. Use approved test records to document destinations, exceptions, evidence, rollback steps, and a go or no-go decision for a specific environment.
Review Abridge adoption and workflow value using local usage records, clinician feedback, and verified contract costs. Build an evidence based decision table covering adoption, quality, support burden, and options to expand, hold, or improve the rollout.
Prepare a bounded support bundle for an Abridge issue using allowlisted operational details such as versions, coarse timestamps, and correlation references. Exclude recordings, transcripts, patient identifiers, credentials, and unrestricted logs, then document redactions and review details.