economic-calendar-fetcher

Fetch upcoming economic events and data releases using FMP API. Retrieve scheduled central bank decisions, employment reports, inflation data, GDP releases, and other market-moving economic indicators for specified date ranges (default: next 7 days). The script outputs raw JSON or text; the assistant filters, assesses impact, and generates the Markdown report.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/economic-calendar-fetcher/SKILL.md

Quality

Content

81%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.

The body is highly actionable with a well-sequenced, validated workflow and properly signaled references, but it runs long and repeats the legacy-endpoint deprecation multiple times, which hurts token efficiency. Splitting the report-format and impact-assessment material into reference files would improve progressive disclosure and conciseness.

Suggestions

Consolidate the legacy-endpoint retirement note into a single 'Deprecated endpoints' section instead of restating the 2025-08-31 retirement ~4 times across the body.

Move the full Markdown report-format templates and impact-assessment taxonomy into a separate reference file, keeping only a concise inline example.

Trim conceptual explanations Claude already knows (e.g., what high/medium/low impact means in general market terms) and retain only FMP-specific field and behavior notes.

Dimension	Reasoning	Score
Conciseness	The 375-line body is mostly efficient but includes redundant repetition of the legacy-endpoint retirement (stated ~4 times) and some conceptual explanation Claude already knows (impact-level definitions, market-sensitivity framing) that could be tightened.	3 / 5
Actionability	Provides copy-paste-ready, fully executable script invocations with exact paths and flags, a full parameter list, the JSON event structure, and complete Markdown report templates with a worked example — covering the common fetch and report-generation cases.	5 / 5
Workflow Clarity	Steps 1–6 are clearly sequenced with explicit validation checkpoints (date-range validation in Step 2, a detailed error-handling table, and an empty-list/404 re-verify feedback loop), so the read-only fetch flow has clear error-recovery guidance.	5 / 5
Progressive Disclosure	Good structure with a clearly signaled, one-level-deep reference (references/fmp_api_documentation.md, which exists) and the script under scripts/, but substantial inline detail (full report templates, impact-assessment taxonomy) could be split into separate files.	4 / 5
	Total	17 / 20 Passed

Description

71%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.

The description is specific and covers a comprehensive range of economic event types and concrete actions, but it omits any "Use when..." trigger guidance, leaving the "when" half of completeness unaddressed. Adding an explicit trigger clause would lift completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming natural user phrases (e.g., 'Use when the user asks for upcoming economic events, the economic calendar, CPI/NFP/GDP releases, or central bank meeting dates').

Include common synonyms users actually say — 'jobs report', 'CPI', 'PPI', 'interest rate decision', 'FOMC' — alongside the current event-type list.

Clarify scope boundary in the description itself (e.g., 'Excludes corporate earnings and historical events') to further reduce conflict risk with adjacent skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("Fetch upcoming economic events", "Retrieve scheduled central bank decisions, employment reports, inflation data, GDP releases", "outputs raw JSON or text", "filters, assesses impact, and generates the Markdown report") with comprehensive coverage of event types.	5 / 5
Completeness	Clearly states the "what" (fetch/retrieve events, output formats, assistant role) but provides no "when" — there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Good coverage of natural terms ("economic events", "employment reports", "inflation data", "GDP releases", "economic indicators"), though common synonyms like "jobs report", "CPI", or "interest rate decision" are missing.	4 / 5
Distinctiveness Conflict Risk	The FMP economic-calendar niche is mostly distinct from earnings/news/real-time skills, with only minor overlap risk from broad terms like "economic events" that could match a general market-news skill.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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
Path: skills/economic-calendar-fetcher/SKILL.md
Commit: 9ef78d6

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.