Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

atlan-sdk-objectstore-io-defaults

Sterne4

Forks7

Aktualisiert6. Februar 2026 um 11:53

Enforce object store and IO defaults from the Atlan SDK for output paths, prefixes, and file writes. Use when implementing or reviewing raw/transformed output handling.

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

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

Datei-Explorer

3 Dateien

SKILL.md

readonly

name	atlan-sdk-objectstore-io-defaults
description	Enforce object store and IO defaults from the Atlan SDK for output paths, prefixes, and file writes. Use when implementing or reviewing raw/transformed output handling.

Atlan SDK Objectstore IO Defaults

Apply SDK-native defaults for all output read/write logic.

Workflow

Apply defaults from references/defaults.md.
Use SDK path-building conventions instead of hardcoded prefixes.
Route writes through SDK IO abstractions where possible.
If local SDK checkout is unavailable, verify behavior from installed package source or remote SDK source/docs.
Run atlan-fact-verification-gate when output behavior changed or conflicts with existing tests.
Validate expected output sections in e2e_case_contract.yaml.

Non-Negotiable Rules

Do not hardcode bucket prefixes when SDK-derived paths exist.
Keep raw and transformed outputs under workflow-specific output path.
Align output naming with e2e assertions.

References

Defaults and anti-patterns: references/defaults.md
Shared templates: ../_shared/references/artifact-templates.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-sdk-objectstore-io-defaults
description	Enforce object store and IO defaults from the Atlan SDK for output paths, prefixes, and file writes. Use when implementing or reviewing raw/transformed output handling.

Atlan SDK Objectstore IO Defaults

Apply SDK-native defaults for all output read/write logic.

Workflow

Apply defaults from references/defaults.md.
Use SDK path-building conventions instead of hardcoded prefixes.
Route writes through SDK IO abstractions where possible.
If local SDK checkout is unavailable, verify behavior from installed package source or remote SDK source/docs.
Run atlan-fact-verification-gate when output behavior changed or conflicts with existing tests.
Validate expected output sections in e2e_case_contract.yaml.

Non-Negotiable Rules

Do not hardcode bucket prefixes when SDK-derived paths exist.
Keep raw and transformed outputs under workflow-specific output path.
Align output naming with e2e assertions.

References

Defaults and anti-patterns: references/defaults.md
Shared templates: ../_shared/references/artifact-templates.md