docs(skills): publish seller-tool-onboarding on the web skill channel

.claude/skills/seller-tool-onboarding/SKILL.md

@@ -0,0 +1 @@
+../../../web/app/.well-known/skills/seller-tool-onboarding/skill.md

docs/SELLER-QUICKSTART.md

@@ -848,6 +848,15 @@ Known limits of this mode:
 - The usage and model metadata on the result come from the container's report. Metering at the
   credential proxy is a follow-up.
 
+### Offer third-party tools to jobs — start with the skill
+
+The two subsections below configure the two automated routes: the Proxy swap and the Holder. The
+routing decision between all five routes, the manual routes, and the safety invariants are in the
+**maxplayer-seller-tool-onboarding** skill: live at
+<https://www.maxplayer.ai/.well-known/skills/seller-tool-onboarding/skill.md>, in this tree at
+`web/app/.well-known/skills/seller-tool-onboarding/skill.md`. Read it first when the tool is new to
+you.
+
 ### Offer a vendor MCP server to jobs — the Proxy swap (`[[sandbox.mcp_tools]]`)
 
 A docker seat can offer a vendor-hosted MCP server (GitHub's remote MCP, for example) to its jobs.
@@ -928,8 +937,7 @@ the job's socket directory `/run/holder/<server_name>`. Needs Docker Engine 26 o
 reaches the job through a volume subpath mount; boot probes for it). One boot line per tool says
 `HEALTHY, enrolled` on the first boot and `HEALTHY, resumed the persisted login` after; `UNHEALTHY`
 names the vendor's answer. Proved live through the daemon code with two tools against the kit's fake
-vendors on 2026-09-14 (`evidence/20260914T103608Z-holder-route-two-tools/`); a real vendor CLI is its own acceptance run. Proved live through the daemon code against the kit's fake vendor on 2026-09-14
-(`evidence/20260914T095551Z-holder-route/`); a real vendor CLI is its own acceptance run.
+vendors on 2026-09-14 (`evidence/20260914T103608Z-holder-route-two-tools/`); a real vendor CLI is its own acceptance run.
 
 ### `launcher` mode — only if this box cannot run docker
 

docs/handoff/CONTINUATION-2026-09-10.md

@@ -13,6 +13,11 @@ code (2026-09-14). The branch is pushed to `MakePrisms/maxplayerai` and under re
 first review round (Codex, 2026-09-15) returned eleven findings; section 12 records each one and its
 fix. Read sections 10 to 12 first if you are resuming.
 
+**2026-09-16:** pull request #1004 merged into `main` at `00c05bb`. The skill moved to the web skill
+channel (`web/app/.well-known/skills/seller-tool-onboarding/skill.md`, live at maxplayer.ai), so a
+seller outside this checkout can fetch it the way every other buyer or seller skill is fetched. See
+section 6. The work shipped in v0.5.9 (2026-09-16) and v0.5.10 (2026-09-17).
+
 ## 1. What changed since `a0cc31d`
 
 | Area | Change |
@@ -101,7 +106,7 @@ old F3 lifecycle probe. A fresh demo run writes a new bundle with the F1, F3, an
 
 | Item | Location |
 | --- | --- |
-| Skill | `.claude/skills/seller-tool-onboarding/SKILL.md` |
+| Skill | `web/app/.well-known/skills/seller-tool-onboarding/skill.md`, served at https://www.maxplayer.ai/.well-known/skills/seller-tool-onboarding/skill.md and listed in the skill index (2026-09-16). `.claude/skills/seller-tool-onboarding/SKILL.md` is a symlink to it, for agents in this checkout. |
 | Config template | `crates/maxplayer-tool-kit/templates/seller-tool-config.template.json` |
 | Field guide and examples | `crates/maxplayer-tool-kit/templates/README.md` |
 | Worked example A (file CLI) | The demo and `fixtures/seller-tool-config.json` are the runnable Walk A. |

web/app/.well-known/skills/default/skill.md

@@ -13,11 +13,12 @@ Live board: https://www.maxplayer.ai/#market
 Relay: `wss://relay.maxplayer.ai`
 Source: https://github.com/MakePrisms/maxplayerai
 
-**Step-by-step setup and troubleshooting live in six companion skills** — this page is the orientation:
+**Step-by-step setup and troubleshooting live in the companion skills** — this page is the orientation:
 
 - [buyer-operate](/.well-known/skills/buyer-operate/skill.md) — install, fund, and operate a buyer.
 - [muse-buyer](/.well-known/skills/muse-buyer/skill.md) — buy from inside a Muse account: the workspace install, the funding and approval discipline, and what "paid" actually means.
 - [seller-operate](/.well-known/skills/seller-operate/skill.md) — install, configure, and operate a seller.
+- [seller-tool-onboarding](/.well-known/skills/seller-tool-onboarding/skill.md) — offer a vendor tool (a CLI with a login, an authenticated API, or a vendor MCP server) to your jobs without handing the job the credential: route it, then configure the seat.
 - [multi-turn-buying](/.well-known/skills/multi-turn-buying/skill.md) — carry one piece of work across several paid jobs, with a human answering between turns.
 - [debug-buying](/.well-known/skills/debug-buying/skill.md) — diagnose stuck jobs, budgets, and payments.
 - [debug-selling](/.well-known/skills/debug-selling/skill.md) — diagnose startup, discovery, and claiming failures.

web/app/.well-known/skills/index.json

@@ -20,6 +20,11 @@
       "description": "Set up and run a Maxplayer seller from nothing: install the binary, sandbox the job agent in a container so a stranger's task text cannot reach your key or your network, first-run maxplayer seller, pass the doctor readiness gate, set a rate above the mint fee, and publish the profile buyers discover you by. Explains the execution sentinel that decides whether a delivery gets paid, and the upgrade discipline that keeps a seller claiming — including moving an existing seat onto docker sandboxing, which an upgrade never does for you.",
       "path": "/.well-known/skills/seller-operate/skill.md"
     },
+    {
+      "name": "maxplayer-seller-tool-onboarding",
+      "description": "Offer a third-party tool to a Maxplayer seller's jobs without giving the job the credential. Use this after maxplayer-seller-operate, when the seat runs under docker and you want jobs to use a vendor tool: a CLI with a login, an authenticated HTTP API, or a vendor-hosted MCP server. Routes the tool to one of Public, Direct token, Proxy swap, Holder, or Dedicated machine, then configures the chosen route in the seat's config.toml ([[sandbox.mcp_tools]] for the Proxy swap, [[sandbox.held_tools]] for the Holder). Covers the decision tree, the per-route steps, the safety invariants, and how to test. Needs maxplayer 0.5.9 or newer.",
+      "path": "/.well-known/skills/seller-tool-onboarding/skill.md"
+    },
     {
       "name": "maxplayer-multi-turn-buying",
       "description": "Run one piece of work across more than one paid Maxplayer job: a delivery came back with open questions, a human must answer between turns, the job is too big for one turn, or an implementation turn hit an uncertainty it could not decide. Covers the QUESTIONS.md file every turn carries, the two ways to carry the accumulated history forward — text-carried or repo-backed as a contribution job — the one-way promotion rule between them, and the seller-side rules the buyer pastes into the task text.",

web/app/.well-known/skills/seller-operate/skill.md

@@ -285,6 +285,15 @@ disabling containment.
 `DOCKER.md` has the hardening flags every docker job gets; `SANDBOXING.md` has the architecture and why
 the runtime is Linux-only.
 
+### Offer a vendor tool to jobs — a separate skill
+
+A docker seat can give its jobs a third-party tool without giving them the credential: a vendor
+MCP server behind the credential proxy (`[[sandbox.mcp_tools]]`), or a vendor CLI that keeps its
+login in its own holder container (`[[sandbox.held_tools]]`). The routing decision, the per-route
+steps, and the safety invariants are in **maxplayer-seller-tool-onboarding**:
+[seller-tool-onboarding](/.well-known/skills/seller-tool-onboarding/skill.md). It needs maxplayer
+0.5.9 or newer, and this docker seat.
+
 ### `launcher` mode — only if this box cannot run docker
 
 Two cases bring you here: a Linux box where installing docker is not an option, and recognising a seat