CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

investment-checklist

AI Berkshire skill: 巴菲特价值投资买入前 Checklist. Source: skills/investment-checklist.md.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./codex-skills/investment-checklist/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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.

A strongly operational skill body: it converts Buffett/Munger principles into an executable, validated workflow with concrete tools, thresholds, and pass/fail gates. The main weaknesses are the absence of any bundle structure for a 250-line body and minor non-essential prose (the adapter note and anecdotes).

Suggestions

Move the per-gate rating criteria and data-collection lists into a references/ file (e.g. references/six-gates.md), keeping SKILL.md as an overview that signals each reference clearly.

Trim or relocate the 'Codex adapter note' section — it is environment meta-commentary, not checklist instruction, and costs ~10 lines of context on every invocation.

Bundle or verify tools/financial_rigor.py (or inline its expected CLI contract) so the two critical valuation commands are guaranteed executable rather than dependent on an external repo checkout.

DimensionReasoningScore

Conciseness

The body is dense and instruction-focused — threshold tables ("ROE>15%优秀", "有息负债/净利润<3年"), star-rating criteria, and a mirror-test template — with almost no explanation of concepts Claude already knows. Minor instances could be trimmed: the 10-line Codex adapter note and the 段永平 quote anecdote, which keeps it below the 'every token earns its place' anchor of 5.

4 / 5

Actionability

Mostly executable guidance: concrete commands with argument names ("python3 tools/financial_rigor.py verify-valuation --price {股价} --eps {EPS} --bvps {每股净资产} ..."), explicit data-collection lists, hard numeric criteria, and a fixed output path ("~/巴菲特Checklist-[公司名].md"). Minor gaps: brace placeholders must be filled in and the referenced tools/financial_rigor.py is not part of this skill's bundle, so the commands are not fully copy-paste ready.

4 / 5

Workflow Clarity

The sequence 第一步→第七步 is explicit with validation checkpoints throughout: A/B/C information-richness gating before analysis, hard-veto rules ("连赚钱方式都说不清,直接标记为不在能力圈"), mandated tool verification ("必须通过工具精确计算,禁止心算"), the mirror test as a pass/fail gate ("5句话说不完整 = 不买"), a quick-reject checklist, and forced explicit conclusions (✅/❌/❓/N/A). This matches the anchor 'clear sequence with explicit validation steps; feedback loops for error recovery; checklists for complex processes'.

5 / 5

Progressive Disclosure

The body has good internal structure (clear headings per gate) but is a ~250-line monolithic file with no bundle files at all — no references/, scripts/, or assets/ exist — and the six-gate detail plus the adapter note are inlined where reference files would serve better. It fits 'some structure; content that should be separate is inline'; it is not a 2 because sections are well-organized and nothing is buried, and not a 4+ because nothing is split out despite the length.

3 / 5

Total

16

/

20

Passed

Description

52%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 correctly identifies a distinctive niche but under-communicates it: no concrete capabilities, no 'Use when' trigger clause, and a wasted 'Source:' provenance fragment. It reads as a title plus metadata rather than a functional description for skill routing.

Suggestions

State concrete capabilities in third person, e.g. "对拟买入公司执行巴菲特式六关检查(能力圈、生意质量、护城河、管理层、安全边际、仓位纪律),输出星级评分与对比总览表".

Add an explicit trigger clause: "Use when the user asks about buying a stock, wants a Buffett-style pre-purchase check, or mentions 巴菲特/价值投资/安全边际 before buying.".

Remove the "Source: skills/investment-checklist.md" provenance line (or move it into the body) and replace jargon like "AI Berkshire skill" with plain capability language.

DimensionReasoningScore

Specificity

The description names the domain ("巴菲特价值投资买入前 Checklist") but lists no concrete actions or capabilities, and "Source: skills/investment-checklist.md" is provenance metadata rather than a capability — matching the anchor 'Names the domain but actions are minimal or generic' (cf. "Processes PDF files"). It is not a 3 because it never states even 1-2 concrete actions like 'evaluates companies against a six-gate checklist' or 'screens stocks before purchase'.

2 / 5

Completeness

There is a recognizable 'what' (a Buffett value-investing pre-buy checklist), but the 'when' is entirely absent — no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. Not a 2 because the 'what' is clear and domain-specific rather than vague.

3 / 5

Trigger Term Quality

It includes some natural keywords a user would say (巴菲特, 价值投资, 买入, Checklist) but misses common variations and synonyms (巴菲特 checklist, Buffett, 价值股, 股票筛选, pre-purchase screening), and "AI Berkshire skill" is internal jargon. Not a 4 because keyword coverage is thin relative to the natural phrase space for this domain.

3 / 5

Distinctiveness Conflict Risk

The Buffett value-investing pre-buy checklist occupies a clear niche with distinct trigger terms (巴菲特/价值投资/买入前), making it unlikely to fire for the wrong skill. Not a 4 because no plausible overlap with a closely related skill is identifiable from the description itself.

5 / 5

Total

13

/

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/investment-checklist/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.