← ClaudeAtlas

qumge-publishlisted

Use when a developer wants to turn an existing project, API, MCP tool, CLI or internal workflow into a paid Qumge capability, prepare or resume its publishing process, update its contract, or manage their published Caps and earnings. For buying or using capabilities, use the qumge skill instead.
Qumge/qumge-skill · ★ 0 · AI & Automation · score 75
Install: claude install-skill Qumge/qumge-skill
# Publish an existing workflow on Qumge Work in the developer's project using its existing coding, test and deployment tools. The hosted Qumge MCP at https://qumge.com/mcp handles registration, checks, publication and settlement; it does not read local code or deploy it. This skill adds a reusable publishing workflow, not a new runtime, wallet, hosted CLI service or permission to publish. ## Language Use the user's requested language for explanations, questions and human-readable reports. If no language is specified, follow the language of their latest request, including Simplified Chinese or English. Keep tool names, commands, identifiers, JSON keys and protocol values unchanged. Preserve machine-readable report schemas; explain their findings in the user's language. These English instructions are the single maintained execution specification. ## Start with the outcome Read the project before asking the owner to fill in details you can determine locally. Identify one clear input, a complete usable result, its completion criteria and limits. Reuse an existing API/MCP operation if it supplies that whole outcome. Compose partial steps privately on the provider server; do not sell the internal status or helper steps. If no interface exists, add thin authenticated HTTPS invoke/status hooks around native functions and jobs. A local CLI still needs a chosen server/container to run on; do not promise an always-on service from a laptop or invent a deployment URL. Use current m