← ClaudeAtlas

pickaxelisted

Build, update, and debug AI tools on the Pickaxe.co platform through its hosted MCP server or HTTP JSON-RPC API. Use this skill whenever the user mentions Pickaxe, pickaxe.co, Pickaxe Studio, a Pickaxe workspace, or any work on Pickaxes, prompts, knowledge bases, documents, actions, deployments, access groups, or credits on the platform, including first-time MCP connection setup. Consult it before any Pickaxe write operation, because the platform has silent-failure traps that make writes look successful when they did nothing.
ThomasUmstattd/pickaxe-skill · ★ 6 · AI & Automation · score 73
Install: claude install-skill ThomasUmstattd/pickaxe-skill
# Working with Pickaxe Pickaxe (pickaxe.co) is a platform for building and selling AI tools. Each tool is a "Pickaxe" with a prompt, a model, an optional form, an optional knowledge base, and optional actions. The platform exposes a hosted MCP server at `https://mcp.pickaxe.co` that also answers plain HTTP JSON-RPC, so everything the Studio UI can configure is scriptable. This skill is a field guide built from months of production work on a large Pickaxe workspace. Every claim was observed on the live platform. Observations are dated because the platform changes fast, so re-verify anything load-bearing before you depend on it. ## Not connected yet? If no Pickaxe MCP server is configured, or calls fail with authorization errors, read `references/getting-connected.md`. The API key lives on a settings page that is genuinely hard to find, and that file walks through it. ## The five rules that prevent the worst failures **1. Every prompt write hits the live bot.** `run_pickaxe_completion` has a `pickaxeConfig` parameter, and it does NOT override the prompt. There is no shadow mode. Iterating on a prompt means writing to whatever bot you target, so iterate on a private staging copy and apply the final version to the live tool once. **2. Never trust a mutation's return value. Read state back.** Mutations can return success while doing nothing, return a different envelope shape than reads, or succeed while a client helper throws. After every write, fetch the state you changed