CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

59

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 reference for earnings revision analysis with concrete thresholds, decision rules, and a clear pre/post-event workflow. The main weaknesses are formula-style pseudocode rather than executable snippets, and a monolithic single-file structure where a skill of this size would benefit from split reference files.

Suggestions

Move the detailed lookup tables (guidance language patterns, earnings quality red flags, US/HK differences) into references/ files (e.g., references/guidance-language.md, references/earnings-quality.md) and keep SKILL.md as an overview with clearly signaled links.

Make the code blocks executable: complete `score_guidance_change` with an explicit return value and turn the SUE/breadth formulas into runnable functions or a small analysis script in scripts/.

Add explicit validation checkpoints to the workflow for data availability (e.g., what to do when real-time consensus data is unavailable) with a fallback path.

DimensionReasoningScore

Conciseness

The body is dense and high-signal — tables, formula blocks with interpretation thresholds, and checklists rather than padded prose, and it largely assumes financial-domain competence. Minor trimming opportunities exist, e.g., the "most robust anomaly in equity markets" framing sentence and repeated interpretation commentary that could be compressed. Not a 5 because a few explanatory asides restate well-known concepts.

4 / 5

Actionability

Most guidance is concrete and immediately usable: exact formulas with decision thresholds (SUE > +2, breadth > +0.5, dispersion > 15%), a structured guidance-scoring function, specific API calls (`ticker.earnings_dates`, `yf.Ticker("0700.HK").financials`), and a full output template. It stops short of a 5 because the Python blocks are formula-style rather than fully executable — e.g., `score_guidance_change` never returns a value and SUE variables are undefined placeholders.

4 / 5

Workflow Clarity

The pre-earnings and post-earnings checklists give a clear, well-ordered sequence from consensus snapshot through price/volume reaction, feeding directly into the output format. Minor gaps only: no explicit checkpoints for confirming data availability or handling missing consensus/guidance data. Not a 5 because there are no validation/feedback loops (e.g., what to do when yfinance lacks consensus data), though this is an analysis skill rather than a destructive or batch operation.

4 / 5

Progressive Disclosure

Section headers and tables give the ~230-line body reasonable internal structure, but everything is inlined in SKILL.md with no bundle files (references/, scripts/, assets/ do not exist). Self-contained reference material — guidance language patterns, earnings quality red flags, the US/HK comparison table — clearly belongs in separate reference files at this size, so it matches the "some structure but content that should be separate is inline" anchor rather than the well-split anchor 4.

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 well-scoped, domain-specific description with multiple concrete actions and good natural trigger terms. Its main weakness is the missing explicit "when to use" clause, which caps completeness, plus a few absent common synonyms (earnings season, beat/miss, analyst upgrades/downgrades).

Suggestions

Add an explicit trigger clause, e.g., "Use when analyzing earnings reports, estimate revisions, guidance changes, or post-earnings price reactions for US or Hong Kong listed stocks."

Include additional natural trigger terms users would actually say: "earnings season", "beat/miss", "analyst upgrades/downgrades", "earnings call reaction".

Optionally mention earnings quality / red-flag analysis to round out coverage of what the skill body actually delivers.

DimensionReasoningScore

Specificity

The description names several specific concrete actions — "track analyst consensus changes, earnings surprise patterns, and management guidance shifts for US/HK equities" — covering the skill's main facets. It falls short of a 5 because capabilities detailed in the body (earnings quality red flags, PEAD trading rules, output formats) are not represented, leaving minor gaps in coverage.

4 / 5

Completeness

The "what" is clear and concrete (tracking revisions, surprises, and guidance shifts), but there is no "Use when..." clause or equivalent explicit trigger guidance — the rubric explicitly caps completeness at 3 in that case. It is not a 2 because the "what" is genuinely clear rather than vague.

3 / 5

Trigger Term Quality

Good keyword coverage with natural terms users would say: "earnings estimate revisions", "guidance analysis", "earnings surprise", "analyst consensus", "PEAD", "US/HK equities". A few natural variations are missing — e.g., "earnings season", "beat/miss", "analyst upgrades/downgrades", "earnings call" — so it does not reach comprehensive synonym-level coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche (earnings revision / PEAD analysis for US/HK equities) with distinctive triggers like "post-earnings drift (PEAD)" and "management guidance shifts". Minor overlap risk remains with closely related finance skills (general equity analysis, valuation, macro commentary) that could also fire on phrases like "earnings" or "equities".

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