site: add Get started install/usage section - #7
Conversation
🤖 Augment PR SummarySummary: Adds a new Get started section to the landing page to help users install and use the hosted qupick/Bitrefill flow. Changes:
🤖 Was this summary useful? React with 👍 or 👎 |
| <span class="n">1</span> | ||
| <h3>Install the skill</h3> | ||
| <p>Drop <code>qupick</code> and its sibling <code>bitrefill</code> into Claude Code together.</p> | ||
| <div class="code"><span class="c">cp -R</span> skills/qupick .claude/skills/ |
There was a problem hiding this comment.
cp -R ... .claude/skills/ assumes .claude/skills/ already exists; on a fresh Claude Code setup these commands will fail unless the directory is created first (the README includes a mkdir -p .claude/skills step).
Severity: medium
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
There was a problem hiding this comment.
Fixed in 28fc79d — added a mkdir -p .claude/skills line before the cp -R in step 1.
| Point <code>.mcp.json</code> at the hosted server and register once — your API key is | ||
| emailed to you. Paste it into the <code>Authorization</code> header and reconnect. | ||
| </p> | ||
| <div class="code"><span class="c">url</span> qupick.quip.network/mcp |
There was a problem hiding this comment.
The MCP endpoint shown as qupick.quip.network/mcp is missing a URL scheme; .mcp.json typically requires the full https://... URL (as shown in the README). Without it, copy/paste setup is likely to produce an invalid config.
Severity: medium
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
There was a problem hiding this comment.
Fixed in 28fc79d — the step 2 panel now shows the full https://qupick.quip.network/mcp.
Adds a "Get started" section to the landing page covering install and usage, drawn from the README's hosted-setup flow.
What's in the section
--inksurface and mono/green tokens.Get startednav link.The full 5-step register flow stays in the README; the section links to it rather than reproducing it.
Install framing (MCP-first)
qupick's purchase layer is the Bitrefill MCP (
mcp__bitrefill__*tools —search-products,product-details,buy-products,get-invoice-by-id). It does not use the bitrefill skill's own mechanics. Step 1 therefore connects the MCP directly:This pairs with #8, which removes the vendored
skills/bitrefill/copy. The two PRs touch disjoint files (this one:site/index.html; #8: README/AGENTS/SKILL + the deletion), so they don't conflict and can merge in either order.Notes
python3 -m http.serverand previewed in-browser.