CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

financial-data

AI Berkshire skill: 财务数据获取与交叉验证规范. Source: skills/financial-data.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/financial-data/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 strong, executable reference: concrete sources per market with priorities and access methods, a precise cross-validation workflow with error bands and escalation, price-adjustment rules, and a quick index. Its weaknesses are minor — the adapter-note preamble and unbundled tool references — and do not impede following the workflow.

DimensionReasoningScore

Conciseness

The body is dense with operational knowledge Claude cannot already know (source URLs, priority order, error bands, adjustment rules) presented as compact tables, with only minor over-explanation: the "Codex adapter note" section is adapter meta-content and some parenthetical asides could be trimmed. This matches anchor 4 rather than 5, and is clearly above anchor 3 since almost nothing here is boilerplate.

4 / 5

Actionability

Commands are copy-paste ready ("python3 tools/twstock_data.py quote 2330", "python3 tools/financial_rigor.py verify-market-cap") with exact URLs, an explicit error-rate formula, numeric thresholds, and worked output-format examples for both consistent and divergent data. It falls short of 5 because the referenced tools/ are not part of the skill bundle, so execution depends on locating the repo checkout.

4 / 5

Workflow Clarity

The 执行规范 section gives a clear three-step sequence (fetch from two sources → compute and mark error → present in a fixed format) with explicit checkpoints: error bands map to defined actions (≤1% accept and cite both sources, 1–5% flag with likely causes, >5% escalate to original filings and forbid direct use), plus edge-case rules for unlisted companies, quarterly vs annual data, and conflicts with primary filings. This matches the anchor with explicit validation and error-recovery escalation.

5 / 5

Progressive Disclosure

No bundle files exist, and the ~150-line body is well sectioned with a quick index; references to tools/twstock_data.py, skills/financial-data.md, and AGENTS.md are one level deep and clearly signaled. It is not 5 because the skill exceeds the simple <50-line case and inlines content that could be split (per-market source tables), and the referenced scripts are not bundled.

4 / 5

Total

17

/

20

Passed

Description

42%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 title-style label: it names the domain and a couple of actions but includes no 'Use when' trigger guidance, few natural keywords, and meta-noise ("AI Berkshire skill", "Source: skills/financial-data.md") that adds no triggering value. It is functional for a human browsing the repo but weak as an automatic skill trigger.

Suggestions

Add an explicit trigger clause, e.g. "Use when researching company financials (revenue, net profit, margins), fetching financial data across US/HK/A-share/Taiwan markets, or cross-validating figures from macrotrends/stockanalysis/EDGAR."

List the concrete capabilities as third-person actions (fetches financials from named sources per market, computes cross-source error rates, flags discrepancies >1%, normalizes price/adjustment bases) instead of a single title phrase.

Remove the provenance line "Source: skills/financial-data.md" and the "AI Berkshire skill" prefix from the description; they consume tokens without helping discovery or triggering.

DimensionReasoningScore

Specificity

The phrase "财务数据获取与交叉验证规范" names the domain (financial data) and two actions (acquisition, cross-validation), but as a title rather than an action list, and coverage is not comprehensive. It is not 4 because no list of several specific actions is given, and not 2 because the domain is named with real actions rather than generic language.

3 / 5

Completeness

A 'what' is present (financial data acquisition and cross-validation specification) but a 'when' is entirely missing, and the rubric guideline caps completeness at 3 in that case. It is not 2 because the 'what' is reasonably clear, not vague.

3 / 5

Trigger Term Quality

Only "财务数据" and "交叉验证" serve as keywords; the natural phrases a user would actually say (e.g. 财报, 营收, 净利润, financial data, earnings) are absent, as are synonyms and any equivalent of a trigger phrase. This matches anchor 2 (one or two generic keywords, missing the natural phrases users say).

2 / 5

Distinctiveness Conflict Risk

Cross-validation of financial data is a fairly specific niche, but "财务数据获取" broadly overlaps sibling financial-research skills (the body itself references earnings-review and thesis-tracker style analyses), so overlap risk remains. It is not 4 because nothing distinguishes it from those closely related skills.

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/financial-data/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.