Agent skill · software engineering · jeremylongshore
attio-debug-bundle
Assemble a minimal redacted Attio diagnostic bundle with request fingerprints, schema context, retry evidence, and environment metadata. Use when escalating an Attio integration failure without leaking CRM data or secrets. Trigger with "Attio debug bundle", "Attio support evidence", or "collect Attio diagnostics".
Why this skill is useful
Adds an executable diagnostic script for collecting Attio API health and configuration details that aren't publicly documented.
What it needs
Requires curl, 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
Redacted Attio Diagnostic Bundle Overview This skill collects the smallest evidence needed to reproduce or escalate an Attio API problem. Redaction and content review happen before a bundle is written or shared. Prerequisites A named incident, repository, and failing operation Redaction rules for tokens, webhook secrets, IDs, and personal data The exact endpoint reference and expected request shape An approved destination for the final bundle Tool Discipline Use Read, Glob, and Grep to inspect configuration names, client code, existing logs, and tests without opening secret files unnecessarily. Use WebFetch only for current official Attio documentation. Use Write or Edit only for a reviewed redacted artifact in the approved path. Current Contract Collect path templates, not customer-bearing URLs. Preserve status, content type, documented error fields, retry timing, and pagination mode. Record scope names but never token values. Do not dump entire records, attribute values, environment variables, headers, or webhook payloads. Authentication If a bounded reproduction is approved, use the existing Bearer credential in process memory. The bundle may state credential type, workspace alias, and granted scopes; it must not contain the credential or reusable signature material. Instructions 1. Define the incident question and minimum evidence fields before collection. 2. Inventory the local caller, endpoint path template, method, timeout, retry policy, and pagination mode. 3. Capture one redacted failure fingerprint and one bounded control request if safe. 4. Add object or list schema identifiers only when needed to explain validation behavior. 5. Scan the candidate bundle for token patterns, authorization headers, webhook secrets, record values, emails, phone numbers, and full IDs. 6. Review the redacted output manually, then write the approved bundle and checksum. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/attio-debug-bundle