CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

calendar

Report scheduled US economic events (CPI, NFP, FOMC, GDP, PCE, ISM, jobless claims...) with times in ET, impact, actual/consensus/previous. Use when user asks about the economic calendar, macro events, what data comes out today/this week, or release times. Optional ForexFactory cross-check for the current week.

Quality

92%

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

100%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 a model of a script-backed skill: one executable command with fully documented arguments, a precise output-schema contract including verification and cross-check fields, examples covering common cases, and concrete reporting rules — all matching the actual bundle script. It is lean, assumes Claude's competence, and requires no external reference files.

DimensionReasoningScore

Conciseness

The body explains nothing Claude already knows — every section carries non-inferable operational detail such as the times_verified ET-clock derivation, ForexFactory rate-limit caching behavior, and null-events semantics. It matches the "lean and efficient; every token earns its place" anchor; the 4 anchor's trimmable over-explanation is absent.

5 / 5

Actionability

"uv run python scripts/events.py [--date YYYY-MM-DD] [--days N] [--impact all|high] [--forexfactory]" is fully executable, every flag is documented, and three copy-paste examples cover the common cases (today, ranged high-impact with cross-check, next week); the referenced scripts/events.py exists in the bundle and implements exactly these flags. This matches the 5 anchor; the 4 anchor's "minor gaps" do not apply.

5 / 5

Workflow Clarity

As a simple single-command skill, the run-then-report sequence is unambiguous, and the Reporting section turns the output's verification fields (verified, times_verified, cross_check, events: null) into explicit checkpoints — "Flag any day with events: null or verified: false... list every time_mismatch / missing_in_nasdaq". Per the simple-skill scoring note this warrants 5, and no destructive/batch cap applies.

5 / 5

Progressive Disclosure

The SKILL.md is a self-contained overview whose only bundle reference is the exact path scripts/events.py, which exists and is one level deep; sections (Instructions, Arguments, Output, Examples, Reporting, Dependencies, Timezone) are well organized with no inlined content that belongs in a separate file. Against the actual bundle structure this matches the 5 anchor for a skill with no need for external references.

5 / 5

Total

20

/

20

Passed

Description

83%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 description with a clear, concrete statement of what it does and an explicit, natural-language "Use when..." trigger clause. Third-person voice is used correctly and event acronyms add keyword coverage. The only weaknesses are a slightly narrow action list and a few missing common synonyms (e.g., "jobs report", "nonfarm payrolls") alongside the broad "macro events" trigger.

DimensionReasoningScore

Specificity

"Report scheduled US economic events (CPI, NFP, FOMC, GDP, PCE, ISM, jobless claims...) with times in ET, impact, actual/consensus/previous" plus "Optional ForexFactory cross-check" names concrete actions with explicit output fields and event types, but the action set is essentially one reporting action plus an optional cross-check — narrower than the comprehensive multi-action coverage of the 5 anchor, yet well above the 3 anchor's minimal action list.

4 / 5

Completeness

It explicitly answers both questions: the "what" is concrete (report events with ET times, impact, actual/consensus/previous, optional cross-check) and the "when" is an explicit "Use when..." clause with concrete trigger phrases — a direct match to the 5 anchor; the 4 anchor's weaker 'when' does not apply.

5 / 5

Trigger Term Quality

"Use when user asks about the economic calendar, macro events, what data comes out today/this week, or release times" provides natural phrases users would actually say, supplemented by acronyms (CPI, NFP, FOMC); common synonyms like "jobs report", "nonfarm payrolls", or "inflation data" are missing, so it falls short of the 5 anchor's comprehensive synonym coverage but clearly exceeds the 3 anchor's partial coverage.

4 / 5

Distinctiveness Conflict Risk

"Scheduled US economic events" and "economic calendar" stake out a clear niche with distinct triggers, but the trigger "macro events" is broad enough to overlap closely related macro/trading skills, giving minor overlap risk — matching the 4 anchor rather than the 5 anchor's minimal conflict risk.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

staskh/trading_skills

Path

.claude/skills/calendar/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.