akash-network/akash-skill
Overview
This skill is a comprehensive Akash Network guide and toolkit for deployers, providers, and node operators. It consolidates SDL generation, CLI and Console API deployments, TypeScript and Go SDK usage, provider setup, and validator operations. Use it to create reproducible SDLs, automate deployments, configure providers, and run nodes securely.
How this skill works
The skill inspects SDL structure and validation rules to generate correct Stack Definition Language files and templates. It guides deployment flows via the Akash CLI, Console API, or SDKs, and provides step-by-step provider and node-operation procedures. It enforces critical rules such as always specifying explicit image tags and validates resource, placement, and endpoint sections. It also maps common patterns (env, storage, GPU, payment) to working SDL examples.
When to use it
- Creating reproducible SDL files for cloud-native workloads
- Deploying applications to Akash using CLI, Console API, or SDKs
- Setting up or configuring an Akash provider and bidding engine
- Running and maintaining full nodes or validators
- Integrating Akash functionality into TypeScript or Go applications
Best practices
- Always specify explicit image tags (never use :latest or omit the tag)
- Use SDL version 2.1 only when IP endpoints are required; otherwise use 2.0
- Define clear profiles and placement pricing for predictable bids
- Keep secrets out of SDL; inject credentials via secure env or secret stores
- Test deployments locally with minimal SDL templates before scaling
Example use cases
- Generate an SDL for a web app with nginx and expose port 80 using versioned images
- Deploy a multi-service stack (web + database) with persistent storage and placement pricing
- Configure a GPU ML workload with NVIDIA attributes and specified GPU model
- Automate deployments from a CI pipeline using the TypeScript SDK or CLI scripts
- Provision a provider node with pricing attributes and monitor bid/lease lifecycle
FAQ
Use SDL version 2.1 when you need IP endpoints; otherwise use 2.0 for standard service deployments.
Can I omit image tags in SDL?
No. Always specify explicit image tags to ensure reproducible deployments and avoid unexpected upgrades.