atlan-cli-run-test-loop
Run Atlan app execution loops using CLI-first commands with automatic CLI availability checks and safe fallbacks.
Best use case
atlan-cli-run-test-loop is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Run Atlan app execution loops using CLI-first commands with automatic CLI availability checks and safe fallbacks.
Teams using atlan-cli-run-test-loop 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-cli-run-test-loop/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How atlan-cli-run-test-loop Compares
| Feature / Agent | atlan-cli-run-test-loop | 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?
Run Atlan app execution loops using CLI-first commands with automatic CLI availability checks and safe fallbacks.
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 CLI Run Test Loop Execute run/test/fix loops that a developer would expect from a normal app request. ## Workflow 1. Resolve target app path. 2. Verify CLI availability first: - Check `command -v atlan`. - If missing, invoke `atlan-cli-install-configure` before run/test. - Do not begin by searching for a local `atlan-cli` repository. - Re-verify with `command -v atlan && atlan --help`. - If network/install is blocked, stop and ask the user to enable installation or provide an existing CLI binary path. 3. Verify infra prerequisites before run/e2e: - `uv`, `temporal`, `dapr` are available. - Dapr runtime initialization is present (config path exists and sidecar can start). - If missing, run `atlan app init tools` first; if issue persists, apply manual Dapr recovery and record it. 4. Use CLI-first commands: - `atlan app run -p <app_path>` - `atlan app test -p <app_path> -t unit` - `atlan app test -p <app_path> -t e2e` 5. Use fallback commands only when CLI path is unavailable or mismatched: - `uv run poe start-deps` - `uv run main.py` - `uv run pytest` 6. Record each cycle in `loop_report.md` using `../_shared/assets/loop_report.md`. 7. If command behavior is unclear or conflicting, verify against CLI docs/code and run `atlan-fact-verification-gate`. 8. If a CLI mismatch appears, append proposal to `../_shared/references/cli-change-proposals.md`. ## Loop Contract - Capture commands, failures, root cause, patch plan, and rerun result. - Prefer deterministic command sequences and explicit paths. - Treat `ATLAN-CLI-APP-0012` / dependency startup failures as infra blockers; collect logs and apply the run-matrix recovery steps. - Do not imply or perform CLI repo edits. ## References - Run matrix: `references/run-matrix.md` - CLI proposal log: `../_shared/references/cli-change-proposals.md` - CLI install/config: `../atlan-cli-install-configure/SKILL.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-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.
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-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.
jepsen-testing
Jepsen-style correctness testing for distributed systems under faults (partitions, crashes, clock skew) using concurrent operation histories and formal checkers (linearizability/serializability and Elle-style anomalies). Use when designing, implementing, or running Jepsen tests, or interpreting histories/violations.
webapp-testing
Toolkit for interacting with and testing local web applications using
testing-websocket-api-security
Tests WebSocket API implementations for security vulnerabilities including missing authentication on WebSocket upgrade, Cross-Site WebSocket Hijacking (CSWSH), injection attacks through WebSocket messages, insufficient input validation, denial-of-service via message flooding, and information leakage through WebSocket frames. The tester intercepts WebSocket handshakes and messages using Burp Suite, crafts malicious payloads, and tests for authorization bypass on WebSocket channels. Activates for requests involving WebSocket security testing, WS penetration testing, CSWSH attack, or real-time API security assessment.
testing-ransomware-recovery-procedures
Test and validate ransomware recovery procedures including backup restore operations, RTO/RPO target verification, recovery sequencing, and clean restore validation to ensure organizational resilience against destructive ransomware attacks.