Holder And Flow Analysis
Analyse early buyers, top-holder concentration, wallet clusters, and smart-money flows. Used by WHALE after RISK CLEAR or CONDITIONAL.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Holder And Flow Analysis when an AI agent needs a reusable SKILL.md workflow for this job: Analyse early buyers, top-holder concentration, wallet clusters, and smart-money flows. Used by WHALE after RISK CLEAR or CONDITIONAL.
When not to use it
Skip Holder And Flow Analysis when the task is outside the analysis category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/holder-and-flow-analysis # Save SKILL.md to ~/.claude/skills/holder-and-flow-analysis/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/holder-and-flow-analysis/SKILL.md. For a shared project, commit the folder at .claude/skills/holder-and-flow-analysis/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Holder And Flow Analysis skill for this task: Use Holder And Flow Analysis when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
68/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 74/100
- Practical detail
- 68/100
- Source evidence
- 56/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Holder and Flow Analysis
## L1 - Summary Smart-money and concentration analysis after RISK CLEAR or CONDITIONAL. Maps who holds the token, how concentrated it is, and whether flows look organic or coordinated. Informs sizing and risk; never authorises a buy.
## L2 - Method 1. Snapshot concentration with the preferred tool path: ```bash python /workspace/pumpgrok/tools/holder_check.py --mint <TOKEN_MINT> --limit 20 ``` 2. Analyse early buyers, top-holder concentration, wallet clusters, and smart-money flows. Correlate with deployer history and large transfers where available. 3. Emit the output schema: ``` LEAD / TICKET-ID: ... Smart-Money Signal: High | Medium | Low | None Supporting Addresses: ... Clusters Detected: yes/no plus description UTC Timestamp: ... Hand-off: CHIEF plus RISK ```
## Failure modes - Sampled-only data: say so (the holder snapshot is sampled); never present it as a full census. - Thin or missing flow evidence: signal `None`, not a guess. - Social-only velocity with no holder evidence: not smart-money evidence.
## References - Tools: `onchain.top_holders` (operator registry); port: `src/pumpgrok/tools/onchain/` - Handoff: CHIEF plus RISK; companion skill: `risk-audit` (the gate this informs)
Intended uses
- Use Holder And Flow Analysis when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.