atlan-sdk-objectstore-io-defaults
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.
Best use case
atlan-sdk-objectstore-io-defaults is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using atlan-sdk-objectstore-io-defaults 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-sdk-objectstore-io-defaults/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How atlan-sdk-objectstore-io-defaults Compares
| Feature / Agent | atlan-sdk-objectstore-io-defaults | 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?
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.
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 SDK Objectstore IO Defaults Apply SDK-native defaults for all output read/write logic. ## Workflow 1. Apply defaults from `references/defaults.md`. 2. Use SDK path-building conventions instead of hardcoded prefixes. 3. Route writes through SDK IO abstractions where possible. 4. If local SDK checkout is unavailable, verify behavior from installed package source or remote SDK source/docs. 5. Run `atlan-fact-verification-gate` when output behavior changed or conflicts with existing tests. 6. 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`
Related Skills
atlan-workflow-args-secrets-state
Implement workflow argument retrieval, credential_guid usage, and state store updates using Atlan SDK patterns. Use when workflows or activities handle credentials, runtime args, or persisted workflow state.
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.
atlan-review-doc-sync
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.
atlan-fact-verification-gate
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.
atlan-e2e-contract-validator
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.
atlan-cli-run-test-loop
Run Atlan app execution loops using CLI-first commands with automatic CLI availability checks and safe fallbacks.
atlan-cli-install-configure
Install Atlan CLI with OS-aware binaries (or Homebrew on macOS) only when missing, then configure baseline tenant auth/log settings.
atlan-app-scaffold-standard
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.
insecure-defaults
Detects fail-open insecure defaults (hardcoded secrets, weak auth, permissive security) that allow apps to run insecurely in production. Use when auditing security, reviewing config management, or analyzing environment variable handling.
Insecure Defaults Detection
Detect insecure default configurations, hardcoded credentials, fail-open security patterns, and dangerous default values in application code and configuration files. Complements SKL-0015 (Security Audit) by focusing on configuration-level vulnerabilities that dependency scanners miss.
json-config-loader-1-always-provide-defaults
Sub-skill of json-config-loader: 1. Always Provide Defaults (+4).
agent-usage-optimizer-baseline-route-defaults
Sub-skill of agent-usage-optimizer: Baseline Route Mapping (quota-agnostic defaults) (+1).