# Atlan SQL Connector Patterns > Select and apply the correct SQL connector implementation pattern (SDK-default minimal or source-specific custom). Use when building or extending SQL metadata/query extraction connectors. Use when this capability is needed. - Skill: `tomevault-io/atlan-sql-connector-patterns` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/atlan-sql-connector-patterns` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/atlan-sql-connector-patterns/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Data & Analytics - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/atlan-sql-connector-patterns --- # Atlan SQL Connector Patterns Choose the right connector strategy and implement it consistently. ## Workflow 1. Use `references/decision-tree.md` to choose `postgres-minimal` or `redshift-custom`. 2. Implement required components for selected path. 3. Verify auth, preflight, workflow map, and transformation behavior against references. 4. Run `atlan-fact-verification-gate` if requirements imply source-specific behavior or SDK override risk. 5. Hand off to `atlan-e2e-contract-validator` for contract generation. ## Rules - Default to minimal path unless requirements justify custom path. - For custom path, explicitly document why SDK defaults are insufficient. - Reuse source-specific patterns only when corresponding requirements are present. ## References - Decision tree: `references/decision-tree.md` - Shared verification map: `../_shared/references/verification-sources.md` --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/atlanhq) — claim your Tome and manage your conversions.