Does Claude's Macro Rates Dashboard Predict Where Rates Are Headed?

The macro-rates-monitor skill combines macro indicators, the yield curve, inflation breakevens, and swap rates into a dashboard using fixed definitions, producing a correctly assembled snapshot rather than any forecast of where rates are going.

2:13 video3 min readWatch on YouTube

Ask Claude for a macro rates monitor dashboard and it is tempting to picture it forming its own view on where the economy is headed, reading the data like an analyst and telling you what's coming. That is not what happens. The macro-rates-monitor skill reads a written SKILL.md and combines exactly four named inputs using definitions already written for them. It does not forecast anything.

The natural but wrong assumption

The intuitive guess is that asking for a macro rates dashboard means Claude is forming an original view on where the economy is headed. It is not. The skill is a fixed procedure that combines four named things, macro indicators, the yield curve, inflation breakevens, and swap rates, using the relationships already defined for them, such as splitting a yield into its real and nominal components. Ask it instead to forecast what a central bank will actually do next quarter, and there is nothing to run. That question is not one of the four things the specification combines.

The four inputs, precisely

The skill takes macro indicators as one input, the shape of the yield curve as a second, inflation breakevens (the market's implied inflation expectation) as a third, and swap rates as a fourth, and combines all four into one dashboard. One pull of market data moves through all four building blocks in a fixed order before it reaches the finished dashboard. Each block uses only the definition the file gives it, nothing added and nothing guessed.

What a finished dashboard actually proves

A completed dashboard proves that the four building blocks were combined the way the file defines them: nothing skipped, nothing improvised. It does not prove that the economic read inside the dashboard will hold up. A correctly computed inflation breakeven can still turn out to be a poor predictor of actual future inflation. If swap rate data is not available and that block cannot populate, that is a data gap, not evidence that the other three blocks are wrong. The two failure modes are separate, and a missing block does not discredit the rest of the dashboard.

Combination, not forecasting

A macro rates dashboard from Claude is not an original economic call. It is four named inputs, macro indicators, yield curve, breakevens, and swap rates, combined by one fixed, repeatable procedure. A finished dashboard means the combination ran correctly, not that reality will follow it. The distinction matters most at the exact point where someone tries to push past what the four inputs cover, asking for a prediction of what a central bank will do, and finds the skill has nothing to offer there.

Seeing the boundary yourself

The fastest way to see the line between "combines what's defined" and "predicts what isn't" is to run both requests back to back. Ask Claude to pull together a macro rates read for a region you follow, combining the yield curve shape, inflation breakevens, and swap rates, and have it show the definition it is using for each piece before combining them. Then ask what the central bank will actually do next quarter, and watch what it can and cannot answer.

Key takeaways

  • The macro-rates-monitor skill combines four fixed inputs (macro indicators, yield curve, inflation breakevens, swap rates) using written definitions; it does not forecast.
  • A completed dashboard proves the combination ran correctly, not that the economic read inside it will turn out accurate.
  • A missing input, like unavailable swap rate data, is a data gap, not evidence that the rest of the dashboard is wrong.
  • Asking the skill what a central bank will do next quarter falls outside what the four inputs cover, and the skill has nothing to run for that question.
  • Testing both a combination request and a forecast request side by side is the clearest way to see the actual boundary of the skill.

Who this is for

Anyone using Claude to build macro or rates-related dashboards who wants to know precisely what the output represents, and where the line falls between a correctly assembled data snapshot and an actual market forecast.

Chapters

  1. 0:00Can Claude predict where rates go?
  2. 0:11Forecast, or four inputs?
  3. 0:42One package, four inputs
  4. 1:05Finished, with a catch
  5. 1:30Carry-out
  6. 1:47Your turn
  7. 2:07Outro
Full transcript(auto-generated, with timestamps)

Can Claude predict where rates go?

[0:00]Someone asks whether a macro rates dashboard means Claude is predicting where rates are headed next. It isn't. Liam is here to take you through what the skill actually combines and what it leaves alone. The natural guess is that

Forecast, or four inputs?

[0:12]Asking Claude for macro rates dashboard means it's forming its own view on where the economy is headed. Reading the data and telling you what's coming. But the skill is a fixed procedure. It combines four named things macro indicators, the yield curve, inflation break heavens, and swap rates using the relationships already defined for them like splitting a yield into its real and nominal parts. Ask it instead to forecast what the central bank will actually do next quarter. And there's nothing to run. That's not one of the four things the spec combines. What the skill actually

One package, four inputs

[0:42]Does, it takes macro indicators as one input, the shape of the yield curve as a second, inflation break heavens, the market's implied inflation expectation as a third, and swap rates as a fourth, and combines all four into one dashboard. Watch the anchor. One pull of market data moving through all four building blocks in order before it reaches the dashboard. Each block uses only the definition the file gives it, nothing added, nothing guessed. The data

Finished, with a catch

[1:05]Package comes out the other side as a finished dashboard, but that only proves the four building blocks were combined the way the file defines them. Nothing skipped, nothing improvised. It doesn't prove the economic read inside the dashboard will hold up a correctly computed break heaven can still turn out to be a poor predictor of actual inflation. And if swap rate data isn't available and that block can't populate, that's a data gap, not evidence the other three blocks are wrong. A macro

Carry-out

[1:30]Rates dashboard from Claude isn't an original economic call. Its four named inputs, macro indicators, yield curve, break heavens, and swap rates combined by one fixed repeatable procedure. A finished dashboard means the combination ran correctly, not that reality will follow it. Your turn. Here's the prompt.

Your turn

[1:48]Read it with me. Pick a country or region you follow. Ask Claw to pull together a macro rates read combining the yield curve shape inflation break Evans and swap rates and have it show you the definition it's using for each piece before it combines them. Then ask it what the central bank will actually do next quarter and watch what it can and can't answer. Liam in for bear. Does Claude's macro rates dashboard predict

Outro

[2:09]Where rates are headed? Liam in for bear.

More from Claude Basics

Humanitarians AI Lyrical Literacy Project