CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

earnings-team

AI Berkshire skill: 财报精读团队:四大师并行解读 + 公众号发布. Source: skills/earnings-team.md.

Quality

74%

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

Quality

Content

81%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 dense, well-sequenced operating manual with concrete commands, templates, validation checkpoints, and a genuine re-audit feedback loop — its workflow clarity is exemplary. The main costs are length (≈450 lines in one file) and a few underspecified details, most notably the audit results JSON that the exit gate depends on.

Suggestions

Specify the JSON fields that report_audit.py verdict expects (or reference its schema/file) so the 准出 exit gate is actually executable rather than depending on the agent guessing.

Move the four agent analysis briefs (段永平/巴菲特/芒格/李录) and the editor/reader-review specs into reference files linked from SKILL.md, keeping the orchestration phases in the main file — this would cut the top-level file roughly in half.

Trim the '设计理念' section and add a fallback note for external paths (tools/, AGENTS.md) in case they are missing from the current checkout.

DimensionReasoningScore

Conciseness

Almost every section is task-specific instruction (agent briefs, output templates, tool commands) rather than concepts Claude already knows, but the '设计理念' rationale section and decorative master quotes are padding that could be trimmed — anchor 4, not the fully lean anchor 5.

4 / 5

Actionability

Highly concrete: executable financial_rigor.py commands with arguments, an exact output file tree, full markdown report/article templates, weighted review dimensions, and good/bad title examples. Falls short of anchor 5 because the report_audit.py step leaves '--results <填好的JSON>' undefined with no schema for its contents.

4 / 5

Workflow Clarity

Three phases are explicitly sequenced with parallel launches in one message, progress tracking, synthesis gated on all four reports, an edit→review→finalize loop, data-availability grading, and a 准出/打回 exit gate with re-audit after fixes — a complete validate→fix→retry feedback loop matching anchor 5.

5 / 5

Progressive Disclosure

The single file is well-sectioned with clear headers, and references (tools/financial_rigor.py, tools/report_audit.py) are one level deep with runnable paths. Minor gap: several referenced paths (tools/, skills/earnings-team.md, AGENTS.md) live outside the skill with no fallback if absent, and the long per-agent briefs could be split into reference files.

4 / 5

Total

17

/

20

Passed

Description

53%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 conveys a distinctive domain and a rough 'what' in very few words, but contains no trigger guidance and no enumeration of the concrete capabilities the skill actually delivers. The 'AI Berkshire skill:' prefix and source-file suffix are noise that dilute the signal.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for a deep team analysis of an earnings report (公司名 季度), or wants earnings analysis written up as a publishable WeChat article' — this would also lift the completeness cap.

Replace the 'AI Berkshire skill:' prefix and 'Source: skills/earnings-team.md.' suffix with 2-4 concrete actions (e.g. parallel four-perspective analysis, financial data cross-validation, reader-review quality gate, WeChat article publishing).

Include natural synonyms users would type (财报分析, 季报, 业绩, 电话会) so the skill triggers on real phrasings, and briefly differentiate it from /earnings-review and /investment-team.

DimensionReasoningScore

Specificity

Names the domain ('财报精读团队') plus two concrete actions ('四大师并行解读', '公众号发布'), matching the '1-2 concrete actions, not comprehensive' anchor; the 'AI Berkshire skill:' prefix and 'Source: skills/earnings-team.md.' suffix add no capability information.

3 / 5

Completeness

The 'what' is reasonably clear (team-based earnings deep-read producing a publishable WeChat article), but there is no 'Use when...' or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

'财报' and '公众号' are natural terms a user would say, but common variations and synonyms (季报, 业绩, 财报分析, 电话会) are absent, matching the 'some relevant keywords, missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The four-master team framing plus publishing pipeline carves a distinct niche, but it overlaps with closely related sibling skills (/earnings-review, /investment-team) that the description never disambiguates against.

4 / 5

Total

13

/

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