Skip to content
Back to skills

Macro Evidence

ASecurity

Research macro releases, currency drivers, policy curves and positioning using FXMacroData tools and explicit source evidence. Use for macro briefs, release context and comparative currency research.

  • 1,531 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
ai-agentsperformance

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add hashgraph-online/awesome-codex-plugins --skill macro-evidence --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Macro Evidence?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Macro Evidence
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hashgraph-online-macro-evidence/badge)](https://www.skillsdirectory.com/skills/hashgraph-online-macro-evidence)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: macro-evidence
description: Research macro releases, currency drivers, policy curves and positioning using FXMacroData tools and explicit source evidence. Use for macro briefs, release context and comparative currency research.
---

# Macro evidence

Discover catalogue definitions before selecting series. Keep FXMacroData's documented terminology, currency codes, indicator slugs, units and payload metadata. Tool schemas determine available inputs and scope.

Prefer the keyless public USD catalogue, recent indicator history and release calendar for USD questions. Respect the public history window. Other tools and older history are optional and can require access. Present an access failure without asking for a key in chat or trying another URL with embedded credentials.

Use the plugin's commands for a structured brief, release review, currency comparison or broader research question. Retain source links, periods and timing qualifications in the output. Mark interpretation separately from observations; forecasts, scenario results and revised values must remain distinguishable.

Use returned data only. Preserve empty or unavailable results. Never create an observation, source, exact release time, forecast or coverage promise to complete a table. Reference rates and research outputs do not establish executable prices or future performance.

The host may expose more tools than the reviewed inventory. Consult live schemas rather than improvising parameters. Never issue a health check before every normal call; use `ping` only when needed to investigate connectivity.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.