earnings-calendar
Get upcoming earnings dates with timing (before/after market) and EPS estimates. Use when user asks about earnings dates, earnings calendar, when a company reports, or upcoming earnings.
93
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that clearly communicates specific capabilities (earnings dates, market timing, EPS estimates), includes a comprehensive 'Use when' clause with natural trigger terms, and occupies a distinct niche. It follows the third-person voice convention and is concise without unnecessary padding.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Get upcoming earnings dates', 'timing (before/after market)', and 'EPS estimates'. These are clear, concrete capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Get upcoming earnings dates with timing and EPS estimates') and when ('Use when user asks about earnings dates, earnings calendar, when a company reports, or upcoming earnings') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'earnings dates', 'earnings calendar', 'when a company reports', 'upcoming earnings'. These cover common variations of how users would phrase such requests. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly occupies a distinct niche around earnings dates and reporting schedules. The specific financial domain terms like 'earnings calendar', 'EPS estimates', and 'before/after market' make it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A solid, well-structured skill for a simple single-command task. The command syntax, arguments, and output schema are clearly documented with good examples. Minor inefficiencies include the unnecessary 'Use Cases' and 'Dependencies' sections that add tokens without adding actionable value for Claude.
Suggestions
Remove the 'Use Cases' section—it describes motivation rather than providing actionable guidance, and Claude can infer appropriate usage from context.
Consider removing or condensing the 'Dependencies' section since the script manages its own imports; if kept, it could be a single inline note.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but the 'Use Cases' section is unnecessary filler—Claude doesn't need to be told why someone would check earnings dates. The 'Dependencies' section is also low-value since the script presumably handles its own imports. The output field descriptions and examples are well-structured though. | 2 / 3 |
Actionability | Provides concrete, copy-paste-ready bash commands with clear argument format. The output schema is well-specified with field names, types, and possible values. Multiple examples cover single and multi-symbol usage patterns. | 3 / 3 |
Workflow Clarity | This is a simple single-command skill with no multi-step process or destructive operations. The single action is unambiguous: run the script with symbols, get structured output. The note about uv vs python fallback is a helpful conditional. No validation checkpoints are needed here. | 3 / 3 |
Progressive Disclosure | For a simple single-purpose skill under 50 lines, the content is well-organized with clear sections (Instructions, Arguments, Output, Examples, Timezone). No external references are needed and none are artificially created. The structure supports quick scanning. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- staskh/trading_skills
- Commit
2db8c82
- 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.