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

attio-ci-integration

Build automated checks for Attio integration changes using sample responses and response format tests. Produce pull request evidence without changing CRM records, with an optional, explicitly enabled read-only check against the live API.

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

원문원문 설명 보기

Build a bounded CI contract gate for an Attio integration using fixtures, schema checks, and an optional read-only smoke request. Use when Attio changes need pull-request evidence without mutating CRM data. Trigger with "Attio CI", "test Attio integration", or "Attio pull request gate".

jeremylongshore/tons-of-skills-marketplace

실행 점수 미검증

설치 방법 보기

이럴 때 유용합니다

  • Adding automated checks for Attio integration pull requests
  • Testing pagination, errors, and retry decisions
  • Checking test outputs for exposed secrets or personal data
  • Adding an optional read-only API connection check

포함된 파일(2)

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

SKILL.md(원문)

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

Attio Contract Gate for CI

Overview

This skill turns an Attio integration change into deterministic pull-request evidence. It separates offline contract tests from an explicitly enabled read-only API smoke test.

Prerequisites

  • A named repository and existing test runner
  • Sanitized Attio response fixtures or generated contract fixtures
  • A separately scoped CI credential only if a live smoke test is approved
  • The endpoint's current required scopes and pagination contract

Tool Discipline

Use Read, Glob, and Grep to inspect workflows, fixtures, client code, and secret names. Use WebFetch only for current official Attio documentation. Use Write or Edit only after identifying the target files, constraints, and verification plan.

Current Contract

  • Test the https://api.attio.com/v2 response envelope and application-owned normalization separately.
  • Treat pagination as endpoint-specific: some endpoints use limit and offset; others return pagination.next_cursor.
  • Keep mutation tests offline unless a dedicated disposable workspace and cleanup plan are approved.
  • Never expose an access token in logs, snapshots, test names, or artifacts.

Authentication

Use a single-workspace access token for one controlled workspace or OAuth for a multi-workspace app. Grant only the endpoint scopes required by the smoke test and pass the token through the CI secret store as a Bearer credential.

Instructions

  1. Inspect the changed endpoints, request methods, scopes, and response shapes.
  2. Add fixture tests for success, structured Attio errors, pagination termination, and retry classification.
  3. Validate that snapshots redact tokens, record values, webhook secrets, and personal data.
  4. Add a disabled-by-default live job that performs only an approved read request such as listing objects.
  5. Require explicit environment configuration before that job runs; skip it cleanly on forks.
  6. Record the exact test command, fixture revision, and live-smoke disposition in the PR evidence.

Approval Boundaries

Do not create, update, or delete records from ordinary PR CI. A mutation smoke test requires a named disposable workspace, bounded fixtures, cleanup verification, and repository-owner approval.

Output

Return the endpoint contract matrix, fixture coverage, redaction result, workflow change, local command result, and live-smoke status.

Error Handling

ConditionResponse
Fork has no secretSkip only the live job; keep offline tests required.
Fixture differs from docsConfirm the live endpoint and refresh the fixture deliberately.
Smoke returns 403Check the endpoint's required scopes; do not broaden blindly.
Mutation detectedFail the job and remove the mutating request.

Examples

Input:

change=record-query-filter; live-smoke=read-only; fork-policy=skip-secret-job

Expected handoff:

fixtures=pass; redaction=pass; live-read=pass; writes=none

This result proves the pull-request gate exercised the contract without receiving mutation authority.

Resources

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

abridge-ci-integration

무료

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일 업데이트

abridge-common-errors

무료

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일 업데이트

abridge-core-workflow-a

무료

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일 업데이트

abridge-core-workflow-b

무료

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일 업데이트

abridge-cost-tuning

무료

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일 업데이트

abridge-debug-bundle

무료

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의 스킬 모두 보기

이 스킬의 문제 신고