setup

To fix environment configuration errors for the Upbit Strategy Toolkit, you need to diagnose your installation mode and verify dependency availability. The setup skill validates your environment readiness, checks for the uv package manager, and identifies execution path issues across clone and agent-based deployments.

Your Upbit backtest fails because required CLI dependencies like the uv package manager are missing. Diagnosing your environment readiness detects unavailable packages, verifies execution paths across deployment modes, and ensures the toolkit is correctly configured for strategy design and backtesting.

Yes, you need the uv package manager to run the Upbit Strategy Toolkit CLI. Environment diagnostic checks validate the availability of uv to ensure the toolkit is correctly configured and ready for strategy development and backtesting across all deployment modes.

To diagnose the installation mode for Upbit toolkit deployment scenarios, run environment checks that automatically identify whether you are running in clone mode, global agent mode, or project-scoped mode. This detects execution path issues and verifies your configuration readiness.

The best way to troubleshoot Upbit CLI execution path issues is to run a full environment diagnostic. This validates your installation mode, confirms the presence of required dependencies like uv, and facilitates resolving path misconfigurations across clone and agent-based deployment scenarios.