llmquant-commodities
Router skill for LLMQuant commodities workflows. Use when the user needs commodity spot, futures curve, inventory, roll yield, or macro linkage analysis.
npx skills add LLMQuant/skills --skill llmquant-commodities --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# LLMQuant Commodities This category routes commodity research and futures-curve workflows. It defines the LLMQuant Data inputs required even when some commodity endpoints are future product surface. ## Routing Rules 1. Identify the commodity, contract codes, region, horizon, and output target. 2. Select the closest workflow below. 3. Open only that workflow and relevant local resources. 4. Use LLMQuant Data for spot, futures, inventory, macro, FX, and rate inputs. 5. Report contract dates, observation dates, source coverage, and missing inputs. ## Workflow Index | User intent | Workflow | |---|---| | Build a commodity market brief across price, curve, inventory, macro, and equities. | [`workflows/commodity-market-lens.md`](workflows/commodity-market-lens.md) | | Analyze futures term structure, roll yield, contango/backwardation, and curve shifts. | [`workflows/futures-curve-monitor.md`](workflows/futures-curve-monitor.md) | ## LLMQuant Data Contract Prefer LLMQuant Data when available. The workflows may need these data capabilities: - Retrieve commodity spot or front-month prices, recent changes, volume, and observation timestamp. - Retrieve futures curves by contract month, inclu
- Routing Rules
- Workflow Index
- LLMQuant Data Contract
What does the llmquant-commodities skill do?
Router skill for LLMQuant commodities workflows. Use when the user needs commodity spot, futures curve, inventory, roll yield, or macro linkage analysis.
How do I install it?
Run `npx skills add LLMQuant/skills --skill llmquant-commodities --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From LLMQuant/skills, a repository with 183 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.