Agent skill · software engineering · jeremylongshore
attio-deploy-integration
Plan and execute a staged deployment for an external Attio REST integration with secret injection, contract tests, read-only smoke evidence, canary writes, and rollback. Use when releasing Attio-backed services. Trigger with "deploy Attio integration", "Attio rollout", or "Attio release plan".
Why this skill is useful
Adds executable deployment scripts for multiple platforms with specific configurations and health checks that the AI wouldn't generate on its own.
What it needs
Requires fly, gcloud, vercel installed locally. 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 Integration Rollout Overview This skill releases application code that calls Attio's REST API. It uses progressive evidence so a bad schema mapping, scope, or retry policy is caught before broad CRM mutation. Prerequisites A versioned application artifact and tested configuration Environment-specific Attio workspace and secret references A disposable canary record or approved read-only smoke path Defined rollback owner, trigger, and previous artifact Tool Discipline Use Read, Glob, and Grep to inspect deployment manifests, secret names, health checks, migrations, and rollback commands. Use WebFetch only for current official Attio documentation. Use Write or Edit after the rollout target and approval boundary are confirmed. Current Contract Inject tokens from the deployment platform; never bake them into images or manifests. Validate object and list schemas in the target workspace before enabling writes. Keep read and write traffic controls separate because Attio publishes different limit tiers. A successful process health check is not proof that CRM mutations are correct. Authentication Use the target environment's least-privilege single-workspace token or tenant-specific OAuth token. Confirm workspace identity and required endpoint scopes before canary traffic. Instructions 1. Compare artifact, configuration, secret references, workspace alias, and endpoint set with the approved release record. 2. Run offline contract and redaction tests on the exact artifact. 3. Deploy with Attio writes disabled and perform a bounded read-only smoke request. 4. Confirm current object/list attributes and pagination behavior in the target workspace. 5. Enable one idempotent or reversible canary write, then read it back. 6. Expand traffic gradually while watching 4xx, 429, 5xx, latency, duplicate writes, and queue age. 7. Roll back on a declared trigger and verify both application and CRM state. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/attio-deploy-integration