When should I use the custom path over the minimal path?

The custom path should only be used when the standard SDK defaults are insufficient for specific source requirements, and these justifications must be explicitly documented.

How does this skill interact with Atlan contracts?

It prepares the implementation for handoff to the atlan-e2e-contract-validator, ensuring the connector meets all required data contracts.

What is the purpose of the atlan-fact-verification-gate?

It is used to verify source-specific behavior and ensure that custom implementations do not introduce risks when overriding default SDK behaviors.

Does this skill help with authentication setup?

Yes, it provides specific guidance on verifying authentication and preflight workflows against reference maps to ensure secure connectivity.

Atlan SQL Connector Patterns

Name: Atlan SQL Connector Patterns
Author: atlanhq

byatlanhq

•

Database Management

Guides the development of Atlan SQL metadata and query extraction connectors by selecting and implementing standardized SDK patterns.

This skill provides a structured framework for developers building or extending SQL connectors within the Atlan ecosystem using the Atlan Application SDK. It streamlines the architectural decision-making process by using a specialized decision tree to determine whether a project requires a minimal SDK-default implementation or a source-specific custom path. By enforcing standardized workflows for authentication, preflight checks, and transformation behavior, this skill ensures that connectors are built consistently, maintainable, and fully compatible with Atlan's end-to-end contract validation requirements.

Key Features

01Decision-tree logic for choosing between minimal and custom connector paths

02Handoff support for end-to-end contract generation and validation

03Standardized implementation patterns for Postgres and Redshift-style sources

044 GitHub stars

05Automated verification for authentication and preflight workflow mapping

06Integrated fact-verification gate to mitigate SDK override risks

Use Cases

01Architecting new SQL metadata extractors for custom database sources

02Standardizing connector implementations to align with Atlan SDK best practices

03Extending existing Atlan connectors with source-specific query extraction logic

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add atlanhq/atlan-sample-apps atlan-sql-connector-patterns

For use in Claude.ai and ChatGPT

Download Skill