Prove the smallest safe Attio REST connection by listing objects and validating the response envelope without changing CRM data. Use when checking a new token, workspace, or integration path. Trigger with "Attio hello world", "first Attio request", or "test Attio connection".
インストールする前に、エージェントに与えられる指示の中身を確認できます。
This skill proves authentication, workspace reachability, JSON parsing, and object discovery with one read-only request. It does not create a demonstration contact in a real CRM.
object_configuration:read scope required by the object-list endpointUse Read, Glob, and Grep to inspect the local client, environment-variable names, and tests. Use WebFetch only for current official Attio documentation. Use Write or Edit after confirming the repository and intended implementation file.
https://api.attio.com/v2.Authorization: Bearer <access_token>; Bearer authentication is the recommended form.GET /v2/objects and validate a { data: [...] } response.Use a workspace API key for a single workspace or OAuth for an app serving multiple workspaces. Do not request write scopes for this proof.
/objects with a bounded timeout and capture status plus content type.data and record only object slugs or counts that are safe to expose.Do not add create, update, assert, or delete calls to the first-read proof. Never print the access token or persist a raw workspace response.
Return the redacted configuration, status, response-envelope assertion, safe object summary, fixture-test result, and next integration boundary.
| Condition | Response |
|---|---|
| 401 | Verify credential injection and replace an invalid token. |
| 403 | Confirm object_configuration:read without broadening other scopes. |
| Non-JSON response | Preserve status/content type and stop parsing. |
| Unexpected workspace data | Stop and verify workspace identity. |
Input:
workspace=development; request=GET /v2/objects; writes=forbidden
Expected handoff:
auth=pass; envelope=pass; expected-object=present; secrets-exposed=0
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Build a synthetic-data CI gate for customer-controlled Abridge integration code without calling undocumented vendor interfaces. Use when adding regression checks to an Abridge deployment repository. Trigger with "test the Abridge integration".
日本語の概要は準備中です。原文の説明を表示しています。
Triage Abridge recording, note-review, Epic handoff, and access failures from observed evidence without inventing vendor error codes. Use when an Abridge clinical workflow is degraded. Trigger with "diagnose this Abridge issue".
日本語の概要は準備中です。原文の説明を表示しています。
Design and verify the clinician workflow from consent through recording, draft review, Linked Evidence, and final note disposition. Use when implementing or auditing an Abridge clinical documentation pathway. Trigger with "map the Abridge note workflow".
日本語の概要は準備中です。原文の説明を表示しています。
Verify the approved handoff of clinician-reviewed Abridge note sections into Epic templates and downstream workflows. Use when configuring or auditing Abridge-to-Epic documentation flow. Trigger with "verify the Abridge Epic handoff".
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate Abridge adoption, workflow value, and avoidable operational friction without inventing prices or vendor billing meters. Use when reviewing an Abridge rollout or renewal. Trigger with "analyze Abridge value".
日本語の概要は準備中です。原文の説明を表示しています。
Produce a PHI-minimized Abridge support bundle with provenance, redaction, and protected escalation boundaries. Use when support needs reproducible evidence for an Abridge issue. Trigger with "build an Abridge debug bundle".
日本語の概要は準備中です。原文の説明を表示しています。