feat(plugin)!: one vocabulary across both plugins, and a /help in each (#335)

BREAKING CHANGE: three commands were renamed. /stocks:stocks → /stocks:report,
/crypto:crypto → /crypto:report, /crypto:coin → /crypto:lookup.

The two plugins had grown separate words for the same question — `stocks` and
`crypto` for "the full report", `coin` and `lookup` for "name → symbol" — so
knowing one taught you nothing about the other. Worse, the headline command in
each was named after its own plugin, which is what produced `/crypto:crypto`.

They cannot ship the same *set*: a pair has no earnings transcript and an equity
has no order book. They can share vocabulary, and now do:

  shared    help · report · quote · lookup
  stocks    signals · research · reports · discover
  crypto    book · bars · spark · pairs

Eight each, four spelled identically. `/stocks:report NVDA` and
`/crypto:report BTC` are the same question asked of different markets.

New in both: `/…:help`, which lists that plugin's commands with no tool call —
the answer to "command not found" being a dead end rather than a signpost.

New in stocks: `/stocks:quote`, the four-line read. It exists because the CLI
already aliases `quote` to `report` for equities, so the plugin was the only
surface where the word did not work — which is exactly how someone found it.
It reads the same document as `report`; the difference is how much it prints.

Two tests hold the shape: every plugin must ship each shared name, and no
command may repeat its own plugin's name. The second one is what a bare
`/crypto:crypto` would have failed.

Both plugins go to 0.3.0 — renamed commands do not reach an existing install
until that number moves.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: ralyodio

README.md

@@ -376,14 +376,20 @@ moshcode plugin install crypto    # add the marketplace + install `crypto`
 moshcode plugin remove stocks     # take it back off
 ```
 
-`stocks@moshcode` adds `/stocks:stocks`, `/stocks:signals`, `/stocks:research`,
-`/stocks:lookup`, `/stocks:reports`, and `/stocks:discover` — the same advis0r research surface described above,
-driven from inside a coding session.
+The two plugins share the four names for the questions both markets answer, and
+differ only where the markets do. Either one's `/…:help` prints its own list.
 
-`crypto@moshcode` adds `/crypto:crypto`, `/crypto:quote`, `/crypto:book`,
-`/crypto:bars`, `/crypto:spark`, `/crypto:pairs`, and `/crypto:coin`. It ships separately because it is a different surface,
-not a mode of the first: live venue reads instead of stored snapshots, and a
-score that must not be ranked against an equity's.
+| | `stocks@moshcode` | `crypto@moshcode` |
+|---|---|---|
+| shared | `help` `report` `quote` `lookup` | `help` `report` `quote` `lookup` |
+| its own | `signals` `research` `reports` `discover` | `book` `bars` `spark` `pairs` |
+
+So `/stocks:report NVDA` and `/crypto:report BTC` are the same question asked of
+different markets, while `/stocks:signals` (what an executive said on a call)
+and `/crypto:book` (live order book depth) have no counterpart on the other
+side. They ship separately because they are different surfaces, not modes of one
+another: stored snapshots versus live venue reads, and a crypto score that must
+not be ranked against an equity's.
 
 Restart the engine after installing either; a newly installed plugin is not live
 in a session that is already running.
@@ -420,7 +426,7 @@ any marketplace". `moshcode plugin install` runs both steps for you.
 ### Upgrading from `ticker@moshcode`
 
 `stocks` was called `ticker` before v0.29.0. Installing the new id does **not**
-replace the old one — engines install plugins side by side, so `/stocks:stocks` would
+replace the old one — engines install plugins side by side, so `/stocks:report` would
 come from two plugins at once. Remove the old id first:
 
 ```sh

plugins/crypto/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "crypto",
   "description": "Crypto market data slash commands backed by advis0r.com: live prices, technical scores, order books, OHLCV history and sparklines across Alpaca's US crypto venue.",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "author": {
     "name": "moshcoder",
     "url": "https://moshcode.sh"

plugins/crypto/README.md

@@ -6,13 +6,19 @@ across Alpaca's US crypto venue.
 
 | command | what it does |
 | --- | --- |
-| `/crypto:crypto BTC` | price, technicals, score, supply, order book |
+| `/crypto:help` | this list, in the engine |
+| `/crypto:report BTC` | price, technicals, score, supply, order book |
 | `/crypto:quote ETH-USD` | latest trade and quote, with the spread in bps |
+| `/crypto:lookup bitcoin` | asset name → `BTC/USD` |
 | `/crypto:book BTC-USD` | top of the order book, both sides |
 | `/crypto:bars ETH-USD` | historical OHLCV at any supported timeframe |
 | `/crypto:spark BTC ETH SOL` | recent moves across pairs, ranked |
 | `/crypto:pairs` | every supported pair, grouped by quote asset |
-| `/crypto:coin bitcoin` | asset name → `BTC/USD` |
+
+The first four names mean the same thing in `stocks@moshcode` — `help`,
+`report`, `quote`, `lookup` — so knowing one plugin gets you half the other.
+The rest are the parts a 24/7 venue has and equities do not: a live order book,
+arbitrary timeframes, and cross-pair comparison.
 
 Pairs are accepted as `BTC`, `BTC-USD`, `BTC/USD` or `BTCUSD`. A bare asset
 resolves to that asset's USD pair.
@@ -50,9 +56,9 @@ Point the commands at another instance with `MOSHCODE_ADVISOR_URL`.
 ## Why this is separate from `stocks`
 
 They answer different questions from different data, and share only a hostname.
-A `/stocks:stocks` report is a **stored snapshot** built from transcripts, SEC
+A `/stocks:report` report is a **stored snapshot** built from transcripts, SEC
 fundamentals and extracted signals — its risk is a stale price read as a live
-one. A `/crypto:crypto` report is a **live venue read** with no transcripts, no
+one. A `/crypto:report` report is a **live venue read** with no transcripts, no
 filings and no signals — its risk is the opposite: a price that is accurate to
 the second and stale by the time you act on it.
 

plugins/crypto/commands/help.md

@@ -0,0 +1,39 @@
+---
+description: What the crypto plugin can do, and the exact command names to type.
+---
+
+## Task
+
+List what this plugin provides. Do not call any tool — everything needed is
+below. Render it as a compact table, then the notes.
+
+| command | what it does |
+| --- | --- |
+| `/crypto:report <PAIR>` | the full report — price, technicals, score, supply, order book |
+| `/crypto:quote <PAIR>` | the short answer — latest trade, bid/ask, spread |
+| `/crypto:lookup <name>` | asset name → pair (`bitcoin` → `BTC/USD`) |
+| `/crypto:book <PAIR>` | top of the order book, both sides |
+| `/crypto:bars <PAIR>` | historical OHLCV at any supported timeframe |
+| `/crypto:spark <PAIR…>` | recent moves across several pairs, ranked |
+| `/crypto:pairs` | every supported pair, grouped by quote asset |
+
+## Notes to pass on
+
+- Pairs are accepted as `BTC`, `BTC-USD`, `BTC/USD` or `BTCUSD`. A bare asset
+  resolves to that asset's USD pair.
+- Every command name is namespaced `/crypto:…`. A bare `/report` is not a
+  command — Claude Code always prefixes plugin commands with the plugin name.
+- `stocks@moshcode` is the sibling plugin, and the four shared names mean the
+  same thing there: `/stocks:report`, `/stocks:quote`, `/stocks:lookup`,
+  `/stocks:help`. It adds `/stocks:signals`, `/stocks:research`,
+  `/stocks:reports` and `/stocks:discover` — transcript and filing work that
+  has no crypto equivalent.
+- **These are live venue reads, not stored snapshots** — the opposite of the
+  stocks plugin. Prices are Alpaca's US crypto venue alone and can differ
+  materially from other exchanges. Crypto trades 24/7: no close, no halt.
+- The crypto technical score counts venue-local liquidity, so it is **not
+  comparable** to a `/stocks:report` score. Do not rank the two against
+  each other.
+
+If the user asked for something no command covers, say so rather than
+improvising one that does not exist.

plugins/crypto/commands/coin.md plugins/crypto/commands/lookup.mdplugins/crypto/commands/coin.md renamed to plugins/crypto/commands/lookup.md

@@ -28,4 +28,4 @@ Fallback: `curl -sS "https://advis0r.com/api/crypto/lookup?q=<url-encoded>&limit
   match is the one they meant.
 - No match: say this venue lists no such pair, and do not invent a symbol. The
   coin may exist and simply not be listed here — those are different answers.
-- Offer `/crypto:crypto <PAIR>` for the match you land on.
+- Offer `/crypto:report <PAIR>` for the match you land on.

plugins/crypto/commands/pairs.md

@@ -25,7 +25,7 @@ URL-safe spelling (`BTC-USD`) used in paths; `symbol` is canonical (`BTC/USD`).
   different markets with three different liquidity profiles.
 - **`idle` means listed but not currently printing trades** — it is not the same
   as unsupported. Show idle pairs, marked, rather than filtering them out.
-- If the user was looking for a specific coin, use `/crypto:coin <name>` instead of
+- If the user was looking for a specific coin, use `/crypto:lookup <name>` instead of
   scanning this list for them.
 - This is the coverage of one venue, not of crypto. A coin missing here is
   missing *from Alpaca's US venue*.

plugins/crypto/commands/crypto.md plugins/crypto/commands/report.mdplugins/crypto/commands/crypto.md renamed to plugins/crypto/commands/report.md

@@ -42,9 +42,9 @@ resolves to that asset's USD pair.
 - Crypto trades 24/7 with no circuit breakers and no market close. Never
   describe a crypto price as "at the close" or "premarket".
 - State `generatedAt` / `fetchedAt`. This is a live read, so it goes stale in
-  seconds, not days — the opposite failure mode from a stored `/stocks:stocks` report.
+  seconds, not days — the opposite failure mode from a stored `/stocks:report` report.
 - The score's liquidity component counts venue-local volume only, so it is
-  **not comparable** to an equity's score from `/stocks:stocks`. Do not rank the two
+  **not comparable** to an equity's score from `/stocks:report`. Do not rank the two
   against each other.
 - End with the response's own `disclaimer`. This is research, not advice.
 - Link the shareable page: `https://advis0r.com/crypto/<PAIR>`.

plugins/crypto/commands/spark.md

@@ -32,5 +32,5 @@ Fallback: `curl -sS "https://advis0r.com/api/crypto/sparklines?symbols=BTC-USD,E
 - Name the window (`start` → `end`) and the period. "Up 5%" over 24h and over 7d
   are different claims.
 - Do not extrapolate a trend from 24 points, and do not call a direction
-  "momentum" without the technicals to back it — `/crypto:crypto <PAIR>` has those.
+  "momentum" without the technicals to back it — `/crypto:report <PAIR>` has those.
 - End with the response's own `disclaimer`.

plugins/stocks/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "stocks",
   "description": "Equity research slash commands backed by advis0r.com: scored reports, extracted signals, transcript search, company-name lookup, and ranked watchlists.",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "author": {
     "name": "moshcoder",
     "url": "https://moshcode.sh"

plugins/stocks/README.md

@@ -6,13 +6,23 @@ and ranked watchlists.
 
 | command | what it does |
 | --- | --- |
-| `/stocks:stocks NVDA` | score, technicals, fundamentals, thesis, signals, sources |
+| `/stocks:help` | this list, in the engine |
+| `/stocks:report NVDA` | score, technicals, fundamentals, thesis, signals, sources |
+| `/stocks:quote NVDA` | the short answer — price, score, staleness |
+| `/stocks:lookup rivian` | company name → `RIVN` |
 | `/stocks:signals AAPL` | what was actually said, quoted and sourced |
 | `/stocks:research data center` | full-text search across every indexed transcript |
-| `/stocks:lookup rivian` | company name → `RIVN` |
 | `/stocks:reports` | every stored report, best score first |
 | `/stocks:discover fusion` | a ranked watchlist for a topic (slow) |
 
+The first four names mean the same thing in `crypto@moshcode` — `help`,
+`report`, `quote`, `lookup` — so knowing one plugin gets you half the other.
+The rest are the parts equities have and crypto does not: transcripts, filings,
+and a watchlist built from them.
+
+Note `report` and `reports` are different commands: singular takes a symbol and
+returns one write-up, plural takes nothing and lists the whole stored index.
+
 The `stocks:` prefix is not optional. Claude Code namespaces every plugin
 command as `/<plugin>:<command>` — always, not only when two plugins collide —
 so a bare `/stocks` answers `Unknown command`. Typing `/` and picking from the
@@ -24,11 +34,11 @@ command, not this plugin's.)
 ## Upgrading from `ticker@moshcode`
 
 This plugin used to be called `ticker`. Both it and its headline command were
-renamed so the name says which market it covers, now that `/crypto:crypto` sits beside
+renamed so the name says which market it covers, now that `/crypto:report` sits beside
 it.
 
 Installing the new one does **not** replace the old one — engines install
-plugins side by side, so `/stocks:stocks` would come from two plugins at once. Remove
+plugins side by side, so `/stocks:report` would come from two plugins at once. Remove
 the old id first:
 
 ```bash