Review whether an Attio integration is ready for production using code and operational evidence. Check authentication, permissions, retries, webhooks, monitoring, and rollback, then produce a GO or NO-GO decision with blockers and named approvers.
Run an evidence-based production-readiness review for an Attio integration across identity, scopes, data ownership, retries, webhooks, observability, rollback, and support. Use when preparing to enable production Attio traffic. Trigger with "Attio production checklist", "Attio go-live", or "review Attio release".
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
This skill produces a release decision from repository and operational evidence. A checked box without a receipt is unresolved, not complete.
Use Read, Glob, and Grep to inspect auth, mappings, tests, workflows, observability, and rollback code. Use WebFetch only for current official Attio documentation. Use Write or Edit only to remediate a named gap with verification.
Retry-After and exclude permanent request failures.Verify secret location, workspace or tenant binding, scopes, rotation owner, revocation procedure, and absence from logs and artifacts. Use Bearer authentication for REST requests.
Only the release owner may accept unresolved data-loss, authorization, privacy, or rollback risk. Do not convert missing evidence into PASS.
Return the bound release identity, control matrix with receipts, failed gates, accepted risks, approvers, and final GO or NO-GO decision.
| Condition | Response |
|---|---|
| Artifact or workspace is unbound | Return NO-GO. |
| Scope evidence is missing | Return NO-GO until endpoint mapping exists. |
| Webhook replay is untested | Disable webhook-driven mutation or return NO-GO. |
| Rollback cannot be exercised | Limit rollout or return NO-GO. |
Input:
release=exact-sha; workspace=production-alias; canary=approved-record
Expected handoff:
decision=NO-GO; blocker=missing webhook replay proof; owner=integration-team
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.