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.
Best use case
atlan-sql-connector-patterns is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using atlan-sql-connector-patterns should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/atlan-sql-connector-patterns/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How atlan-sql-connector-patterns Compares
| Feature / Agent | atlan-sql-connector-patterns | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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
asyncredux-connector-pattern
Implement the Connector pattern for separating smart and dumb widgets. Covers creating StoreConnector widgets, implementing VmFactory and Vm classes, building view-models, and optimizing rebuilds with view-model equality.
asyncio-concurrency-patterns
Complete guide for asyncio concurrency patterns including event loops, coroutines, tasks, futures, async context managers, and performance optimization
async-python-patterns
Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-blocking operations.
async-patterns-guide
Guides users on modern async patterns including native async fn in traits, async closures, and avoiding async-trait when possible. Activates when users work with async code.
async-await-patterns
Use when writing JavaScript or TypeScript code with asynchronous operations
astro-patterns
Astro best practices, routing patterns, component architecture, and static site generation techniques. Use when building Astro websites, setting up routing, designing component architecture, configuring static site generation, optimizing build performance, implementing content strategies, or when user mentions Astro patterns, routing, component design, SSG, static sites, or Astro best practices.
argparse-patterns
Standard library Python argparse examples with subparsers, choices, actions, and nested command patterns. Use when building Python CLIs without external dependencies, implementing argument parsing, creating subcommands, or when user mentions argparse, standard library CLI, subparsers, argument validation, or nested commands.
architecture-patterns
Software architecture patterns and best practices
architectural-patterns-large-react
Establish scalable architecture using modular boundaries, domain-driven design, and consistent data access patterns.
arch_patterns
Architecture patterns - monolith vs microservices, layered, event-driven, CQRS.
applying-frontend-patterns
Framework-agnostic frontend component design patterns.
application-patterns
Common application development patterns and implementations