--- name: attio-debug-bundle description: >- 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". argument-hint: "[repository-path] [incident-id]" allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit version: 1.8.0 author: Jeremy Longshore license: MIT tags: - saas - attio - diagnostics model: inherit effort: high compatibility: Designed for Claude Code --- # 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. ## Approval Boundaries Do not run broad workspace enumeration for diagnostics, collect raw CRM responses, or transmit a bundle until its exact contents and destination are reviewed. ## Output Return a bundle manifest, redaction report, request fingerprint, observed-versus-expected contract, reproduction result, checksum, and sharing disposition. ## Error Handling | Condition | Response | |---|---| | Secret pattern is found | Stop, redact, and rescan from the beginning. | | Evidence contains personal data | Replace it with typed placeholders or counts. | | Reproduction would mutate data | Use fixtures or request explicit disposable-target approval. | | Bundle does not answer the incident question | Remove noise and collect only the missing field. | ## Examples Input: ```text incident=attio-query-429; endpoint=/v2/objects/:object/records/query ``` Expected handoff: ```text bundle=redacted; secrets=0; fingerprint=complete; sharing=approved ``` This result makes the escalation artifact useful without exporting customer records. ## Resources - [Skill-specific official documentation](references/official-docs.md) - [REST API overview](https://docs.attio.com/rest-api/overview) - [Rate limiting](https://docs.attio.com/rest-api/guides/rate-limiting) - [Authentication](https://docs.attio.com/rest-api/guides/authentication) --- Source attribution: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/attio-pack/skills/attio-debug-bundle/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice MIT License Copyright (c) 2025 Jeremy Longshore Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Mega AI Hub resource metadata Creator / publisher: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/attio-pack/skills/attio-debug-bundle/SKILL.md Attribution basis: Source repository record Fields of work: Sales, Customer Support Roles: Business Development, Customer Success Manager, Sales Engineer, Sales Development Rep (SDR), Support Agent Specialties: API Tools: Attio Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: fdcc9ad291ad93b57a7732ccdeb372bccdacbaae7766cf6965823a3a5fe1a688