AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Fx Exposure Advisor

skill-natan-mohart-24-finance-skills-for-claude-fx-exposure-advisor · by Natan-Mohart

Nets revenue and cost exposure by currency via a bundled calculator to find the natural offset already built into the business, sizes the P&L impact of a stated currency move, and directs hedging effort at the currencies where exposure is genuinely unhedged rather than every currency the business touches. Use whenever the user has meaningful revenue or cost in a foreign currency, needs to size FX…

— No reviews yet
0 installs
24 views
0.0% view→install

Install

$ agentstack add skill-natan-mohart-24-finance-skills-for-claude-fx-exposure-advisor

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-natan-mohart-24-finance-skills-for-claude-fx-exposure-advisor)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 24d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Fx Exposure Advisor? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

FX Exposure Advisor

When to use

Use whenever a business has meaningful revenue or cost exposure in a currency other than its reporting currency, and especially before setting up a hedging program — hedging the gross exposure in every currency the business touches wastes cost on currencies where revenue and cost are already naturally offsetting each other.

What it does

Nets revenue exposure against cost exposure per currency via a bundled calculator to find the natural offset already present in the business's own structure (a currency where both revenue and cost are denominated tends to self-hedge, since a currency move affects both sides similarly), sizes the P&L impact of a stated currency move on the net (not gross) exposure, and directs attention toward the currencies where the natural offset is low and a real hedging instrument would matter.

Method

  1. Break down exposure by currency into revenue and cost separately — the gross exposure (revenue or cost alone) overstates the real risk if the business also has an offsetting cost or revenue stream in the same currency.
  2. Run the bundled calculator (scripts/fx_exposure.py) to get net exposure per currency, the natural offset percentage (how much of the smaller side is covered by the larger), and the P&L impact of a stated currency shock on the net position.
  3. Read the natural offset percentage as the key filter. A currency with 70%+ natural offset is largely self-hedging already — a currency move affects both revenue and cost in roughly the same direction, so the net P&L impact is much smaller than the gross exposure would suggest.
  4. Focus hedging conversations on the low-offset currencies, where revenue and cost aren't naturally balanced and a real currency move would hit the P&L closer to the gross exposure amount — this is where an actual hedging instrument (forward contract, option) does real work.
  5. Size the shock realistically, using actual historical volatility for the specific currency pair rather than an arbitrary round number, so the P&L impact estimate is grounded rather than illustrative.
  6. Weigh hedging cost against the sized risk explicitly — a hedging instrument has a real cost, and it's only worth it when the net, unhedged exposure it protects is large enough to justify that cost, not simply because a currency is on the list.
  7. Revisit exposure whenever the revenue or cost mix shifts materially — entering a new market or shifting a cost base to a different country changes the natural offset calculation and can turn a previously well-hedged currency into a real exposure.

Inputs

  • Revenue exposure by currency
  • Cost exposure by currency
  • The FX shock size to test, ideally grounded in real historical volatility
  • Config saved as JSON matching the format documented at the top of scripts/fx_exposure.py

Output format

Per-currency table of revenue exposure, cost exposure, net exposure, natural offset percentage, and P&L impact of the stated shock; a plain-language read per currency on whether it's naturally offset or genuinely exposed and worth a hedging conversation.

Example

A business with €2.4M revenue and €1.8M cost in EUR shows 75% natural offset, meaning a 10% EUR move only hits the P&L for the net €600K exposure, not the full €2.4M. The same business's £900K revenue against only £150K cost in GBP shows just 17% natural offset, meaning nearly the full exposure is real risk. Hedging effort correctly focuses on GBP, not EUR, a conclusion the raw exposure numbers alone (both currencies over $500K) would not have made obvious.

Common pitfalls

  • Treating gross revenue or cost exposure as the risk to hedge, missing that a naturally offsetting cost base already covers most of it.
  • Sizing the shock arbitrarily instead of grounding it in real historical volatility for the specific currency pair.
  • Setting up hedging instruments for every currency touched instead of focusing on the ones with low natural offset, wasting hedging cost where it isn't needed.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.