CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

78%

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

Fix and improve this skill with Tessl

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

Quality

Content

73%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 highly actionable, well-sequenced workflow with excellent error-handling specificity and a properly wired bundle (real scripts and a one-level-deep reference doc). The dominant weakness is redundancy: the same API caveats are repeated multiple times and reference-doc material is duplicated inline, inflating token cost without adding guidance value.

Suggestions

State the legacy v3 endpoint retirement and the 402 restricted-endpoint behavior exactly once (e.g., in a short 'Deprecated / known endpoint issues' subsection) and remove the other three repetitions.

Trim the 'API Details', 'Usage Tips', and 'Event Coverage' sections to a couple of lines each pointing to references/fmp_api_documentation.md, since that file already documents rate limits, auth, and best practices.

Condense Step 5's impact taxonomy to the FMP-specific facts (impact field values, clustering heuristic) and drop generic explanations of which indicators are market-moving.

DimensionReasoningScore

Conciseness

The body is noticeably verbose for a single-endpoint fetcher (~375 lines): the legacy v3 endpoint retirement (2025-08-31) is repeated four times (Overview, Step 3 error handling, Resources, Error Handling), the 402 restricted-endpoint guidance three times, and the "API Details"/"Usage Tips"/"Event Coverage" sections duplicate material already in references/fmp_api_documentation.md. Step 5 also explains impact taxonomy Claude already knows (e.g., that CPI and NFP are high-impact). This matches anchor 2 ("several unnecessary explanations or padded sections") rather than 3, since the padding is repeated across sections rather than being a few tighten-able spots.

2 / 5

Actionability

Guidance is fully executable: copy-paste-ready CLI invocations for default, explicit-range, and env-var cases; a documented parameter table (--from/--to/--api-key/--format/--output); a concrete JSON event structure; specific filter mappings ("impact == 'High'", name-search terms for central bank events); and precise failure semantics (exit codes, ZERO_RESULT_REASON stderr markers, key redaction). This matches anchor 5's "copy-paste ready code or commands; specific examples cover the common cases".

5 / 5

Workflow Clarity

The six-step workflow is clearly sequenced (key → date range → fetch → filter → assess → report) with explicit validation checkpoints: date-range validation (start ≤ end, ≤ 90 days), per-failure recovery guidance (429 → wait/re-run, 402 → upgrade not "zero events", empty array → re-verify range and key rather than assume), and the post-fetch instruction to locally filter events outside the requested window. These feedback loops match anchor 5; the operation is read-only, so no destructive/batch cap applies.

5 / 5

Progressive Disclosure

The bundle structure is used well: scripts are referenced with their roles, and references/fmp_api_documentation.md is real, one level deep, and clearly signaled in Resources with a breakdown of its contents. The gap is that the body still inlines a moderate amount of material the reference already covers (endpoint URLs, rate limits, auth, usage tips, parts of error handling), which is more than "minor organization gaps" but well short of anchor 3's example of large inlined reference content with weak signaling — the signaling here is explicit.

4 / 5

Total

16

/

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.

A specific, concrete description that clearly communicates what the skill does and how responsibilities are split between script and assistant. Its main weakness is the absence of any explicit "when to use" trigger guidance, which both caps completeness and omits the most natural user phrasing ("economic calendar").

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about the economic calendar, upcoming economic events or data releases (e.g. FOMC, jobs report, CPI) for a date range."

Include the phrase "economic calendar" and common shorthands (FOMC, NFP, CPI) so the description matches the wording users and the skill name actually use.

Optionally note the boundary (no historical analysis, no earnings) in the description to further reduce overlap with adjacent market-news skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Fetch upcoming economic events and data releases", "Retrieve scheduled central bank decisions, employment reports, inflation data, GDP releases" — and even specifies the division of labor ("The script outputs raw JSON or text; the assistant filters, assesses impact, and generates the Markdown report") with a default date range. Coverage of the skill's capabilities is comprehensive; it is not merely naming the domain with 1-2 actions (score 3) nor leaving minor gaps (score 4).

5 / 5

Completeness

The "what" is clearly and concretely answered (fetch/retrieve scheduled economic indicators via FMP API with a stated default window), but there is no "Use when..." clause or equivalent explicit trigger guidance — per the judging guidelines this caps completeness at 3. It sits above anchor 2 because "what" is fully clear (not vague), but below anchor 4 because "when" is only weakly implied by "upcoming" and never stated.

3 / 5

Trigger Term Quality

Good natural-keyword coverage: "economic events", "central bank decisions", "employment reports", "inflation data", "GDP releases", "market-moving economic indicators" are phrases users would plausibly say. However, the canonical trigger phrase "economic calendar" itself (the skill's name and the most likely user wording) is absent, as are common shorthand triggers like "FOMC", "jobs report", or "CPI release" — matching anchor 4 ("a few natural terms missing") rather than 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — scheduled/upcoming economic indicators via the FMP API — and naming FMP plus specific event families (central bank decisions, CPI-type inflation, GDP) distinguishes it from generic market-data or news skills. Minor overlap risk remains with adjacent skills (e.g., historical market analysis or earnings calendars, which the body explicitly disambiguates but the description does not), fitting anchor 4 rather than 5's "minimal conflict risk".

4 / 5

Total

16

/

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

Path

skills/economic-calendar-fetcher/SKILL.md

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.