CtrlK
BlogDocsLog inGet started
Tessl Logo

earnings-preview

Generate a pre-earnings briefing for any stock using Yahoo Finance data. Use this skill whenever the user wants to prepare for an upcoming earnings report, understand what analysts expect, review a company's beat/miss track record, or get a quick overview before an earnings call. Triggers include: "earnings preview for AAPL", "what to expect from TSLA earnings", "MSFT reports next week", "earnings preview", "pre-earnings analysis", "what are analysts expecting for NVDA", "earnings estimates for", "will GOOGL beat earnings", "earnings beat/miss history", "upcoming earnings", "before earnings", "earnings setup", "consensus estimates", "earnings whisper", "EPS expectations", "what's the street expecting", "earnings season preview", any mention of preparing for or previewing an earnings report, or any request to understand expectations ahead of a company's earnings date. Always use this skill when the user mentions a ticker in context of upcoming earnings, even if they don't say "preview" explicitly.

68

Quality

82%

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

68%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 well-structured, actionable skill body that pulls data via concrete yfinance code and lays out a clear five-section briefing template. Its main weakness is workflow_clarity: it lacks explicit validation/error-recovery checkpoints within the main flow despite the fragile nature of external data fetching.

Suggestions

Add an explicit validation checkpoint after Step 2's data fetch (e.g., check each attribute is non-None/non-empty and surface a clear error or fallback if a source is missing) rather than deferring error handling to the reference file.

Make the Step 2 fetch code self-contained by deriving the ticker from the user's request instead of leaving the placeholder 'ticker = yf.Ticker("AAPL") # replace with actual ticker'.

Tighten the Step 4 caveats list and sample tables, which restate data the reference file already covers, to improve token efficiency.

DimensionReasoningScore

Conciseness

Efficient body that mostly assumes Claude's competence and lets tables and code carry the load, with minor trimmable padding such as the multi-bullet caveats list and the sample-table illustration.

4 / 5

Actionability

Provides executable install/fetch code and a concrete output template with five labeled sections, but the data-fetch script uses a placeholder ticker ('replace with actual ticker') and the output sections are described rather than given as runnable code.

4 / 5

Workflow Clarity

A clear four-step sequence is present, but there are no explicit validation checkpoints or error-recovery loops; the body relies on the reference file's try/except note rather than embedding a checkpoint in the workflow itself.

3 / 5

Progressive Disclosure

Good one-level-deep structure: SKILL.md is an overview and clearly signals a single reference file (references/api_reference.md), which exists and holds the bulk API detail, with only minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

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

An exemplary description that clearly states the skill's purpose and provides an exhaustive, natural set of trigger phrases. It is highly specific and complete, with only minor overlap risk from its permissive ticker clause.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (upcoming earnings date, consensus estimates, beat/miss track record, analyst sentiment, key financial context) sourced from Yahoo Finance, matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both what (generate a pre-earnings briefing using Yahoo Finance data) and when (a long, concrete list of trigger phrases plus an 'Always use this skill when...' clause).

5 / 5

Trigger Term Quality

Comprehensive coverage of natural phrases and synonyms users would say, including 'earnings preview for AAPL', 'what to expect from TSLA earnings', 'consensus estimates', 'earnings whisper', and 'EPS expectations'.

5 / 5

Distinctiveness Conflict Risk

A clear pre-earnings niche with distinct triggers, but the broad 'any mention of a ticker in context of upcoming earnings' clause creates minor overlap risk with general stock-analysis skills.

4 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
himself65/finance-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.