Plan a staged release for an application that uses Attio’s REST API. The workflow checks configuration and schemas, runs contract tests and a read-only smoke check, verifies a canary write, monitors rollout signals, and prepares rollback evidence.
中文简介正在准备中。当前显示英语简介。
Plan and execute a staged deployment for an external Attio REST integration with secret injection, contract tests, read-only smoke evidence, canary writes, and rollback. Use when releasing Attio-backed services. Trigger with "deploy Attio integration", "Attio rollout", or "Attio release plan".
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
This skill releases application code that calls Attio's REST API. It uses progressive evidence so a bad schema mapping, scope, or retry policy is caught before broad CRM mutation.
Use Read, Glob, and Grep to inspect deployment manifests, secret names, health checks, migrations, and rollback commands. Use WebFetch only for current official Attio documentation. Use Write or Edit after the rollout target and approval boundary are confirmed.
Use the target environment's least-privilege single-workspace token or tenant-specific OAuth token. Confirm workspace identity and required endpoint scopes before canary traffic.
Production writes, token rotation, schema changes, and cleanup of canary data require exact target display and owner approval. Do not roll forward through unexplained validation or authorization failures.
Return artifact identity, environment checks, read smoke, canary evidence, traffic stage, observed metrics, rollback status, and residual risks.
| Condition | Response |
|---|---|
| Workspace identity is uncertain | Stop before enabling traffic. |
| Schema differs from staging | Disable writes and reconcile mappings. |
| 429 rate increases | Hold or reduce traffic and honor Retry-After. |
| Canary is not reversible | Do not use it; choose a safer proof. |
Input:
artifact=release-sha; environment=production; writes=initially-disabled
Expected handoff:
read-smoke=pass; canary=verified; expansion=approved; rollback=ready
This result binds the rollout decision to the tested artifact and rollback path.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示英语简介。