CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

earnings-revision

Earnings estimate revisions, guidance analysis, and post-earnings drift (PEAD) — track analyst consensus changes, earnings surprise patterns, and management guidance shifts for US/HK equities.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./agent/src/skills/earnings-revision/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 strong, information-dense body that provides genuinely non-obvious domain heuristics, concrete formulas with thresholds, and a clear pre/post-earnings workflow. Its main gap is the single-file structure — at ~230 lines, the detailed reference tables could be split into one-level-deep reference files — and code snippets that are illustrative rather than fully executable.

Suggestions

Split detailed reference material (multi-market considerations, guidance-language patterns, earnings-quality indicators) into one-level-deep files under references/ and keep SKILL.md as an overview with clearly signaled links.

Make the code snippets executable: give score_guidance_change a return value and define the input structures, or convert the pseudocode formulas into runnable Python functions.

Add a data-availability checkpoint to the workflow (e.g., what to do when real-time consensus is unavailable, since the Notes concede yfinance lacks it).

DimensionReasoningScore

Conciseness

The body is dense with non-obvious domain content — signal hierarchy tables, SUE/breadth/dispersion thresholds, PEAD quintile drifts, guidance-language interpretation — with only minor over-explanation (the Overview rationale paragraph, the PEAD intro sentence, and some 'Interpretation' comments) that could be trimmed. It is not a 5 because a few passages restate knowledge Claude already has about earnings revisions and PEAD.

4 / 5

Actionability

Concrete, mostly executable guidance throughout: SUE/breadth/dispersion formulas with numeric thresholds, a guidance-scoring function, yfinance API calls ('ticker.earnings_dates', 'ticker.earnings_history'), and a full output template. Not a 5 because the code snippets are illustrative rather than copy-paste ready — 'score_guidance_change' references undefined structures (current_guide.midpoint) and returns nothing, and the metric formulas are pseudocode.

4 / 5

Workflow Clarity

The Pre-Earnings and Post-Earnings Analysis Checklists give a clear six-step sequence with a defined output format, and the Notes section flags pitfalls. Not a 5 because there are no explicit validation checkpoints or data-availability feedback loops (e.g., what to do when consensus data is missing); it is above 3 since the sequences are complete and this is read-only analysis, so the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

The ~230-line body is monolithic with no bundle files (no references/, scripts/, or assets/ exist) and no external references at all; sections are well-organized with clear headers, but content that could live in separate reference files (multi-market considerations, guidance-language patterns, earnings-quality red flags) is fully inlined. This sits between the 2 anchor (inlined content that belongs in separate files) and the 4 anchor (appropriately split), matching the 3 anchor's 'some structure but could be better organized'.

3 / 5

Total

15

/

20

Passed

Description

66%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 specific, well-scoped description that clearly communicates a niche analytics capability with good natural trigger terms. Its main weakness is the absence of any 'Use when...' trigger guidance, which caps completeness and slightly limits discoverability.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user asks about analyst estimates, earnings surprises, guidance changes, or post-earnings drift for US or Hong Kong listed stocks.'

Include common user phrasings like 'beat/miss', 'analyst upgrades/downgrades', or 'earnings report reaction' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description lists several concrete, domain-scoped actions — 'track analyst consensus changes, earnings surprise patterns, and management guidance shifts for US/HK equities' — going beyond naming the domain. It falls short of the 5 anchor's comprehensive multi-action coverage since 'track' patterns are the only verb forms and coverage of the workflow (e.g., pre/post-earnings analysis) is not fully enumerated.

4 / 5

Completeness

It has a clear 'what' (tracking revisions, surprises, and guidance shifts) but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 4 because the 'when' is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

Good keyword coverage with natural terms users would say — 'earnings', 'estimate revisions', 'guidance', 'analyst consensus', 'earnings surprise', 'PEAD' — plus market scope 'US/HK equities'. A few natural synonyms are missing (e.g., 'beat/miss', 'analyst upgrades/downgrades', 'earnings report'), keeping it below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The earnings-revision/PEAD niche with explicit US/HK equity scope is mostly distinct with clear triggers, though it could minimally overlap with broader fundamental-analysis or equity-research skills. Not a 5 because adjacent skills (e.g., general equity analysis or earnings-call summarization) share some trigger territory.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

HKUDS/Vibe-Trading

Path

agent/src/skills/earnings-revision/SKILL.md

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.