Agent skill · data analytics · jeremylongshore
attio-common-errors
Diagnose Attio REST API failures from status, structured error fields, endpoint contract, and request context without exposing customer data. Use when an Attio request returns 400, 401, 403, 404, 409, 422, 429, or 5xx. Trigger with "Attio error", "Attio request failed", or "debug Attio API".
Why this skill is useful
Provides specific error handling patterns and curl commands for diagnosing Attio API errors that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, jq installed locally. Requires attio account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Attio Error Triage Overview This skill classifies an Attio failure before changing code or credentials. It preserves the response's structured fields while keeping tokens and CRM values out of diagnostics. Prerequisites The HTTP method, path template, status, and redacted response body The endpoint's documented required scopes The request's pagination mode and mutation semantics A correlation or application request identifier when available Tool Discipline Use Read, Glob, and Grep to locate the caller, response parser, retry policy, and logs. Use WebFetch only for current official Attio documentation. Use Write or Edit only after the failing contract and safe verification path are known. Current Contract Attio error responses can include statuscode, type, code, and message. Diagnose from observed fields instead of inventing a fixed code list; endpoint references remain authoritative for request shape and scopes. Authentication Confirm that a Bearer token exists at runtime and belongs to the intended workspace. For 401, rotate or replace the invalid credential; for 403, compare granted scopes with the endpoint's required scopes before requesting any change. Instructions 1. Capture method, path template, status, response content type, and redacted structured error fields. 2. Reconcile the request with the exact endpoint reference, including path slug versus UUID and body envelope. 3. Classify authentication, authorization, validation, uniqueness, not-found, throttling, or provider failure. 4. For 429, parse Retry-After as an HTTP date and retry only after the indicated time. 5. For ambiguous 5xx failures, preserve a minimal reproduction and check Attio status before changing business logic. 6. Apply the smallest correction and repeat the same bounded request. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/attio-common-errors