CtrlK
BlogDocsLog inGet started
Tessl Logo

investment-research

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

59

Quality

67%

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

77%

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, highly actionable multi-step research workflow with executable tooling and robust validation/audit feedback loops, held back mainly by verbosity and meta-overhead and by reliance on out-of-bundle references instead of bundled detail files.

DimensionReasoningScore

Conciseness

The content is mostly specialized investment-research methodology Claude would not inherently produce in this form (four-masters framing, rigor gates), but it carries meta-overhead (the Codex adapter note), repeated data-source listings, and verbose bias tables that could be tightened, so it is not fully lean.

2 / 3

Actionability

It provides concrete, parameterized executable commands — e.g. `python3 tools/financial_rigor.py verify-market-cap --price {股价} --shares {总股本} --reported {报告市值}`, plus cross-validate, verify-valuation, three-scenario, and report_audit subcommands — that are copy-paste ready once placeholders are filled.

3 / 3

Workflow Clarity

A clearly sequenced 前置步骤 + seven-step process is reinforced with explicit validation checkpoints and feedback loops ("如果工具报告 ❌ 偏差过大,必须排查原因后才能继续分析" and the 数据抽检 准出/打回 retry loop), matching the validate→fix→retry pattern.

3 / 3

Progressive Disclosure

Sections are well-organized and a detail spec is signaled one level deep ("> 数据源规范:参见 skills/financial-data.md"), but no bundle files exist and referenced paths (skills/financial-data.md, tools/) point outside the skill, so the structure is monolithic rather than a clean in-bundle progressive disclosure.

2 / 3

Total

10

/

12

Passed

Description

57%

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 identifies a distinctive niche but reads as a labeled framework title padded with generation metadata rather than a capability statement, omitting concrete actions and any explicit trigger guidance.

Suggestions

Rewrite in third-person action voice stating what the skill does, e.g. "Conducts systematic investment research on a company using the Buffett-Munger-Duan Yongping-Li Lu framework across moat, management, valuation, and risk."

Add an explicit trigger clause such as "Use when the user asks for fundamental investment analysis, company valuation, or research using the four-masters framework."

Remove the non-functional padding ("AI Berkshire skill:" and "Source: skills/investment-research.md.") so the description is concise and trigger-focused.

DimensionReasoningScore

Specificity

The description names a specific domain — "投资研究:巴菲特-芒格-段永平-李录 四大师综合分析框架" (four-masters investment research framework) — but states no concrete actions (no verbs like "evaluates" or "values"), so it sits above the vague "Helps with documents" anchor yet below the multi-action anchor.

2 / 3

Completeness

It offers a recognizable but weak "what" (a framework label, not actions) and entirely lacks a "when"/"Use when..." clause, so per the cap-at-2 guideline it lands at 2 rather than 1 because a domain "what" is present.

2 / 3

Trigger Term Quality

Relevant natural keywords are present ("投资研究" and the four masters' names), but coverage is missing common variations (估值, 护城河, 估值分析) and the field is cluttered with non-trigger meta text ("AI Berkshire skill:", "Source: skills/investment-research.md.").

2 / 3

Distinctiveness Conflict Risk

Naming four specific investment masters carves out a clear, narrow niche that is unlikely to trigger for unrelated skills; the "Source:" padding is noise but does not raise conflict risk.

3 / 3

Total

9

/

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.