Awesome-omni-skill 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.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skill

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/development/atlan-sql-connector-patterns-atlanhq" ~/.claude/skills/diegosouzapw-awesome-omni-skill-atlan-sql-connector-patterns && rm -rf "$T"

manifest: skills/development/atlan-sql-connector-patterns-atlanhq/SKILL.md

source content

Atlan SQL Connector Patterns

Choose the right connector strategy and implement it consistently.

Workflow

Use

references/decision-tree.md

to choose

postgres-minimal

redshift-custom

Implement required components for selected path.
Verify auth, preflight, workflow map, and transformation behavior against references.
Run
```
atlan-fact-verification-gate
```
if requirements imply source-specific behavior or SDK override risk.
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