CtrlK
BlogDocsLog inGet started
Tessl Logo

financial-data

AI Berkshire skill: 财务数据获取与交叉验证规范. Source: skills/financial-data.md.

61

Quality

71%

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

Quality

Content

92%

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 high-quality, dense research spec: executable tooling, exact cross-validation thresholds, a sequenced three-step workflow with feedback loops, and good section organization plus a quick index. Its only structural weakness is that it is a monolithic single file relying on external repo tools rather than a split, progressive-disclosure bundle.

DimensionReasoningScore

Conciseness

The body is dense and token-efficient — compact tables for data sources, thresholds, and a quick index, plus copy-ready commands — with no padding explaining concepts Claude already knows; the only prose (the Codex adapter note) is actionable adapter instruction that earns its tokens, matching the 'lean, every token earns its place' anchor.

3 / 3

Actionability

It provides fully executable commands ('python3 tools/twstock_data.py quote 2330'), concrete URL templates, an exact error formula, and explicit threshold bands (≤1% / 1%-5% / >5%) with prescribed actions, reaching the copy-paste-ready level 3 rather than the pseudocode or partial level 2.

3 / 3

Workflow Clarity

The '执行规范' section sequences 第一步/第二步/第三步 with a built-in cross-validation feedback loop (>5% discrepancy forces re-checking the original filing) and the price-adjustment rules add explicit checkpoints, matching the 'clear sequence with explicit validation steps and error-recovery loops' anchor.

3 / 3

Progressive Disclosure

Sections are well-organized with a 快速索引 navigation table and one-level-deep, clearly-signaled references to external repo files (tools/*.py, AGENTS.md), but the skill is a single monolithic file over 50 lines with no bundle reference files to split into, so the 'content appropriately split across files' bar for level 3 is not met.

2 / 3

Total

11

/

12

Passed

Description

50%

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 essentially a Chinese title plus internal source metadata rather than a proper skill description: it states a domain and two actions but provides no 'Use when' trigger guidance and is padded with non-user-facing branding. It is adequate but not strong, sitting at the middle anchor on every dimension.

Suggestions

Rewrite the description in third person to lead with concrete actions, e.g. 'Acquires and cross-validates corporate financial data across US/HK/A/TW markets...', and drop the 'AI Berkshire skill:' branding and 'Source: skills/financial-data.md.' metadata.

Add an explicit trigger clause such as 'Use when the user requests financial figures (revenue, net income, margins, EPS), needs numbers verified against two sources, or asks about PDD/腾讯/网易/台积电 etc.'

Include natural keyword variations users would actually say (financial data, earnings, cross-check numbers, stock fundamentals) to raise trigger-term coverage.

DimensionReasoningScore

Specificity

The phrase '财务数据获取与交叉验证规范' names the domain (financial data) and two actions (acquisition, cross-validation), but does not enumerate multiple concrete capabilities, so it sits at 'names domain and some actions, not comprehensive' rather than the multi-action level 3.

2 / 3

Completeness

It weakly states 'what' (financial data acquisition and cross-validation) but has no 'Use when...' or equivalent trigger guidance, and the judging guidelines explicitly cap completeness at 2 when such a clause is missing, keeping it below the explicit-both level 3 and above the missing-everything level 1.

2 / 3

Trigger Term Quality

'财务数据' and '交叉验证' are relevant keywords a user might say, but the description is cluttered with non-trigger branding ('AI Berkshire skill', 'Source: skills/financial-data.md') and the jargon term '规范', missing common natural variations, so it is not the sparse-jargon level 1 nor the well-covered level 3.

2 / 3

Distinctiveness Conflict Risk

The cross-validation niche is somewhat distinctive, but the description reads as a generic specification title rather than a set of distinct triggers, so it could still overlap with general financial-analysis skills and does not reach the clear-distinct-niche level 3.

2 / 3

Total

8

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
xbtlin/ai-berkshire
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.