Agent skill · software engineering · jeremylongshore
attio-hello-world
Prove the smallest safe Attio REST connection by listing objects and validating the response envelope without changing CRM data. Use when checking a new token, workspace, or integration path. Trigger with "Attio hello world", "first Attio request", or "test Attio connection".
Why this skill is useful
Provides specific API call examples and patterns for integrating with the Attio CRM, which the AI wouldn't reliably generate on its own.
What it needs
Requires jq 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 Verified First Read Overview This skill proves authentication, workspace reachability, JSON parsing, and object discovery with one read-only request. It does not create a demonstration contact in a real CRM. Prerequisites A named repository and non-production or approved workspace A single-workspace access token or OAuth access token The objectconfiguration:read scope required by the object-list endpoint A runtime with HTTPS and JSON support Tool Discipline Use Read, Glob, and Grep to inspect the local client, environment-variable names, and tests. Use WebFetch only for current official Attio documentation. Use Write or Edit after confirming the repository and intended implementation file. Current Contract Base URL: https://api.attio.com/v2. Send Authorization: Bearer <accesstoken>; Bearer authentication is the recommended form. Start with GET /v2/objects and validate a { data: [...] } response. Keep the credential out of source, output, exceptions, and request logging. Authentication Use a workspace API key for a single workspace or OAuth for an app serving multiple workspaces. Do not request write scopes for this proof. Instructions 1. Confirm the repository, runtime, workspace alias, secret source, and granted scope. 2. Add or inspect a tiny request wrapper with explicit base URL and Bearer header injection. 3. Request /objects with a bounded timeout and capture status plus content type. 4. On success, parse data and record only object slugs or counts that are safe to expose. 5. Assert that at least one expected object is visible to the workspace. 6. Add a fixture test for success plus 401, 403, and non-JSON failure handling. Approval Boundaries Do not add create, update, assert, or delete calls to the first-read proof. Never print the access token or persist a raw workspace response. Output Return the redacted configuration, status, response-envelope assertion, safe object summary, fixture-test result, and next integration boundary. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/attio-hello-world