Skills Guide

Atlan SQL Connector Patterns

VerifiedSafe

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.

Sby Skills Guide Bot
DevelopmentIntermediate
306/2/2026
Claude Code
#sql-connector#connector-patterns#atlan#metadata-extraction

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Our review

Selects and implements the appropriate SQL connector pattern (SDK-minimal or source-specific custom) for metadata and query extraction.

Strengths

  • Structured decision tree for pattern selection
  • Reuses proven connector implementations
  • Built-in verification and contract validation steps

Limitations

  • Requires prior understanding of SDK connector architecture
  • Depends on external reference documents (decision tree, verification map)
When to use it

When building or extending a SQL metadata/query extraction connector.

When not to use it

For non-SQL connectors or when requirements are fully met by the minimal SDK path without customization.

Security analysis

Safe
Quality score85/100

The skill does not instruct the AI to run any commands or access external resources; it only guides through decision-making and referencing other internal skill files. There is no risk of destructive or exfiltrating actions.

No concerns found

Examples

Select connector pattern for PostgreSQL
I need to build a SQL connector for PostgreSQL metadata extraction. Should I use the minimal SDK path or a custom source-specific pattern? Use the Atlan SQL connector patterns skill to decide and implement.
Extend connector with custom Redshift behavior
We have requirements that the SDK defaults are insufficient for Redshift – we need custom preflight and transformation behavior. Apply the Atlan SQL connector patterns skill to document why and implement the custom path.

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

Next.js App Router Expert

Development

A skill that turns Claude into a Next.js App Router expert.

Claude CodeCursoradvanced
890
234
2,846
Admin

README Generator

Development

Creates professional and comprehensive README.md files for your projects.

claudeCursorWindsurfbeginner
259
72
821
Admin

API Documentation Writer

Development

Generates comprehensive API documentation in OpenAPI/Swagger format.

claudeCursorWindsurfintermediate
156
44
682
Admin