Build or refactor a typed client for Attio’s REST API, with workspace-aware credentials, endpoint-specific pagination, structured errors, and bounded retries. The skill helps define tested integration boundaries and keeps the REST client distinct from Attio’s in-product App SDK.
中文简介正在准备中。当前显示英语简介。
Build a typed Attio REST client with tenant-aware tokens, endpoint-specific pagination, structured errors, bounded retries, and contract tests while distinguishing it from the Attio App SDK. Use when creating or refactoring Attio integration code. Trigger with "Attio SDK", "Attio client wrapper", or "typed Attio API".
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
This skill designs a small REST client around the endpoints an application actually uses. It does not conflate a server-side REST wrapper with Attio's attio App SDK for in-product apps.
Use Read, Glob, and Grep to inspect clients, types, dependency policy, and tests. Use WebFetch only for official Attio REST, OpenAPI, and App SDK documentation. Use Write or Edit after the target abstraction and endpoint contracts are confirmed.
https://api.attio.com/v2 base URL and endpoint-specific scopes.pagination.next_cursor.attio serves apps running inside Attio and is not a universal REST client replacement.Inject a token provider that resolves the authorized workspace at request time. Do not place a global production token in source, client constructors, snapshots, fixtures, or logs.
Do not replace an established client, add a generated dependency, or migrate production call sites without owner approval and compatibility evidence.
Return the endpoint inventory, client interface, pagination mapping, error taxonomy, auth boundary, test evidence, migration plan, and rollback point.
| Condition | Response |
|---|---|
| Endpoint contract is ambiguous | Stop and recheck the official endpoint reference. |
| Runtime payload fails validation | Return a typed contract error and preserve redacted evidence. |
| Pagination repeats a page | Abort at the loop guard and record the endpoint strategy. |
| Tenant token does not match context | Reject before sending the request. |
Input:
runtime=TypeScript; endpoints=record query and task create; tenancy=multi-workspace
Expected handoff:
client=typed REST wrapper; pagination=endpoint mapped; tenant-tests=pass
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示英语简介。