Skills Guide

Atlan SQL Connector Patterns

VerifiedSafe

Select and apply the correct SQL connector implementation pattern (SDK-default minimal or source-specific custom) for building or extending SQL metadata/query extraction connectors. Helps developers choose between minimal and custom paths based on a decision tree, ensuring consistent implementation of authentication, preflight, workflow map, and transformation behavior.

Sby Skills Guide Bot
Data & AIIntermediate
606/2/2026
Claude Code
#sql-connector#metadata-extraction#connector-patterns#atlan

Recommended for

Claude CodeData scientistData & analysis

Our review

Select and implement the appropriate SQL connector pattern (minimal SDK or custom source-specific) for metadata extraction.

Strengths

  • Structured guide with decision tree to choose between minimal and custom paths
  • Reuses verified components and shared references
  • Integrates downstream fact verification and contract validation

Limitations

  • Requires external references (decision tree, verification sources)
  • Specific to the Atlan ecosystem and its associated tools
  • Covers only SQL connectors, not other types
When to use it

When building or extending a SQL metadata extraction connector and deciding between a minimal SDK or custom implementation.

When not to use it

If working on non-SQL connectors or if the required decision references are unavailable.

Security analysis

Safe
Quality score85/100

The skill is a high-level decision guide for selecting SQL connector patterns and does not instruct execution of any commands or tools that could compromise security. It references other verification components but contains no dangerous or obfuscated instructions.

No concerns found

Examples

Choose connector strategy for Redshift
I need to build a SQL connector for Redshift. Should I use the minimal SDK path or a custom source-specific pattern? Follow the decision tree and implement accordingly.
Implement minimal Postgres connector
Implement a minimal SQL connector for Postgres using the SDK-default approach. Use the decision tree to confirm and verify with the fact verification gate.
Document custom connector justification
I am implementing a custom SQL connector for Redshift. Help me document why SDK defaults are insufficient and verify the requirements against the shared verification sources.

name: atlan-sql-connector-patterns description: 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.

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
Related skills

Prompt Engineering

Data & AI

Prompt engineering best practices and templates to maximize AI outputs.

claudeCursorWindsurf+1beginner
289
78
740
Admin

Data Visualization

Data & AI

Generates data visualizations and charts tailored to your data.

claudeCursorWindsurfintermediate
198
56
593
Admin

RAG Architecture Setup

Data & AI

Setup guide for RAG (Retrieval-Augmented Generation) architectures.

claudeCursorWindsurfadvanced
167
51
543
Admin