agentleFS
d-wweid-wwei/openclaw-financial-services/skills/fsi-lseg-cmd-analyze-fx-carry/SKILL.md

fsi-lseg-cmd-analyze-fx-carry

Skill16 starsChanged 9 months agoApache-2.0View on GitHub

Evaluate FX carry trade opportunities with spot, forwards, vol surface, and historical context — usage: /analyze-fx-carry <currency pair e.g. USDJPY> [tenor e.g. 3M]

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the user for:

    line 21
  2. Very specific:

    Call fx_spot_price with the currency pair.

    line 28
  3. Very specific:

    Call fx_forward_price with the pair and target tenor.

    line 34
  4. Very specific:

    Call fx_forward_curve (list then calculate) for the pair.

    line 40
  5. Very specific:

    Call fx_vol_surface for the pair.

    line 46
  6. Very specific:

    Call tscc_historical_pricing_summaries for the pair's RIC with interval: "P1D", tenor: "1Y".

    line 54

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

Analyze FX Carry Trade

This command uses LSEG FX pricing, forward curves, volatility surfaces, and historical data tools. See CONNECTORS.md for available tools.

Evaluate carry trade opportunities for a currency pair by combining spot rates, forward points, the carry term structure, volatility risk, and historical price context.

See the fx-carry-trade skill for domain knowledge on carry frameworks and risk metrics.

Workflow

1. Gather Input

Ask the user for:

  • Currency pair (required) — e.g., USDJPY, EURUSD, AUDUSD
  • Target tenor (optional, default 3M)
  • Valuation date (optional, defaults to today)

2. Get the Spot Rate

Call fx_spot_price with the currency pair.

Extract: mid/bid/ask rates, bid-ask spread.

3. Price the Forward at Target Tenor

Call fx_forward_price with the pair and target tenor.

Extract: forward rate, forward points. Compute annualized carry.

4. Map the Full Carry Curve

Call fx_forward_curve (list then calculate) for the pair.

Present carry profile across tenors (ON through 1Y): forward points, annualized carry, cumulative carry. Identify the sweet-spot tenor.

5. Assess Volatility Risk

Call fx_vol_surface for the pair.

Extract: ATM vol at target tenor, 25-delta risk reversal, 25-delta butterfly.

Compute carry-to-vol ratio = annualized carry / ATM implied vol.

6. Historical Spot Context

Call tscc_historical_pricing_summaries for the pair's RIC with interval: "P1D", tenor: "1Y".

Assess: 52-week range, current position in range, trend direction.

7. Synthesize the Report

Present: carry-to-vol ratio and overall assessment, spot & forward pricing, carry term structure table, vol surface snapshot, historical context.

Output Format

Lead with the carry-to-vol ratio and overall assessment (attractive / moderate / unattractive). Follow with detailed supporting data in tables.

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.