Agent skill
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.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/atlan-sdk-objectstore-io-defaults
SKILL.md
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-gatewhen 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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?