Router skill for LLMQuant crypto workflows. Use when the user needs crypto market regime analysis, token research, perpetual funding, basis, leverage, liquidity, or cross-asset crypto context.
Install
npx skills add https://github.com/llmquant/skills --skill llmquant-cryptoSKILL.md
LLMQuant Crypto
This category routes crypto research and trading-context workflows. It covers market regime, token-level diligence, and perpetual funding or basis monitoring.
Routing Rules
- Identify the asset, chain, venue, horizon, benchmark, and requested decision.
- Select the closest workflow below.
- Open only that workflow and any referenced local resources.
- Use LLMQuant Data for crypto prices, liquidity, funding, open interest, on-chain context, macro, ETF, and risk inputs.
- Report timestamps, venue coverage, observation windows, stale notices, and unavailable future inputs.
Workflow Index
| User intent | Workflow |
|---|---|
| Diagnose the crypto market regime across BTC, ETH, majors, liquidity, leverage, and macro. | workflows/crypto-market-regime.md |
| Build a token or protocol research memo with tokenomics, usage, valuation, and risk evidence. | workflows/crypto-token-research.md |
| Monitor perpetual funding, basis, open interest, and leverage crowding. | workflows/crypto-perp-funding-monitor.md |
LLMQuant Data Contract
Prefer LLMQuant Data when available. The workflows may need these data capabilities:
- Retrieve crypto spot prices, OHLCV history, realized volatility, drawdowns, correlations, and liquidity.
- Retrieve perpetual funding, basis, open interest, liquidations, exchange flows, and venue-level timestamps.
- Retrieve token supply, unlock schedules, protocol usage, revenue, TVL, holder concentration, governance, and security-risk context.
- Retrieve macro, rates, liquidity, ETF, and equity-market inputs that affect crypto risk appetite.
Fallback:
- If on-chain, funding, or venue-level data is unavailable, name the missing input and continue only with available price, macro, or user-provided evidence.
- Do not infer live funding, liquidity, TVL, or holder behavior from memory.
Related skills
researchmattpocock575KInvestigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.paper-context-resolverlllllllama451KRigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing Renv-and-assets-bootstraplllllllama450KRigor Setup skill for README-first deep learning repo reproduction. Use when the task is specifically to prepare a conservative conda-first environment, checkpoint and dataset path assumptions, cache location hints, and setup notes before any run on a README-documented repository. Do not use for repo scanning, full orchestration, paper interpretation, final run reporting, or generic environment setup that is not tied to a specific reproduction target.ai-research-explorelllllllama311KRigor Explore compatible skill slug for meaningful and potentially novel deep learning research candidates. Use when the researcher has chosen the task family, dataset, benchmark, evaluation method, provided SOTA references, and wants candidate-only exploration on top of `current_research` with auditable repo understanding, idea gating, fair comparison, and governed experiments written to `explore_outputs/`. Do not use for README-first trusted reproduction, open-ended direction finding, narrow c