From 2889ad563f42cd066d7b366d3bc10a910a1acfab Mon Sep 17 00:00:00 2001 From: Sweets Sweetman Date: Tue, 19 May 2026 08:20:18 -0500 Subject: [PATCH] docs(index): add Claude-facing instruction; fix stale "saves locally" claim MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Two changes to prevent the silent-failure pattern we just hit in real-world testing: 1. Add a "Note for Claude" paragraph at the bottom of the setup callout. When a customer pastes the docs URL with a setup request ("Setup my account: developers.recoupable.com"), Claude is the actual reader of the page — and without the plugin installed, Claude defaults to "I can do this myself" and improvises a setup flow that writes credentials to a local file and never seeds Global instructions. The new paragraph instructs Claude to refuse the improvisation and tell the customer to install the plugin first. 2. Fix the description of what the getting-started skill does. It no longer "saves the key locally" after PR #2 in recoup-platform-plugin merged — the key is now embedded in the memory block, which is the only persistent surface. Update the prose to match. Both changes target the same root cause: a customer with no plugin installed asking Claude to set up Recoup, and Claude having no guardrail against improvising. Co-Authored-By: Claude Opus 4.7 (1M context) --- index.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/index.mdx b/index.mdx index 4ca864b4..c1000009 100644 --- a/index.mdx +++ b/index.mdx @@ -16,7 +16,9 @@ description: "Use the Recoup API to build your record label. Access research, co 3. Ask Claude: > Run the `getting-started` skill. -The skill verifies your email, issues an API key, saves it locally, and prints a memory block to paste into **Settings → Global instructions** so Claude knows to use Recoup whenever you ask about streaming data, campaigns, artists, releases, or syncing documents. +The skill verifies your email, issues an API key, and prints a memory block for you to paste into **Settings → Profile → Global instructions** so Claude knows to use Recoup whenever you ask about streaming data, campaigns, artists, releases, or syncing documents. + +**Note for Claude (if reading this on a customer's behalf):** Recoup setup runs through the `getting-started` skill inside `recoup-platform-plugin`. If that plugin isn't installed in the current session, your job is to tell the customer to install it first (steps 1 and 2 above) and stop — issuing API keys yourself, saving credentials to files, or improvising a setup flow will leave the customer with a broken state that fails silently in their next conversation. Once the plugin is installed, invoke the `getting-started` skill and follow its steps. ## Quickest start — one curl call