mcpbeat

Llmquant Etfs

llmquant/llmquant-etfs

Router skill for LLMQuant ETFs workflows. Use when the user needs ETF holdings, overlap, concentration, issuer snapshot, or theme exposure analysis.

1k tokens
context cost
the whole folder, loaded on every use
4
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
183
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/LLMQuant/skills --skill llmquant-etfs

The instruction itself

4 sections, as written by the author

LLMQuant ETFs

This category routes ETF analysis tasks to holdings and exposure workflows.

Routing Rules

  • Identify the ETF tickers, comparison universe, as-of date, and required output.
  • Select the closest workflow below.
  • Open only the selected workflow and required local resources.
  • Use LLMQuant Data for holdings, fund metadata, prices, and coverage notices.
  • Report holdings as_of_date, source, stale flags, unsupported tickers, and missing fields.

Workflow Index

| User intent | Workflow |

|---|---|

| Compare ETF holdings, overlap, concentration, and exposure. | workflows/etf-overlap-report.md |

LLMQuant Data Contract

Prefer LLMQuant Data when available. The workflows may need these data capabilities:

  • Look up ETF identity, issuer, category, expense ratio, market price, NAV, and coverage status.
  • Retrieve ETF holdings with weights, identifiers, sectors, countries, source, and holdings as-of date.
  • Compare ETF holdings overlap, top-name concentration, and exposure breakdowns.
  • Retrieve price history, fund-flow history, and sector exposure history when available.

Fallback:

  • If holdings coverage is unsupported, report the unsupported ticker and the ETF identifiers needed.
  • If LLMQuant Data or a compatible data MCP is unavailable, ask the user for issuer holdings files or holdings tables.
  • Do not approximate holdings from memory.

How to use it

Copy the folder

Take llmquant/llmquant-etfs from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.