/SKILL.md
DEPRECATED — this standalone skill has been split into three skills and repackaged as the `akash-network` Claude Code plugin. Install the plugin and uninstall this standalone skill. See the repo README for migration instructions.
npx skillsauth add akash-network/akash-skill akashInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This standalone skill has been split into three skills and repackaged as a Claude Code plugin:
akash-network:akash — Deploy workloads (SDL, Console API, CLI, SDKs)akash-network:akash-provider — Run an Akash providerakash-network:akash-node — Run a full node or validatorRemove the standalone install. If this skill was installed by symlinking or cloning into ~/.claude/skills/akash/, remove that directory.
Install the plugin. From the repo root (where you found this file):
claude --plugin-dir /path/to/this/repo
Or, if the plugin is published to a Claude Code marketplace your client is configured for:
/plugin install akash-network
The three skills will then be available as akash-network:akash, akash-network:akash-provider, and akash-network:akash-node. The triggers in their descriptions are the same as before, just with the namespace prefix.
The original skill mixed three distinct personas (deployer, provider operator, validator operator) into one description, which made it hard for Claude to pick the right skill for the right task. Splitting them sharpens trigger precision and lets each skill stay focused.
See README.md for the full changelog and rationale.
tools
Build, validate, and deploy workloads to the Akash Network — the decentralized cloud marketplace. Covers SDL syntax & examples, choosing a deployment method (Console API, CLI, TypeScript/Go SDKs), authentication (API key, JWT, self-custody wallets), deployment lifecycle, fetching logs/events via the provider proxy, and fee grants/authz. Also covers AkashML — the managed inference surface for calling open-source LLMs on Akash compute via OpenAI/Anthropic-compatible APIs. Use for "deploy to Akash", "Akash SDL", "Akash Console API", "Akash CLI deploy", "Akash API key", "x-api-key", "Akash deploy logs", "stream Akash logs", "integrate Akash into my app", "@akashnetwork/chain-sdk", "@akashnetwork", "AkashML", "managed inference on Akash", "call an LLM on Akash", "playground.akashml.com", "api.akashml.com".
testing
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".
tools
Run an Akash Network full node or validator. Covers hardware and network requirements, full-node installation, state sync, becoming a validator, validator operations, slashing avoidance, key management (consensus key + operator key), monitoring, and sentry node patterns. Use for "Akash validator", "Akash full node", "Akash state sync", "Akash validator setup", "Akash sentry node", "Akash slashing", "Akash consensus key", "Akash node upgrade".
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.