Use this skill to migrate an existing Attio integration when endpoints, schemas, client versions, or architecture change. It guides a contract comparison, compatibility work, shadow checks, a limited canary rollout, reconciliation, and a tested rollback plan.
中文简介正在准备中。当前显示英语简介。
Migrate an Attio integration through a contract-led inventory, OpenAPI and documentation diff, shadow validation, canary rollout, reconciliation, and tested rollback. Use when endpoint assumptions, client versions, schemas, or integration architecture must change. Trigger with "upgrade Attio integration", "Attio migration", or "Attio API contract change".
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
This skill migrates the integration that actually exists. It does not assume a generic historical version jump; it proves every affected endpoint and data shape against current Attio contracts.
Use Read, Glob, and Grep to inventory current assumptions and tests. Use WebFetch only for current official Attio documentation and OpenAPI. Use Write or Edit after the contract diff, rollout boundary, and rollback point are documented.
Preserve tenant-to-token binding and least privilege throughout the migration. Any new scope requires explicit justification, administrator approval, and a reversible credential plan.
Do not add scopes, alter destructive mutations, switch all tenants, or remove the rollback path without owner approval and recorded evidence.
Return the before-and-after contract matrix, risk classification, adapter plan, test evidence, shadow or canary results, reconciliation status, and rollback decision.
| Condition | Response |
|---|---|
| Official sources disagree | Pause the affected endpoint and preserve both references. |
| Shadow results diverge | Classify the mismatch and keep production on the old path. |
| Canary error budget fails | Roll back and retain captured redacted evidence. |
| Rollback cannot restore state | Stop before rollout and repair recovery first. |
Input:
change=replace hand-written record client; cohort=one test workspace
Expected handoff:
contract-diff=complete; shadow=matched; canary=pass; rollback=retained
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示英语简介。