CtrlK
BlogDocsLog inGet started
Tessl Logo

fxmacrodata-calendar

Fetch official FXMacroData macro release-calendar events for trade planning, macro regime checks, and event-risk filters. Use before CPI, NFP, GDP, PCE, retail sales, PMI, and central-bank decision windows.

69

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, executable, single-purpose skill whose documented CLI flags, endpoint, and auth variable all check out against the bundled script, with explicit exit-code semantics and acceptance criteria. Remaining gaps are small: no sample output shape, and no stated recovery path when the fetch fails.

Suggestions

Add a brief example of the events[] output shape (key fields like release identifier, timestamp, market_tier) so 'Review events[]' has a concrete referent.

State the recovery action when the fetch exits nonzero (e.g., retry once, then treat the plan as unverified and pause entries) to close the feedback loop explicitly.

Mention the --limit flag alongside --currency and --min-tier since the bundled script supports it and callers may need more than the default 50 rows.

DimensionReasoningScore

Conciseness

The ~40-line body is lean with no padding or explanation of concepts Claude already knows; every sentence carries operational information (command, exit-code semantics, acceptance criteria, auth), matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Provides a copy-paste-ready command ("python3 skills/fxmacrodata-calendar/scripts/fetch_calendar.py --currency usd --min-tier 1" — flags verified against the actual script) plus concrete acceptance criteria (currency match, data_quality confirmation, announcement timestamp, non-empty release identifier). Minor gaps keep it below fully-executable anchor 5: no sample output shape for events[], the --limit flag is undocumented, and no example authenticated invocation is shown.

4 / 5

Workflow Clarity

A clear 3-step sequence with an explicit validation checkpoint ("Treat a nonzero exit as an unverified event-risk state, never as an empty calendar" plus explicit acceptance conditions) and follow-up scheduling. It falls short of anchor 5 because no recovery action is stated when the command fails — the validate-to-retry loop is implied (pause entries) rather than explicit.

4 / 5

Progressive Disclosure

The body is under 50 lines, single-purpose, with well-organized Workflow and Authentication sections and no external reference files needed; the single script reference resolves to a real bundle file. Per the rubric's simple-skill guideline this matches anchor 5.

5 / 5

Total

18

/

20

Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that explicitly states what the skill does and when to use it, with concrete event-name triggers that map directly to user intent. Its only weakness is that it describes a single fetch action with use contexts rather than enumerating several distinct capabilities, and it omits a few common trigger synonyms.

DimensionReasoningScore

Specificity

The description names one concrete action ("Fetch official FXMacroData macro release-calendar events") plus purpose contexts ("trade planning, macro regime checks, and event-risk filters"), but these are use contexts rather than several distinct actions, matching the 'domain and 1-2 concrete actions' anchor rather than the 'several specific actions' anchors above.

3 / 5

Completeness

It explicitly answers both what ("Fetch official FXMacroData macro release-calendar events for trade planning, macro regime checks, and event-risk filters") and when ("Use before CPI, NFP, GDP, PCE, retail sales, PMI, and central-bank decision windows") with concrete trigger phrases, matching anchor 5 exactly.

5 / 5

Trigger Term Quality

"Use before CPI, NFP, GDP, PCE, retail sales, PMI, and central-bank decision windows" provides natural terms users would say, but common variations like "FOMC", "Fed/rate decision", "economic calendar", or "nonfarm payrolls" are missing, fitting the 'good coverage; a few natural terms missing' anchor rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche (official-source FX macro release calendar for trade planning) with domain-specific triggers like CPI, NFP, and central-bank decision windows that are unlikely to fire a wrong skill, matching the 'clear niche with distinct triggers' anchor.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tradermonty/claude-trading-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.