From akash-network
Set up and operate an Akash Network provider — the supply side of the decentralized cloud. Covers Kubernetes prerequisites, provider installation, attributes and pricing configuration, bid engine tuning, monitoring, and troubleshooting. Use for "run an Akash provider", "set up Akash provider", "Akash provider Kubernetes", "Akash provider attributes", "Akash provider pricing", "Akash provider bid engine", "Akash provider not getting bids", "Akash provider audit", "provider lease monitoring".
How this skill is triggered — by the user, by Claude, or both
Slash command
/akash-network:akash-providerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill covers everything needed to run a provider on the Akash Network: cluster prerequisites, installing the provider services, configuring attributes and pricing, tuning the bid engine, and ongoing operations.
agents/openai.yamlrules/configuration/attributes.mdrules/configuration/bid-engine.mdrules/configuration/pricing.mdrules/operations/lease-management.mdrules/operations/monitoring.mdrules/operations/troubleshooting.mdrules/overview.mdrules/requirements.mdrules/setup/configuration.mdrules/setup/kubernetes-cluster.mdrules/setup/provider-installation.mdThis skill covers everything needed to run a provider on the Akash Network: cluster prerequisites, installing the provider services, configuring attributes and pricing, tuning the bid engine, and ongoing operations.
For deploying workloads to Akash, use the akash-network:akash skill. For running full nodes or validators, use akash-network:akash-node.
The Akash chain uses the same vocabulary across all three roles; these are the terms a provider operator most often encounters.
akash1...). Runs a provider-services daemon backed by a Kubernetes cluster.dseq (deployment sequence) is the per-deployment id; gseq and oseq identify the group and order within it. Bids/leases are scoped to (dseq, gseq, oseq).region=us-west, tier=community). SDLs use placement attribute filters to select providers.signedBy.uakt) — chain token. Used for gas (--gas-prices, minimum-gas-prices), staking, and validator rewards. The provider's wallet uses AKT to pay gas on its bid transactions.uact) — deployment-payment token. Used for SDL pricing, bid prices, lease payments. The provider's bid prices (output of your pricing script) are in uact/block. Lease revenue arrives as ACT.uakt — the bidMinDeposit config value (and the deposit field on MsgCreateBid) is anti-spam collateral posted from the provider's balance, not a compute payment. Default is 500000 uakt (0.5 AKT); uact is accepted only via a rare burn-mint fallback.uakt; bid prices, lease revenue, and pricing-script output use uact. Don't conflate the gas denom and the pricing denom.For a fuller chain-side vocabulary (deployer view), see the akash-network:akash skill's rules/terminology.md.
| Area | File |
|---|---|
| Hardware, network, and OS requirements | @rules/requirements.md |
| Kubernetes cluster setup (single + multi-node) | @rules/setup/kubernetes-cluster.md |
Installing provider-services and CRDs | @rules/setup/provider-installation.md |
Initial provider configuration (provider.yaml) | @rules/setup/configuration.md |
| Attribute schema and how SDLs filter on them | @rules/configuration/attributes.md |
| Pricing script — how bids are priced per resource | @rules/configuration/pricing.md |
| Bid engine tuning (when to bid, min/max prices) | @rules/configuration/bid-engine.md |
| Day-to-day lease management | @rules/operations/lease-management.md |
| Resource reclamation (AEP-82, v0.13.0+) — provider-initiated reclaim of active leases | @rules/operations/lease-management.md (§ Resource Reclamation) + @rules/configuration/bid-engine.md (§ Resource Reclamation Window) |
| Monitoring (metrics, alerting, on-chain status) | @rules/operations/monitoring.md |
| Common failures and how to diagnose | @rules/operations/troubleshooting.md |
Internet
│
├──► Tenant manifest push (mTLS or JWT)
│
▼
provider-services daemon
│
├──► bid engine ──► broadcasts MsgCreateBid
├──► manifest receiver ──► applies workload to Kubernetes
├──► proxy ──► forwards tenant traffic to pods (ingress)
│
▼
Kubernetes cluster
├── tenant pods (workloads)
├── ingress controller
├── persistent volumes (beta2 / beta3 / ram)
└── (optional) GPU operator
The provider does three jobs:
MsgCreateDeployment events).uact in your bid pricing script (the script's output becomes the price field on MsgCreateBid). Use uakt for --gas-prices and minimum-gas-prices (chain gas). The bidMinDeposit / deposit field on MsgCreateBid defaults to uakt (500000 = 0.5 AKT, posted from the provider's balance); uact is accepted only via a rare burn-mint fallback. The pricing-script price denom and the gas denom aren't interchangeable; the chain enforces both.provider-services up to date. Chain upgrades regularly break older provider releases. Subscribe to the Akash Discord / GitHub releases. For node v2.1.0, run provider-services v0.13.0 or later (the paired build; required to offer AEP-82 resource reclamation via --reclamation-window).signedBy claims (e.g. "trusted by AkashNetwork"), you must arrange the on-chain signature from the auditor. Don't claim unverified audits.vendor.nvidia.model: a100, your provider must expose that).# Check provider status (replace with your address)
provider-services query provider get akash1yourprovider...
# List active leases on your provider
provider-services query market lease list --provider akash1yourprovider...
# Tail provider logs (Kubernetes)
kubectl -n akash-services logs -f deployment/akash-provider
# Bid engine logs
kubectl -n akash-services logs -f deployment/akash-provider | grep -i bid
akash-network:akash — Deployer-side knowledge: how tenants write SDLs, what attributes they filter on, and the bid-matching workflow (rules/bid-matching/) that deployers use to check which providers can run their SDL. Helpful to run against your own provider to see whether you're being filtered out.npx claudepluginhub akash-network/akash-skill --plugin akash-networkProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.