Attio CRM Object Enrichment, Deal Stage & Speed-to-Lead Skill

Sync inbound leads, product signups, and meeting notes into Attio CRM: deduplicate company domains and person records, update deal pipeline stages, and tri

---
name: attio-crm-sync
description: Sync inbound leads, product signups, and meeting notes into Attio CRM: deduplicate company domains and person records, update deal pipeline stages, and trigger founder follow-ups. Use when working with Attio CRM, Deal Pipelines, Lead Enrichment, RevOps.
triggers:
  - attio crm sync
  - attio crm
  - deal pipelines
---

# Attio CRM Object Enrichment, Deal Stage & Speed-to-Lead Skill

## 1. When to Use This Skill
Load `skill-attio-crm-sync` whenever an engineering or operations task involves **Attio CRM, Deal Pipelines, Lead Enrichment, RevOps**. Specifically:
- Sync inbound leads, product signups, and meeting notes into Attio CRM: deduplicate company domains and person records, update deal pipeline stages, and trigger founder follow-ups.
- Designing, reviewing, or debugging production configurations without guesswork or deprecated flags.
- Running deterministic pre-flight and post-execution verification checks before reporting completion.

## 2. Prerequisites & Required Environment
- **Target Stack:** Attio CRM, Deal Pipelines, Lead Enrichment, RevOps
- **Permissions:** Read-only inspection by default; ask for explicit confirmation before executing destructive mutations or production deployments.
- **Reference Repository:** `https://docs.attio.com`

## 3. Step-by-Step Execution Playbook
1. **Context & Configuration Discovery:**
   Inspect existing project manifests (`package.json`, `wrangler.jsonc`, schema files, or environment declarations) before proposing changes. Never overwrite existing bindings or credentials blindly.
2. **Deterministic Implementation:**
   Apply the canonical patterns for **Attio CRM**:
   - Enforce strict schema/type validation at every external boundary.
   - Include explicit error handling, structured logging, and idempotency keys on all mutating calls.
   - Keep secrets in environment variables or secret stores—never hardcode tokens in source files.
3. **Verification & Regression Gate:**
   Run the verification commands below and inspect both exit codes and output payloads before marking the task complete.

## 4. Reference Commands & CLI Workflow
```bash
curl -s https://api.attio.com/v2/objects -H 'Authorization: Bearer $ATTIO_API_KEY'
```

## 5. Edge Cases & Anti-Hallucination Guardrails
- **Zero Unverified Claims:** Never claim a deployment, migration, or API call succeeded without inspecting the command output or HTTP status code.
- **Rollback Readiness:** Always record the previous state or migration version so changes can be reverted cleanly if downstream health checks fail.

Synthesized Engineering Blueprint & Setup Guide