Build a controlled workflow for Attio records by checking an object’s schema, mapping fields, and choosing query, create, or assert operations. Verify owned fields after writes, and require explicit approval and exact record IDs before deletion.
中文简介正在准备中。当前显示英语简介。
Implement a safe Attio record lifecycle for standard or custom objects, including schema discovery, query, create or assert, update, and delete controls. Use when building record synchronization or CRM write paths. Trigger with "Attio records", "Attio CRUD", or "sync Attio objects".
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
This skill builds a record workflow from the workspace's actual object and attribute schema. It favors deterministic identity and reversible updates over blind create calls.
Use Read, Glob, and Grep to inspect the local data model, mapping code, tests, and request wrapper. Use WebFetch only for current official Attio documentation. Use Write or Edit after the object contract and approval boundary are explicit.
POST /v2/objects/:object/records/query; this endpoint uses limit and offset.PUT and PATCH have different multiselect behavior; confirm the endpoint reference before updating.Send a single-workspace or OAuth access token as Authorization: Bearer <access_token>. Confirm the endpoint's object-configuration and record-permission scopes before any write.
Never infer a destructive target from a display name. Record deletion, bulk writes, schema changes, and overwrite updates require the exact workspace, object, record IDs, and owner approval.
Return the schema snapshot, identity rule, request plan, redacted response evidence, read-after-write comparison, and rollback or cleanup status.
| Condition | Response |
|---|---|
| Attribute slug is absent | Stop and refresh object definitions. |
| Assert matches unexpectedly | Stop; reconcile the matching attribute and source identity. |
| Multiselect result is wrong | Check PUT versus PATCH semantics before retrying. |
| Delete target is ambiguous | Refuse deletion and return candidate IDs for review. |
Input:
object=companies; operation=assert; match=domains; owned-fields=description,domains
Expected handoff:
schema=confirmed; identity=stable; write=verified; foreign-fields=untouched
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示英语简介。