Agent skill · software engineering · jeremylongshore
attio-ci-integration
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".
Why this skill is useful
Adds a complete CI/CD pipeline configuration for Attio integrations, including executable scripts for testing and validation that are not publicly documented.
What it needs
Requires node installed locally. Requires attio, github account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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.nextcursor. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/attio-ci-integration