CtrlK
BlogDocsLog inGet started
Tessl Logo

earnings-recap

Generate a post-earnings analysis for any stock using Yahoo Finance data. Use when the user wants to review what happened after earnings, understand beat/miss results, see stock reaction, or get an earnings recap. Triggers: "AAPL earnings recap", "how did TSLA earnings go", "MSFT earnings results", "did NVDA beat earnings", "post-earnings analysis", "earnings surprise", "what happened with GOOGL earnings", "earnings reaction", "stock moved after earnings", "EPS beat or miss", "revenue beat or miss", "quarterly results for", "how were earnings", "AMZN reported last night", "earnings call recap", or any request about a company's recent earnings outcome. Use this skill when the user references a past earnings event, even if they just say "AAPL reported" or "how did they do".

71

Quality

86%

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

78%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, mostly executable skill body with good progressive disclosure and a clear step sequence. The main gaps are a hardcoded ticker placeholder, approximate reaction-window logic, and data-validation logic that lives in the reference rather than the main workflow.

Suggestions

Add an inline guard in Step 2/3 to check that earnings_history is non-empty before indexing, so the main workflow has an explicit validation checkpoint rather than relying on the reference file.

Parameterize the ticker clearly (e.g., a named variable extracted from the user request) instead of a hardcoded 'AAPL' with a comment, to make the core script copy-paste ready.

Tighten the intro and remove the price-reaction tips duplicated between the body and references/api_reference.md to reduce token overlap.

DimensionReasoningScore

Conciseness

Mostly efficient with code blocks and tables carrying the load, but includes minor over-explanation ('a complete picture of what happened') and some content that overlaps the reference file (price-reaction tips appear in both).

4 / 5

Actionability

Provides concrete, executable Python for data gathering, price reaction, and margin calculations, but the ticker is hardcoded with a 'replace with actual ticker' placeholder and the reaction-window logic is acknowledged as approximate.

4 / 5

Workflow Clarity

A clear five-step sequence with an install-validation checkpoint in Step 1, but the body itself lacks an explicit validation step for the fetched data (empty/None earnings_history handling is delegated to the reference file rather than inline).

4 / 5

Progressive Disclosure

Well-organized into clearly headed steps with a single one-level-deep reference (references/api_reference.md, verified present) that is explicitly signaled and reserved for method signatures and edge cases.

5 / 5

Total

17

/

20

Passed

Description

95%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, well-structured description that explicitly covers both what the skill does and when to use it, with an extensive set of natural trigger phrases and a distinct niche. The only weakness is that the listed capabilities are synonymous variations rather than a breadth of distinct actions.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('Generate a post-earnings analysis', 'review what happened after earnings', 'understand beat/miss results, see stock reaction, or get an earnings recap'), but they are variations on a single theme rather than a comprehensive set of distinct actions.

4 / 5

Completeness

Clearly states what it does ('Generate a post-earnings analysis for any stock using Yahoo Finance data') and explicitly when to use it with concrete trigger phrases ('Use when the user wants to…', 'Use this skill when the user references a past earnings event').

5 / 5

Trigger Term Quality

Comprehensive coverage of natural user phrases including synonyms and variations ('AAPL earnings recap', 'did NVDA beat earnings', 'EPS beat or miss', 'AMZN reported last night', 'earnings call recap'), which users would plausibly say verbatim.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (post-earnings stock analysis via Yahoo Finance) with earnings-specific triggers, making conflict with other skills minimal.

5 / 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.