CtrlK
BlogDocsLog inGet started
Tessl Logo

earnings-preview

Build pre-earnings analysis with estimate models, scenario frameworks, and key metrics to watch. Use before a company reports quarterly earnings to prepare positioning notes, set up bull/bear scenarios, and identify what will move the stock. Triggers on "earnings preview", "what to watch for [company] earnings", "pre-earnings", "earnings setup", or "preview Q[X] for [company]".

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is token-efficient and well-structured for a self-contained instruction-only skill, but its actionability and workflow clarity are held back by bracketed placeholder templates and an absence of validation checkpoints in the workflow.

Suggestions

Replace the empty scenario-table cells and bracketed catalyst-checklist placeholders ('[Metric] vs. [consensus/whisper number]') with a worked example for one company so the deliverable is concrete rather than template-only.

Add an explicit validation step to the workflow, e.g. before Step 5 output, verify estimate sources/dates are cited and reconcile the options-implied move against the scenario ranges.

Provide a minimal fill-in example for the bull/base/bear table (sample revenue/EPS/driver/reaction values) to make the scenario framework immediately actionable.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it lists metrics (ARR, NIM, book-to-bill) without explaining what they are, and the 'Important Notes' add genuinely non-obvious context (whisper numbers, options-implied move) rather than padding, matching the score-3 'lean and efficient' anchor.

3 / 3

Actionability

Concrete sector-specific metric lists and a defined one-page output spec provide real guidance, but the scenario table has empty cells and the catalyst checklist uses bracketed placeholders ('[Metric] vs. [consensus/whisper number]'), leaving core deliverables template-only rather than copy-paste ready — closer to the score-2 'concrete but incomplete' than score-3.

2 / 3

Workflow Clarity

Five steps are clearly sequenced (Gather Context → Metrics Framework → Scenario Analysis → Catalyst Checklist → Output) and a checklist is present, but there are no validation/verification checkpoints — matching the score-2 'sequence present but checkpoints missing or implicit' rather than the score-3 'explicit validation steps' anchor.

2 / 3

Progressive Disclosure

The skill is self-contained (no references/scripts/assets bundle files exist) and well-organized into clearly headed sections with no nested references, so per the under-50-lines/simple-organization guidance the clean sectioning earns the score-3 rather than the monolithic-wall score-2.

3 / 3

Total

10

/

12

Passed

Description

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.

The description is strong across all dimensions: it states concrete capabilities, includes natural trigger phrasings, answers both what and when explicitly, and occupies a distinct niche. Third-person voice is used correctly.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Build pre-earnings analysis with estimate models, scenario frameworks', 'prepare positioning notes, set up bull/bear scenarios, and identify what will move the stock' — matching the score-3 anchor rather than the single-domain score-2 anchor.

3 / 3

Completeness

Explicitly answers both 'what' (build pre-earnings analysis with estimate models/scenario frameworks/key metrics) and 'when' ('Use before a company reports quarterly earnings' plus an explicit 'Triggers on' clause), matching the score-3 anchor.

3 / 3

Trigger Term Quality

Provides natural phrasings a user would actually say — 'earnings preview', 'what to watch for [company] earnings', 'pre-earnings', 'earnings setup', 'preview Q[X] for [company]' — giving good coverage of common variations rather than jargon.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (pre-earnings positioning) with earnings-specific triggers unlikely to fire for unrelated skills, matching the score-3 'clear niche with distinct triggers' anchor rather than the more generic score-2.

3 / 3

Total

12

/

12

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
anthropics/financial-services
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.