Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

atlan-sql-connector-patterns

Sterne4

Forks7

Aktualisiert6. Februar 2026 um 11:53

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.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

atlanhq

atlanhq/atlan-sample-apps

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

DatenbankarchitektenInformatik- und Mathematikberufe·SOC 15-1243

Datei-Explorer

3 Dateien

SKILL.md

readonly

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

Use references/decision-tree.md to choose postgres-minimal or 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

Mehr aus diesem Repository

gleiches Repository

atlan-app-scaffold-standard

atlanhq/atlan-sample-apps

Scaffold new Atlan apps from CLI templates as the default behavior when users ask for a new app, then align files to sample-app standards.

2026-02-064

atlan-cli-install-configure

atlanhq/atlan-sample-apps

Install Atlan CLI with OS-aware binaries (or Homebrew on macOS) only when missing, then configure baseline tenant auth/log settings.

2026-02-064

atlan-cli-run-test-loop

atlanhq/atlan-sample-apps

Run Atlan app execution loops using CLI-first commands with automatic CLI availability checks and safe fallbacks.

2026-02-064

atlan-e2e-contract-validator

atlanhq/atlan-sample-apps

Generate and validate e2e test contracts for Atlan workflows, including API responses, output paths, and schema assertions. Use when adding or updating workflow e2e coverage.

2026-02-064

atlan-fact-verification-gate

atlanhq/atlan-sample-apps

Verify Atlan app behavior against SDK docs/code and CLI docs/code before behavior-changing decisions; use lightweight checks by default and deep checks when risk is high.

2026-02-064

atlan-review-doc-sync

atlanhq/atlan-sample-apps

Run findings-first review for Atlan app changes and synchronize app documentation with implemented behavior. Use when completing a change set, preparing handoff, or auditing regressions.

2026-02-064

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

Use references/decision-tree.md to choose postgres-minimal or 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