Index of every page on this site: llms.txt
All skills
Run it yourself

Choose and configure Attio REST authentication for a single workspace or multi-workspace OAuth app, including least-privilege scopes and a read-only verification. Use when connecting a service to Attio. Trigger with "Attio auth", "Attio API key", or "Attio OAuth setup".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/attio-install-auth

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈73 tokens for metadata: the name and description. ≈804 when used: this file. ≈528 more on demand in 1 file.

Description uses 3.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈291 characters, or 3.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Attio Authentication Setup

Overview

This skill selects the correct Attio access-token path, maps endpoint scopes, and proves the credential with a non-mutating request.

Prerequisites

  • The integration's workspace and tenancy model
  • Exact endpoints and operations the application will use
  • An approved secret store and rotation owner
  • Registered redirect URIs when OAuth is required

Tool Discipline

Use Read, Glob, and Grep to inspect the local auth wrapper, secret names, redirect configuration, and endpoint use. Use WebFetch only for current official Attio documentation. Use Write or Edit after the auth model and target files are confirmed.

Current Contract

  • Prefer OAuth 2.0 for an app that serves multiple Attio workspaces.
  • Use a manually generated workspace API key for one controlled workspace.
  • Both credential types can be sent as Authorization: Bearer <access_token>.
  • Required scopes are documented per endpoint and should be granted operation by operation.
  • Attio also supports Basic authentication with the token as username and an empty password, but Bearer is recommended.

Authentication

For OAuth, validate state, use the registered redirect URI exactly, exchange the code server-side, and encrypt the resulting token at rest. For a workspace key, create it in developer settings with the minimum scopes and store it only in the approved secret manager.

Instructions

  1. Classify the integration as single-workspace or multi-workspace.
  2. Inventory methods and endpoints, then derive scopes from their current reference pages.
  3. Define secret storage, tenant-to-token mapping, rotation, revocation, and audit ownership.
  4. Implement server-side credential injection without token logging.
  5. For OAuth, bind and verify state; never expose the client secret to browser code.
  6. Verify with one read-only endpoint and record only status, workspace alias, and granted scope names.

Approval Boundaries

Do not generate or broaden production credentials, modify redirect URIs, or migrate tenant tokens without the owning administrator's approval and a rollback plan.

Output

Return the chosen auth model, endpoint-to-scope map, secret reference, OAuth control evidence if applicable, read-only verification, and rotation owner.

Error Handling

Condition Response
Tenancy model is unclear Stop before choosing a credential type.
OAuth state mismatch Reject the callback and start a fresh authorization flow.
403 after verification Compare the exact endpoint scopes; do not grant all scopes.
Token appears in logs Revoke or rotate it and scrub retained output.

Examples

Input:

tenancy=multiple-workspaces; endpoint=GET /v2/tasks; storage=encrypted-server-side

Expected handoff:

auth=oauth; state=verified; scopes=endpoint-derived; read-test=pass

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides guidance for setting up Attio authentication using security best practices. It includes a surface for indirect prompt injection by reading local project files and references official documentation. No malicious behavior was detected.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 2 months ago
What it can do
Reads files Network Edits files
Modelinherit
argument-hint
[repository-path] [single-workspace|oauth]
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "attio",
  "authentication"
]
model
inherit
effort
high
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/attio-install-auth