agentleFS
JerryLiu369JerryLiu369/awesome-quant-skills/skills/global-equities/llmquant-macro/SKILL.md

llmquant-macro

Skill3 starsChanged 33 days agoMITView on GitHub

This category routes macroeconomic research workflows for regime dashboards, policy previews, and portfolio impact mapping. Prefer LLMQuant Data when available. The workflows may need these data capabilities: - Retrieve macro indicator snapshots, histories, revisions, release dates, and consensus context. - Retrieve central-bank policy rates, rate expectations, yield curves, inflation, labor, growth, housing, liquidity, and sentiment. - Retrieve cross-asset prices for equities, rates, FX, commodities, credit, crypto, and volatility. - Retrieve portfolio exposures and ETF look-through when translating macro into portfolio…

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use LLMQuant Data for macro observations, release dates, rates, FX, commodities, credit, equity indices, and research context.

    line 23
  2. Distinctive:

    Prefer LLMQuant Data when available.

    line 36
  3. Distinctive:

    If a macro series or release calendar is unavailable, name the missing input and avoid time-sensitive claims.

    line 43
  4. Distinctive:

    Do not imply real-time macro data when only latest closed observations are available.

    line 44

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Imported from: https://github.com/LLMQuant/skills Source Path: skills/llmquant-macro/SKILL.md Curated for awesome-quant-skills -->

name: llmquant-macro description: Router skill for LLMQuant macro workflows. Use when the user needs macro dashboards, Fed or central-bank previews, inflation and growth context, liquidity, or macro-to-portfolio impact analysis. input_data_source: LLMQuant Data category: macro

LLMQuant Macro

This category routes macroeconomic research workflows for regime dashboards, policy previews, and portfolio impact mapping.

Routing Rules

  1. Identify geography, indicators, policy body, asset universe, horizon, and requested deliverable.
  2. Select the closest workflow below.
  3. Open only that workflow and any referenced local resources.
  4. Use LLMQuant Data for macro observations, release dates, rates, FX, commodities, credit, equity indices, and research context.
  5. Report observation dates, release dates, revisions, frequencies, stale notices, and missing inputs.

Workflow Index

User intentWorkflow
Build a cross-indicator macro dashboard and regime view.workflows/global-macro-dashboard.md
Prepare a Fed or central-bank policy meeting preview.workflows/fed-policy-preview.md
Translate macro data into equity, rates, credit, FX, commodity, and portfolio implications.workflows/macro-to-portfolio-impact.md

LLMQuant Data Contract

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

  • Retrieve macro indicator snapshots, histories, revisions, release dates, and consensus context.
  • Retrieve central-bank policy rates, rate expectations, yield curves, inflation, labor, growth, housing, liquidity, and sentiment.
  • Retrieve cross-asset prices for equities, rates, FX, commodities, credit, crypto, and volatility.
  • Retrieve portfolio exposures and ETF look-through when translating macro into portfolio impact.

Fallback:

  • If a macro series or release calendar is unavailable, name the missing input and avoid time-sensitive claims.
  • Do not imply real-time macro data when only latest closed observations are available.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.