Build Attio workflows for sales pipelines and operational queues. Keep parent records separate from list-specific information, reuse existing list entries, and verify updates while treating notes and tasks as separate linked resources.
中文简介正在准备中。当前显示英语简介。
Build an Attio workflow around lists and entries while keeping record data, list-specific attributes, notes, and tasks correctly separated. Use when implementing pipelines, queues, or operational CRM processes. Trigger with "Attio lists", "Attio entries", or "Attio pipeline workflow".
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
This skill models a business process without confusing an Attio record with its membership in a list. It makes ownership of record attributes and entry attributes explicit.
Use Read, Glob, and Grep to inspect process rules, identifiers, mappings, and tests. Use WebFetch only for current official Attio documentation. Use Write or Edit after the list contract and mutation boundary are confirmed.
Use Bearer authentication with only the read or read-write scopes needed for list configuration, entries, notes, tasks, and parent records. Resolve 403 responses from endpoint scope documentation.
Bulk entry changes, task assignment, destructive removal, and any parent-record deletion require a preview of exact IDs and impact. Never treat a list slug as sufficient proof of record identity.
Return the list schema, parent-object check, membership decision, changed values, linked-resource IDs, verification result, and cleanup disposition.
| Condition | Response |
|---|---|
| Parent object is incompatible | Stop and choose the correct list or record. |
| Membership already exists | Reuse its entry ID; do not create a duplicate. |
| Entry and record values conflict | Apply the documented ownership boundary. |
| Removal intent is unclear | Refuse mutation and show entry versus record impact. |
Input:
list=sales-pipeline; parent=company-id; owned-entry-fields=stage,owner
Expected handoff:
membership=existing; update=verified; parent-record=preserved
This result shows that the list workflow changed only its owned entry values.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示英语简介。