When CHAIN is explicitly set to 'robinhood', the auto-detection logic
previously treated it as unknown and fell back to probing bsc/eth/base,
returning empty data and forcing slow inline workarounds.
Adding a KNOWN_CHAINS tuple that includes 'robinhood' (and 'sol') causes
the script to skip the probe entirely and query the specified chain directly.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Fix output appearing twice by clarifying Output Rule in SKILL.md
- Simplify entry cost batch detail: replace per-wallet lists with
selling/accumulating counts on the batch summary line
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Two improvements:
1. Extract 700-line inline Python script to analyze.py — Claude no longer
streams the entire script as text, reducing response time from ~2min to
~5s (API calls take ~3s, script execution <1s).
Also adds full 3-way concurrency: holders + dev fetched in parallel, then
created-tokens fires immediately when dev result arrives — saving ~1.2s vs
prior serial approach. EVM addresses auto-detect chain (bsc→eth→base).
2. Add Output Rule section after the run command — Claude's reply MUST contain
only the raw stdout verbatim, no summary or omission. Previously the CRITICAL
note appeared before the command, so it was forgotten by reply time; moving
it after (as the last thing Claude reads before replying) enforces compliance.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
gina888666