docs: surface nansen trade across README, help banner, and npm metadata#421
Open
0xlaveen wants to merge 1 commit into
Open
docs: surface nansen trade across README, help banner, and npm metadata#4210xlaveen wants to merge 1 commit into
0xlaveen wants to merge 1 commit into
Conversation
Internal users reported their agents claim nansen-cli has no trading functionality. Root cause: every surface a model scans first (README tagline, npm description, `nansen` help line) framed the CLI as analytics-only, so agents answered from priors without running --help. Reframe across five surfaces to lead with both analytics and DEX trading: README tagline + new Capabilities section, package.json description + keywords (dex/swap/trading/jupiter/aggregator), CLI help banner trade line, schema.json trade description, and AGENTS.md Capabilities header. No behavior change. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Internal users reported that their agents (e.g. Claw) confidently claim nansen-cli has no trading functionality and route directly to Uniswap / Aerodrome / Jupiter instead. Root cause is a docs framing problem, not a missing feature:
nansen tradeexists withquote,execute,bridge-status, andlimit-order, but every surface a model scans first frames the CLI as analytics-only, so agents answer from priors without ever running--help.This PR reframes five surfaces to lead with both analytics and DEX trading:
README.md— tagline rewritten ("Onchain analytics and DEX trading from the command line"), new "What it does" section above Installation, Trading section beefed up with bridge + limit-order examples, Trade keywords (Jupiter, 0x, best-quote routing) added inline.package.json— description rewritten; addeddex,swap,trading,jupiter,aggregator,base,bridgekeywords so npm search surfaces it.src/cli.js(HELP banner) —tradeline now readsDEX swaps on Solana & Base via best-quote routing (Jupiter/0x): quote, execute, bridge-status, limit-order. Added a swap example to EXAMPLES.src/schema.json— trade root description rewritten sonansen schema tradereturns a richer line.AGENTS.md— added Capabilities section so contributor docs lead with both analytics and trade.No behavior change. Patch changeset added.
Test plan
npm test(1394 passed, 2 skipped)npm run lint(clean)node src/index.jssmoke-tested — help banner reads correctly🤖 Generated with Claude Code