본문으로 건너뛰기
cccskills
무료GitHub에 공개

attio-sdk-patterns

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".

실행 점수 미검증

설치 방법 보기

이럴 때 유용합니다

  • Creating a typed Attio REST client
  • Adding pagination for specific Attio endpoints
  • Refactoring Attio integration error handling

포함된 파일(2)

  • SKILL.md3.9 KB
  • references/official-docs.md2.1 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Attio Typed Client Patterns

Overview

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.

Prerequisites

  • Runtime, package manager, and existing HTTP conventions
  • Exact endpoints, methods, scopes, and response shapes
  • Tenancy and credential model
  • Existing tests and error-handling policy

Tool Discipline

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.

Current Contract

  • Attio REST requests use the https://api.attio.com/v2 base URL and endpoint-specific scopes.
  • Pagination is endpoint-specific: some operations use limit and offset, while others return a cursor such as pagination.next_cursor.
  • The Attio App SDK package attio serves apps running inside Attio and is not a universal REST client replacement.
  • Generated types can start from the official OpenAPI document, but application-level validation and tests still own runtime safety.

Authentication

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.

Instructions

  1. Inventory call sites and group the smallest useful endpoint surface.
  2. Reverify each method, path, scope, body, response, and paginator in official documentation.
  3. Define typed request and response boundaries with runtime validation for external data.
  4. Centralize base URL, authorization, timeouts, redaction, request IDs, and structured error translation.
  5. Implement separate offset and cursor iterators; bind each endpoint explicitly to the correct strategy.
  6. Retry only eligible transient failures, respecting rate limits and mutation idempotency.
  7. Add fixture, pagination-termination, error, redaction, and tenant-isolation tests.

Approval Boundaries

Do not replace an established client, add a generated dependency, or migrate production call sites without owner approval and compatibility evidence.

Output

Return the endpoint inventory, client interface, pagination mapping, error taxonomy, auth boundary, test evidence, migration plan, and rollback point.

Error Handling

ConditionResponse
Endpoint contract is ambiguousStop and recheck the official endpoint reference.
Runtime payload fails validationReturn a typed contract error and preserve redacted evidence.
Pagination repeats a pageAbort at the loop guard and record the endpoint strategy.
Tenant token does not match contextReject before sending the request.

Examples

Input:

runtime=TypeScript; endpoints=record query and task create; tenancy=multi-workspace

Expected handoff:

client=typed REST wrapper; pagination=endpoint mapped; tenant-tests=pass

Resources

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Adding regression checks to an Abridge integration repository
  • Testing consent and note-release handling
  • Checking logs for sensitive data exposure
jeremylongshore/tons-of-skills-marketplace2.9천2026년 10월 23일 업데이트

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Separate recording problems from upload failures
  • Investigate note creation delays and editor issues
  • Identify the responsible team for Epic handoff failures
jeremylongshore/tons-of-skills-marketplace2.9천2026년 10월 23일 업데이트

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Map a clinical note workflow for a care setting
  • Check where consent and patient identity are verified
  • Review draft notes against linked evidence before sign-off
jeremylongshore/tons-of-skills-marketplace2.9천2026년 10월 23일 업데이트

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking Abridge note section mappings to Epic templates
  • Auditing a department’s approved documentation handoff
  • Preparing test evidence and a go or no-go decision
jeremylongshore/tons-of-skills-marketplace2.9천2026년 10월 23일 업데이트

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing adoption after an Abridge rollout
  • Preparing evidence for a renewal decision
  • Comparing workflow outcomes across care settings
jeremylongshore/tons-of-skills-marketplace2.9천2026년 10월 23일 업데이트

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Preparing reviewed evidence for an Abridge support case
  • Documenting redactions and excluded data
  • Collecting approved operational details for an incident
jeremylongshore/tons-of-skills-marketplace2.9천2026년 10월 23일 업데이트

jeremylongshore의 스킬 모두 보기

이 스킬의 문제 신고