CtrlK
BlogDocsLog inGet started
Tessl Logo

financial-data

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

57

Quality

65%

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

82%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 lean, highly actionable financial-data spec with concrete source tables, executable commands, explicit error thresholds, and a clear three-step workflow with validation gates. Its main weakness is that all reference material is inlined in one file with no bundle files for deeper navigation.

DimensionReasoningScore

Conciseness

The body is dense and information-rich with no padding of concepts Claude already knows; nearly every section earns its place with URLs, commands, or thresholds, with only minor explanatory asides in the '常见差异原因' table.

4 / 5

Actionability

It provides copy-paste-ready commands (e.g. 'python3 tools/twstock_data.py quote 2330'), concrete URL templates with ticker substitution, an explicit error formula, and an output-format template covering common cases.

5 / 5

Workflow Clarity

The 第一步/第二步/第三步 sequence is clear and the error-threshold table provides explicit validation gates (≤1% accept, 1-5% flag, >5% must re-verify against原始财报), though the re-validation feedback loop is somewhat implicit rather than a spelled-out fix-and-retry cycle.

4 / 5

Progressive Disclosure

Content is well-organized under clear section headers with a 快速索引 navigation table, and tool references (tools/twstock_data.py, financial_rigor.py) are one level deep and clearly signaled; minor gaps as everything lives in a single ~168-line file.

4 / 5

Total

17

/

20

Passed

Description

48%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 essentially a domain title plus a source pointer: it conveys the niche but provides no concrete actions and no explicit trigger guidance. It is distinct but thin on what/when completeness.

Suggestions

Add concrete actions, e.g. 'Fetches financial data from two independent sources and flags discrepancies >1%'.

Add an explicit 'Use when...' trigger clause such as 'Use when researching company financials or when the user asks for revenue, profit, or valuation figures'.

Drop the internal 'Source: skills/financial-data.md' metadata from the user-facing description.

DimensionReasoningScore

Specificity

The description names the domain ("财务数据获取与交叉验证规范") but lists no concrete actions, and the trailing "Source: skills/financial-data.md" is metadata rather than capability detail, matching the anchor 'Names the domain but actions are minimal or generic'.

2 / 5

Completeness

A 'what' is present via the spec title, but there is no 'Use when...' or equivalent trigger clause, so per the judging guidelines completeness is capped at 3 ('clear what, missing when').

3 / 5

Trigger Term Quality

Domain terms like "财务数据" and "交叉验证" are relevant keywords a user might say, but they are framed as a formal spec title rather than natural trigger phrasing, and common variations/synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

The financial-data cross-validation niche is specific and unlikely to trigger for unrelated skills, with only minor overlap risk against other finance skills.

4 / 5

Total

12

/

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.

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.