CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

earnings-review

AI Berkshire skill: 财报精读:一手资料深度解读. Source: skills/earnings-review.md.

Quality

69%

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 ./codex-skills/earnings-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a well-engineered, highly actionable workflow: concrete tool invocations, validation checkpoints with numeric thresholds, and a report-audit exit gate with a genuine fix-and-retry loop. Its weaknesses are the missing bundle structure — long reference-worthy material is inlined and cited external files are not part of the skill — and light motivational padding in the design-philosophy sections.

Suggestions

Move the stable detail tables (MD&A signal catalog 3.1, notes checklist 4.1/4.2, per-market data-source list in step 1) into a references/ file (e.g. references/signal-catalogs.md) and link them with clearly signaled one-level-deep pointers from SKILL.md, keeping the eight-step workflow as the overview.

Specify the JSON schema for `report_audit.py verdict --results` (required keys, expected value types) inline or in a reference file so the audit step's input is not an opaque '<填好的JSON>' placeholder.

Trim the '设计理念' section and the epigraph quotes to 2-3 lines total — the workflow already embodies the philosophy, and the rationale lines scattered through steps 2-3 can be cut without losing guidance value.

DimensionReasoningScore

Conciseness

The body is dense with tables, checklists, and parameterized commands that earn their tokens, but the '设计理念' motivation section, the Li Lu/Buffett epigraphs, and some rationale lines ('巴菲特最看重', '这是巴菲特和李录花最多时间的部分') are mild padding that could be trimmed, matching the 'efficient with minor over-explanation' anchor.

4 / 5

Actionability

Commands are copy-paste ready with full arguments ('python3 tools/financial_rigor.py cross-validate --metric "revenue" --values 108.3e9 107.9e9 ...'), report structure and output paths are concrete ('reports/{公司名}-earnings-{期间}.md'), and input formats are exemplified ('腾讯 2025Q4'); the main gap is the unverifiable '<填好的JSON>' placeholder in the audit verdict command, so it sits at 'mostly executable with minor gaps' rather than fully executable.

4 / 5

Workflow Clarity

Eight explicitly sequenced steps, an upfront material-availability grading table (A/B/C), cross-validation checkpoints with a concrete tolerance rule (two-source error >1% must be flagged), and a final audit exit gate with a pass/fail feedback loop ('【打回】有不通过 → 修正后重审') plus checkbox checklists — this matches the top anchor of clear sequence with explicit validation, error-recovery loops, and checklists.

5 / 5

Progressive Disclosure

The skill is a single monolithic file with no bundle (references/, scripts/, assets/ are absent), while its detailed MD&A signal tables, checklist items, and per-market data-source lists are inlined material that could live in reference files; external references (skills/financial-data.md, tools/*.py) sit outside the bundle and are not clearly signaled as one-level-deep navigation, matching the 'some structure but could be better organized' anchor.

3 / 5

Total

16

/

20

Passed

Description

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

The description is a terse bilingual title rather than a functional description: it identifies the domain but names no concrete actions, omits any 'when to use' trigger guidance, and includes metadata ('Source: skills/earnings-review.md') that adds no triggering value. It would benefit most from listing 2-3 concrete capabilities and an explicit use-when clause.

Suggestions

List concrete actions in third person, e.g. '深读公司季报/年报(10-K、港股披露、A股公告):提取并交叉验证收入/现金流/资产负债数据、精读管理层讨论与电话会、挖掘财报附注异常信号、输出精读报告' — this raises both specificity and completeness.

Add an explicit trigger clause such as 'Use when the user asks to 精读/分析 a specific company's 财报、季报、年报、earnings, or 业绩 (e.g. "腾讯 2025Q4")', which lifts completeness to a 4-5 and adds natural trigger-term variations.

Drop the 'Source: skills/earnings-review.md.' provenance note from the description — it consumes trigger-matching tokens without helping a user (or Claude) select this skill.

DimensionReasoningScore

Specificity

The phrase '财报精读:一手资料深度解读' names the domain (deep-reading earnings reports via primary sources) but lists no concrete actions like extracting cash-flow metrics or auditing management commentary, matching the anchor for naming the domain with minimal/generic actions rather than the 1-2 concrete actions needed for a 3.

2 / 5

Completeness

A recognizable 'what' exists (title-style: deep-read earnings reports from primary materials), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

'财报' and '精读' are natural terms a Chinese-speaking user would say, but common variations and synonyms (季报, 年报, 10-K, 电话会, earnings) are entirely absent, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'AI Berkshire skill: 财报精读' carves out a niche within an investing skill family, but the family label plus title-style naming could still overlap with sibling financial-analysis skills, matching the 'somewhat specific but could still overlap' anchor.

3 / 5

Total

11

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

xbtlin/ai-berkshire

Path

codex-skills/earnings-review/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.