crypto-check
Skill0 starsChanged 7 days agoMITView on GitHub
State of the crypto market from live data — bitcoin and ether price and trend, RSI, support and resistance, BTC dominance, perpetual funding rates, open interest, spot bitcoin and ether ETF flows and Fear & Greed. Use when the user asks about bitcoin, ether or the crypto market, funding, ETF flows or crypto sentiment.
In this repository3 other files it gives its agents.
- compare-assetsSkill
- market-checkSkill
- stock-checkSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Call get_crypto_context: BTC and ETH dominance, total and altcoin market cap, Fear & Greed, funding rates and open interest, stablecoin …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Crypto check
- Call
get_crypto_context: BTC and ETH dominance, total and altcoin market cap, Fear & Greed, funding rates and open interest, stablecoin supply ratio, the latest settled spot ETF net flows. - For the coin the user asks about, use the
-USDpair (BTC-USD,ETH-USD) withget_instrument_info,get_technical_indicatorsandget_key_levels. - For news on a crypto theme, call
public_search_newswith a short query such as "spot bitcoin ETF flows".
Summarise positioning (funding, open interest), flows (ETF, stablecoins) and sentiment separately, then the price trend and levels. Only bitcoin and ether are covered as instruments; say so if the user asks about another coin. This is research, not investment advice.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

