CtrlK
BlogDocsLog inGet started
Tessl Logo

earnings-forecast

盈利预测与一致预期分析(自上而下/自下而上预测法/SUE/PEAD/分析师预期修正),捕捉业绩超预期交易机会。

62

Quality

73%

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-forecast/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

Highly actionable with concrete A-share-specific formulas and thresholds, but it is a dense monolithic file that would benefit from tighter prose, explicit validation checkpoints in the trading workflow, and offloading reference material to bundled files.

Suggestions

Add explicit validation checkpoints into the four-step workflow (e.g. confirm ≥8 quarters of forecast-error history before computing SUE; confirm analyst coverage ≥3 before trusting consensus; strip 非经常性损益 before EPS comparison).

Move the 财报日历 table and detailed SUE/ERM threshold tables into reference files (e.g. references/calendar.md, references/thresholds.md) and link from the overview to improve progressive disclosure.

Trim conceptual prose that restates broadly known ideas (e.g. why expectation gaps matter, basic margin drivers) to improve token efficiency.

DimensionReasoningScore

Conciseness

Mostly efficient with genuinely value-adding A-share-specific thresholds and formulas, but it includes conceptual filler Claude largely knows ('股价短期由盈利预期差驱动…') and re-stated basics that could be tightened.

2 / 3

Actionability

Provides fully executable formula/code blocks (SUE, ERM, dispersion, portfolio config) with concrete numeric thresholds and a copy-paste-ready output template rather than pseudocode.

3 / 3

Workflow Clarity

The '盈利分析四步法' gives a clear sequence, but batch trading workflows lack explicit validation checkpoints (e.g. verify ≥8 quarters of history, analyst coverage ≥3, 扣非EPS adjustments) wired into the flow, capping clarity at 2.

2 / 3

Progressive Disclosure

Well-labeled sections and no broken/nested references, but the ~194-line monolithic body inlines threshold tables, the 财报日历, and detailed methodology that a more progressive design would offload to reference files.

2 / 3

Total

9

/

12

Passed

Description

82%

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-anchored description with good natural trigger terms and a distinct niche, held back only by the absence of an explicit 'when to use' clause.

Suggestions

Add an explicit trigger clause, e.g. 'Use when 分析公司盈利超预期、构建一致预期偏差交易信号、或跟踪分析师预期修正时'.

Consider adding a couple of broader user-facing phrasings like '财报分析' or '业绩分析' to widen trigger coverage.

DimensionReasoningScore

Specificity

Names multiple concrete capabilities — '自上而下/自下而上预测法/SUE/PEAD/分析师预期修正' — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly states what the skill does, but lacks an explicit 'Use when...' or equivalent trigger guidance; per the judging guidelines a missing explicit trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

Includes natural terms a practitioner would say — '盈利预测', '一致预期', '业绩超预期', '分析师预期修正' — alongside the technical acronyms SUE/PEAD, giving good coverage of likely user phrasings.

3 / 3

Distinctiveness Conflict Risk

The SUE/PEAD/consensus-expectation framing carves out a clear niche within analysis skills that is unlikely to trigger for unrelated skills.

3 / 3

Total

11

/

12

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.

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