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]".

66

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/agent-plugins/earnings-reviewer/skills/earnings-preview/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 tight, actionable workflow that assumes financial literacy and gives concrete frameworks (metrics, scenarios, catalysts, output). It scores well on all dimensions with only minor gaps around validation checkpoints and reference organization.

Suggestions

Add an explicit verification checkpoint (e.g. 'confirm estimate source and date before drafting scenarios') to strengthen the workflow.

Consider moving the sector-specific operational-metric lists into a small reference file to keep the main body focused.

DimensionReasoningScore

Conciseness

Lean, bullet-driven body with no padding of concepts Claude already knows; every line is task-relevant, with only minor reference-style lists that could be marginally tightened.

4 / 5

Actionability

Concrete, specific guidance throughout (per-sector metric lists, a scenario table structure, a catalyst checklist template, a defined output spec), though web-search reliance means no literal executable code is offered.

4 / 5

Workflow Clarity

Five clearly sequenced steps from context gathering to a defined output; this is an analysis task rather than a destructive/batch op, so the missing hard validation checkpoint is only a minor gap.

4 / 5

Progressive Disclosure

Single, well-organized SKILL.md with clear section headers and no nested references; at ~70 lines it slightly exceeds the simple-skill threshold but is appropriately self-contained with no bundle files.

4 / 5

Total

16

/

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 well-constructed description that clearly states purpose, timing, and natural trigger phrases. It is specific and distinctive, with only minor gaps in action concreteness and trigger synonym coverage.

Suggestions

Add 1-2 concrete output artifacts (e.g. 'consensus estimates table', 'options-implied move') to raise specificity.

Include a couple more trigger synonyms users say (e.g. 'earnings prep', 'earnings run') for fuller trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ('estimate models, scenario frameworks, and key metrics to watch', 'prepare positioning notes, set up bull/bear scenarios'), but stays at a high level rather than naming concrete outputs like a consensus table or implied-move calculation.

4 / 5

Completeness

Explicitly answers both what ('Build pre-earnings analysis with estimate models, scenario frameworks, and key metrics') and when ('Use before a company reports quarterly earnings', plus a concrete 'Triggers on' clause).

5 / 5

Trigger Term Quality

Explicit natural triggers are provided ('earnings preview', 'pre-earnings', 'earnings setup', 'preview Q[X] for [company]') that users would realistically say, though a few common variants (e.g. 'earnings prep', 'earnings run') are absent.

4 / 5

Distinctiveness Conflict Risk

The pre-earnings niche is clearly bounded by distinct trigger phrases, with only minor overlap risk against broader financial-analysis skills.

4 / 5

Total

17

/

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