Agent skill · software engineering · jeremylongshore
attio-upgrade-migration
Migrate an Attio integration through a contract-led inventory, OpenAPI and documentation diff, shadow validation, canary rollout, reconciliation, and tested rollback. Use when endpoint assumptions, client versions, schemas, or integration architecture must change. Trigger with "upgrade Attio integration", "Attio migration", or "Attio API contract change".
Why this skill is useful
Adds detailed migration scripts and specific API endpoint changes for transitioning between Attio API versions that are not publicly documented.
What it needs
Requires attio 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 Migration Overview This skill migrates the integration that actually exists. It does not assume a generic historical version jump; it proves every affected endpoint and data shape against current Attio contracts. Prerequisites Current integration commit, dependencies, and deployment topology Endpoint, scope, pagination, data-shape, and webhook inventory Representative redacted fixtures and reconciliation queries Canary cohort, rollback owner, and recovery objective Tool Discipline Use Read, Glob, and Grep to inventory current assumptions and tests. Use WebFetch only for current official Attio documentation and OpenAPI. Use Write or Edit after the contract diff, rollout boundary, and rollback point are documented. Current Contract Validate method, path, scopes, request fields, response fields, value shapes, and pagination per endpoint. Treat official OpenAPI as an input to the diff, not a substitute for behavioral fixtures and endpoint documentation. Record and entry queries may use offset pagination and score-based rate accounting; other endpoints can expose cursors. Webhook changes must preserve raw-body signature verification and at-least-once idempotency. Authentication Preserve tenant-to-token binding and least privilege throughout the migration. Any new scope requires explicit justification, administrator approval, and a reversible credential plan. Instructions 1. Freeze a baseline of call sites, dependencies, contracts, fixtures, metrics, and current production behavior. 2. Diff each affected endpoint against official documentation and OpenAPI. 3. Classify changes as compatible, additive, behavior-sensitive, or breaking. 4. Add compatibility adapters and tests for pagination, value shapes, errors, idempotency, and redaction. 5. Run shadow reads or dry-run comparisons and reconcile mismatches without customer-facing mutations. 6. Canary one bounded workspace or workload with explicit health and rollback thresholds. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/attio-upgrade-migration