English

简体中文

English

简体中文

Appearance

ZenMux Skills ​

ZenMux Skills is an official collection of Skills released by ZenMux. They follow the open Skills standard, so they can be recognized and invoked by 45+ popular AI Agents. Whether you use Claude Code, Cursor, Cline, Codex, Gemini CLI, GitHub Copilot, Amp, OpenCode, Warp, Antigravity, Kimi Code CLI, Deep Agents, Firebender, or any other supported Agent, a single install lets you immediately:

  • 🔍 Ask the docs: Ask anything about ZenMux in natural language — the Agent answers based on the latest official documentation and cites its sources.
  • 🛠 Configure tools: Get step-by-step guidance for connecting Cursor, Cline, Claude Code, Cherry Studio, and more to ZenMux.
  • 📊 Check usage: Look up quota remaining, subscription details, wallet balance, and per-request cost at any time.
  • 💬 Submit feedback: File bugs and feature requests through conversation — GitHub Issues are created automatically.
  • 📟 Watch status: Keep subscription tier, quota usage, and wallet balance always visible in the Claude Code status line.

💡 What is a Skill?

A Skill is an extension mechanism defined by the Agent Skills open standard. Each Skill is simply a SKILL.md file with YAML metadata. Once installed:

  • You can invoke it explicitly with /skill-name.
  • The Agent can also trigger it automatically when it detects a matching intent (controlled by each Skill's own description field).

Because the standard is open, the same Skill can be loaded by many different Agents (Claude Code, Cursor, Cline, Codex, Copilot, and more).

Prerequisites ​

One-click install ​

Install the full Skills collection in one shot:

bash
npx skills add ZenMux/skills

This launches an interactive selection UI: first pick which Skills to install, then pick which Agents should receive them.

Interactive selection UI for npx skills add ZenMux/skills

Based on your selections, the tool copies each Skill into the appropriate Agent directory (for example, Claude Code → ~/.claude/skills/; Cursor, Cline, Codex, and others that share the universal directory → ~/.agents/skills/; Augment → ~/.augment/skills/; and so on). The next time you open one of those Agents, it will recognize and be able to invoke the Skills.

You can also install Skills one at a time:

bash
# Documentation assistant
npx skills add https://github.com/zenmux/skills --skill zenmux-context

# Integration helper
npx skills add https://github.com/zenmux/skills --skill zenmux-setup

# Usage query helper
npx skills add https://github.com/zenmux/skills --skill zenmux-usage

# Feedback submission helper
npx skills add https://github.com/zenmux/skills --skill zenmux-feedback

# Account status line (Claude Code only)
npx skills add https://github.com/zenmux/skills --skill zenmux-statusline

📍 About where Skills are installed

Every Agent has its own directory convention, and npx skills add writes to each one automatically. Most Agents support hot reload — newly added or modified Skills take effect in the next session without a restart (exact behavior depends on the Agent you use).

Supported Agents ​

npx skills add supports 45+ Agents, split into two groups.

Universal (.agents/skills, shared directory, always included) ​

These Agents all read the same .agents/skills directory, so one install covers all of them:

AgentAgentAgent
AmpAntigravityCline
CodexCursorDeep Agents
FirebenderGemini CLIGitHub Copilot
Kimi Code CLIOpenCodeWarp

Additional (separate directories, opt-in) ​

These Agents each use their own Skills directory — select them in the interactive UI to install:

  • Augment (.augment/skills)
  • IBM Bob (.bob/skills)
  • Claude Code (.claude/skills)
  • OpenClaw (skills)
  • CodeBuddy (.codebuddy/skills)
  • Command Code (.commandcode/skills)
  • Continue (.continue/skills)
  • Cortex Code (.cortex/skills)
  • …and 23+ more

💡 The CLI is the source of truth

The list of supported Agents keeps growing. For the most up-to-date roster, run npx skills add ZenMux/skills and check the interactive selection UI.

Skills overview ​

SkillIn one sentenceExample trigger
zenmux-contextAnswers questions based on the latest ZenMux docs"How does ZenMux handle model routing?"
zenmux-setupWalks you through connecting a tool to ZenMux"Help me connect Cursor to ZenMux"
zenmux-usageQueries usage, balance, subscription, and cost"How much Flow do I have left?"
zenmux-feedbackFiles GitHub Issues through conversation"I want to report a bug to ZenMux"
zenmux-statuslineShows account info in the Claude Code status line (Claude Code only)"Set up the ZenMux status line for me"

zenmux-context — documentation assistant ​

What it does: Answers your questions based on the latest ZenMux official documentation and cites its sources. Supports both English and Chinese.

When it triggers: Any time you ask about ZenMux — product features, APIs, configuration, model routing, provider routing, subscription plans, pay-as-you-go, multimodal, tool calling, observability, best practices, and more — the Agent invokes it automatically.

Example conversation:

text
You: What's the difference between model routing and provider routing on ZenMux?
Agent: [pulls the latest docs and answers with source links]

You: /zenmux-context Explain prompt caching
Agent: [answers based on the prompt-cache doc]

What problem it solves: You no longer need to leave your Agent to browse docs, and you don't have to worry about stale training data.

zenmux-setup — integration helper ​

What it does: Interactively guides you through filling in the right Base URL, API Key, and model slug so you can connect any tool or SDK to ZenMux.

When it triggers: You say things like "how do I configure it", "what should I put in Base URL", "how to connect to ZenMux", "set up the API key", or mention a specific tool (Cursor, Cline, Claude Code, Cherry Studio, Obsidian, Sider, Codex, Gemini CLI, opencode, and so on).

Example conversation:

text
You: I want Cursor to route through ZenMux. Walk me through it.
Agent: [invokes zenmux-setup]
       Sure. First — are you on the Subscription plan or Pay As You Go?
       … (continues field by field and ends with a verification step)

What problem it solves: Avoids the usual integration pitfalls — wrong Base URL, wrong API Key type, misspelled model slugs.

zenmux-usage — usage query helper ​

What it does: Calls the ZenMux Management API in real time to fetch:

  • Subscription details (tier, price, billing cycle)
  • Quota usage for the 5-hour / 7-day / monthly windows
  • Account health status
  • Flow rate
  • Pay As You Go wallet balance (top-up credits + bonus credits)
  • Cost, token breakdown, and latency for a specific generation
  • Platform statistics (timeseries trends, model leaderboards, provider market share)

When it triggers: You ask things like "how much quota do I have left", "what's my balance", "how much did my last request cost", "check usage", "subscription details", or "Flow rate".

Prerequisite: The ZENMUX_MANAGEMENT_KEY environment variable. Create one in the Management console.

Example conversation:

text
You: How much Flow have I used this week, and how much is left?
Agent: [invokes zenmux-usage]
       7-day quota: 6182 Flows used 416.11 (6.7%), 5765.89 remaining.

You: /zenmux-usage How much did the last generation cost?
Agent: [returns the generation id, token breakdown, and cost breakdown]

What problem it solves: No more quota anxiety, no more opaque balances, no more invisible per-request costs.

zenmux-feedback — feedback submission helper ​

What it does: Collects bugs, feature requests, and product suggestions through natural conversation, then calls the gh CLI to automatically create a GitHub Issue in the ZenMux repo.

When it triggers: You say things like "I want to report a bug to ZenMux", "submit some feedback", or "suggest a new feature".

Prerequisite: The GitHub CLI (gh) is installed and logged in.

Example conversation:

text
You: I want to report a bug — some models occasionally return 500 over the Anthropic protocol.
Agent: [invokes zenmux-feedback and collects details]
       Got it. Let me organize this:
       1. Which model specifically?
       2. How often does the error happen?
       3. Do you have a generation id I can reference?
       … (creates the Issue automatically and returns the link)

What problem it solves: No more tedious feedback loops or incomplete bug reports — you don't even have to fill out the Issue template yourself.

zenmux-statusline — account status line ​

⚠️ Claude Code only

This Skill depends on Claude Code's statusLine mechanism and currently only works inside Claude Code. If you use a different Agent, skip this section and use zenmux-usage for interactive account queries instead.

What it does: Installs a two-line status bar at the bottom of Claude Code that shows session metrics alongside ZenMux account info.

text
[claude-opus-4-7[1m]] 📁 skills | 🌿 main* | ████░░░░░░ 42% ctx | 💾 r72.0k w5.0k
⚡ ZenMux Ultra | 🔑 Sub sk-ss-...6e6 | 5h █░░░░ 19% · 7d █░░░░ 24% | 💳 Bal $492.74

💡 Activate once after installing

npx skills add only copies the Skill to your local machine. The first time you use it, explicitly invoke it once inside Claude Code:

text
/zenmux-statusline

Claude Code will write the status line script into its config, install any missing dependencies (curl, jq), and remind you to set ZENMUX_MANAGEMENT_KEY. After that, the status bar stays in place — no need to invoke it again.

Line 1 · Session info (injected by Claude Code) ​

SegmentExampleDescription
Model[claude-opus-4-7[1m]]Current model slug
Directory📁 skillsCurrent working directory
Git🌿 main*Branch name; * indicates uncommitted changes
Context████░░░░░░ 42% ctxContext window usage: green <70%, yellow 70–89%, red ≥90%
Cache💾 r72.0k w5.0kPrompt cache from the last API call: r = cache hits, w = cache writes. Hidden before the first API call

Line 2 · ZenMux account ​

SegmentExampleDescription
Plan⚡ ZenMux UltraSubscription tier; a ⚠ suffix appears when the account is unhealthy
API Key🔑 Sub sk-ss-...6e6Key type (Sub = subscription, PAYG = pay-as-you-go) + masked key. Hidden when ZENMUX_API_KEY is not set
5-hour quota5h █░░░░ 19%5-hour rolling quota; at 100%, shows ⏳ Xh Ym countdown to reset
7-day quota7d █░░░░ 24%7-day rolling quota, same color and reset logic
PAYG balance💳 Bal $492.74Available wallet balance (top-up + bonus); hidden when there is no PAYG balance

Fallback behavior ​

SituationBehavior
ZENMUX_MANAGEMENT_KEY not setLine 2 shows: ⚙ Set ZENMUX_MANAGEMENT_KEY to display account data
ZENMUX_API_KEY not setAPI Key segment is hidden; everything else still shows
API call failsUses the last cached value; if none, Line 2 is temporarily hidden

Refresh frequency ​

DataRefresh intervalSource
Session info (model, context, cache)Real-timeInjected into statusLine by Claude Code after every assistant response
Git branch5 secondsPer-session cache
ZenMux account (plan, quota, PAYG)120 secondsGlobal shared cache (across sessions)

Environment dependencies ​

  • curl and jq installed locally (macOS: brew install jq)
  • The ZENMUX_MANAGEMENT_KEY environment variable set (Management console)

Environment variables at a glance ​

These Skills rely on the following environment variables:

VariablePurposeWhere to create it
ZENMUX_API_KEYGeneral-purpose API key; zenmux-statusline uses it to detect the key typeSubscription console or PAYG console
ZENMUX_MANAGEMENT_KEYManagement API key; used by zenmux-usage and zenmux-statusline to fetch account dataManagement console

Add them to your shell startup file (~/.zshrc or ~/.bashrc):

bash
export ZENMUX_API_KEY="<your ZenMux API Key>"
export ZENMUX_MANAGEMENT_KEY="<your Management API Key>"

Apply the change:

bash
source ~/.zshrc   # or: source ~/.bashrc

How to invoke a Skill ​

Every Skill supports two invocation styles (the exact UX depends on the Agent you use):

  1. Automatic: When you describe an intent in natural language, the Agent decides whether to invoke the Skill based on its description.
  2. Explicit: Most Agents let you type / to open the menu, or type /skill-name [arguments] directly.

Both styles work for the same request:

text
# Automatic
How much Flow quota do I have left?

# Explicit
/zenmux-usage 5-hour quota

💡 What if it doesn't trigger?

If the Agent doesn't pick the Skill automatically, just invoke it explicitly with /skill-name, or rephrase your request with clearer keywords ("quota", "balance", "status line", etc.). Different Agents have different matching strategies, and explicit invocation is usually the most reliable path.

FAQ ​

1. Install fails / npx command not found ​

Make sure Node.js is installed:

bash
node -v

If you don't see a version number, install it from nodejs.org. npx ships with Node.js — no separate install needed.

2. A Skill isn't triggering automatically ​

  • Your phrasing may not match the keywords in the Skill's description — invoke it explicitly with /skill-name.
  • You may not have selected this Agent during install — re-run npx skills add ZenMux/skills and tick your current Agent in the selection UI.
  • The Skill may not be installed at all — run npx skills add ZenMux/skills to install everything.

3. zenmux-usage / zenmux-statusline can't fetch account data ​

First verify the Management Key is set in your current shell:

bash
echo $ZENMUX_MANAGEMENT_KEY

If it prints nothing, create one in the Management console, add it to your shell startup file, and source it again.

4. zenmux-feedback fails to create an Issue ​

bash
gh --version     # verify it's installed
gh auth status   # verify you're logged in

If you're not logged in, run gh auth login and follow the prompts.

5. zenmux-statusline is installed but the status bar hasn't changed ​

First, confirm you're using Claude Code (this Skill targets Claude Code's statusLine mechanism specifically). Beyond that, remember that npx skills add only downloads the Skill — you still need to invoke /zenmux-statusline once inside Claude Code so it can write the script into Claude Code's config and register the status line.

Contact us

If you have questions or suggestions while using ZenMux Skills, you can: