CtrlK
BlogDocsLog inGet started
Tessl Logo

investment-research

AI Berkshire skill: 投资研究:巴菲特-芒格-段永平-李录 四大师综合分析框架. Source: skills/investment-research.md.

48

Quality

51%

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

Quality

Content

73%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 strongly actionable, well-sequenced research workflow with executable verification commands and real validation/feedback loops, scoring high on actionability and workflow clarity. Its weak point is progressive disclosure: a single long inlined file with no bundled reference scripts, so heavy reference material (data-source catalog, common-error catalog) is inlined rather than split into one-level-deep files.

Suggestions

Split the data-source catalog (the macrotrends/stockanalysis/aastocks/东方财富+巨潮资讯 table) and the '常见错误防范' list into a bundled `references/financial-data.md` and link to it, so the SKILL.md body stays a lean overview.

Bundle the invoked scripts as `scripts/financial_rigor.py` and `scripts/report_audit.py` (or a `scripts/` placeholder noting they live at repo root) so the referenced tool paths actually exist within the skill bundle.

Trim the repeated reinforcement lines ('必须通过工具验算' / '禁止心算' appears several times) to a single canonical statement per step to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly efficient instructional prose that assumes Claude's competence (it does not explain what a moat or DCF is), but the ~246-line length and repeated reinforcing lines (e.g. '必须通过工具验算', '禁止心算' restated several times) and the embedded full data-source catalog and common-error list add bulk that could be trimmed or moved to a reference.

3 / 5

Actionability

It provides concrete, copy-paste-ready shell commands with exact subcommands and flags for the key operations — `python3 tools/financial_rigor.py verify-market-cap --price ... --shares ...`, `cross-validate --field ... --values '{...}'`, `verify-valuation`, `three-scenario`, and `tools/report_audit.py extract|verdict` — covering the common cases fully and executably.

5 / 5

Workflow Clarity

The process is explicitly sequenced (前置步骤 → 第一步…第八步 → 输出要求 → 数据抽检) with mandatory validation checkpoints and explicit feedback loops: tool outputs must be embedded, a ❌ result blocks continuation, and the report-audit '打回 → 修正 → 重新抽检直到准出' loop is a textbook validate→fix→retry cycle for a batch/destructive operation.

5 / 5

Progressive Disclosure

All substantive content is inlined into one ~246-line file with no bundle directory (references/, scripts/, assets/ absent), and it references external paths (skills/financial-data.md, tools/financial_rigor.py, tools/report_audit.py, AGENTS.md) that are not bundled in the skill, so the data-source catalog and per-step details that belong in separate reference files are inlined rather than split.

2 / 5

Total

15

/

20

Passed

Description

28%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 names the analytical domain and its four-master framing but specifies no concrete actions and omits any 'Use when...' trigger guidance, capping completeness at 2. Trigger coverage is thin and first/second-person voice is not the main issue, but the meta 'AI Berkshire skill: … Source: skills/investment-research.md.' prefix is implementation metadata that does not help trigger the skill.

Suggestions

Rewrite in third person as concrete actions, e.g. '对个股进行四大师方法论的投资研究:收集并交叉验证财务数据、评估护城河与管理层、做三情景估值与安全边际、生成买入/观望/回避决策备忘录。'

Add an explicit 'Use when...' clause with natural triggers users would say: '当用户要求分析某只股票、估值、研究护城河、或做投资尽调时使用。'

Remove the implementation metadata prefix ('AI Berkshire skill: … Source: skills/investment-research.md.') from the description so it reads as a capability statement rather than a source citation.

DimensionReasoningScore

Specificity

The phrase '投资研究:巴菲特-芒格-段永平-李录 四大师综合分析框架' names the analytical domain and its four-master framework, but describes no concrete actions (collect, validate, value, audit) — only 'comprehensive analysis framework', leaving actions minimal and generic.

2 / 5

Completeness

It states a 'what' (a four-master analysis framework) but has no 'Use when...' trigger clause at all, so it answers only 'what' with a vague formulation and omits 'when' — matching the anchor for a vague 'what' and no 'when'.

2 / 5

Trigger Term Quality

It offers the single natural phrase '投资研究' (investment research) and the master names, but lacks the common variations users actually say (估值, 护城河, 安全边际, 财报分析, DCF) and any English synonyms, so most natural trigger terms are missing.

2 / 5

Distinctiveness Conflict Risk

The four-master framing (Buffett/Munger/Duan/Li) is a fairly specific niche unlikely to collide with unrelated skills, yet 'investment research / comprehensive analysis framework' is broad enough that it could overlap with other finance-analysis skills, so it sits between 'somewhat specific' and 'mostly distinct'.

3 / 5

Total

9

/

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.