CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bottleneck-hunter

AI Berkshire skill: 供应链瓶颈猎手:AI驱动的全球产业链瓶颈套利. Source: skills/bottleneck-hunter.md.

Quality

59%

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/bottleneck-hunter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 workflow itself is excellent: a well-sequenced seven-step process with explicit validation gates, numeric screening criteria, and concrete output templates. Weaknesses are structural rather than substantive — the skill is a long monolith with duplicated valuation rules and report templates that belong in separate reference files, and a couple of key computations are specified as rules without a concrete method.

Suggestions

Split the two report templates (§每小时扫描模式) and the hourly-scan operating mode into a references/ file (e.g. references/hourly-scan.md) and keep only a one-line pointer in SKILL.md, reducing the inline body substantially.

State the valuation rules once (§4.2.1) and reference them from §6.1's signal-strength table and core principle #8 instead of restating them three times.

Make the 10-year / 25x-PE exit-return check concrete: give the exact formula or a small worked example (inputs → required net income → implied revenue multiple → annualized return) so the mandatory check is reproducible.

DimensionReasoningScore

Conciseness

The body is dense and assumes domain competence (criteria tables, thresholds, templates rather than concept explanations), but there is real duplication: valuation rules appear in §4.2.1, again in the signal-strength ratings (§6.1), and again as core principle #8; output requirements are stated in both 第六步 and 每小时扫描模式, which also carries two near-parallel report templates. Fits 'mostly efficient but could be tightened', not 4.

3 / 5

Actionability

Highly executable guidance: copy-paste search strings ('{趋势} supply chain bottleneck 2026', 'sole source supplier'), numeric gates (PS > 30x, market cap > 20% of TAM, bottleneck revenue > 30%), fill-in output templates, file-naming rules, and an explicit tool command (python3 tools/twstock_data.py). Scored 4 rather than 5 because a few key computations (e.g. the 10-year / 25x-PE annualized-return check) are described conceptually but never given a concrete method or worked example.

4 / 5

Workflow Clarity

Seven explicitly sequenced steps each with a defined output artifact, and validation is explicit rather than implied: trend confirmation requires ≥3 dated sourced events, the valuation check is marked '必须执行,不可跳过', reverse (Munger-style) verification is mandatory, risk checklists are provided, and the incremental-update step re-checks prior bottlenecks — a genuine feedback loop. Matches anchor 5 (clear sequence, explicit validation steps, checklists, feedback loops).

5 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, assets/), so everything lives inline in one ~490-line SKILL.md. Internal sectioning is good, but content that clearly belongs in separate reference files — the two full report templates, the hourly-scan mode, the per-trend teardown templates — is inlined, and the referenced external paths (tools/financial_rigor.py, skills/financial-data.md, AGENTS.md, CLAUDE.md) are not part of this bundle. Fits anchor 3: some structure, but content that should be separate is inline.

3 / 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 reads as a generated title plus provenance metadata rather than a functional description: it names the domain but states no concrete capabilities and provides no 'use when' trigger guidance. The 'Source: skills/bottleneck-hunter.md' fragment is bookkeeping noise that further dilutes it.

Suggestions

Rewrite the description to list concrete actions in third person, e.g. 'Scans a confirmed super-trend's physical supply chain, identifies 2nd/3rd-layer bottlenecks, screens and valuation-checks listed suppliers, and maintains a ranked bottleneck opportunity board with Chinese-language reports.'

Add an explicit trigger clause with natural user phrases in both languages, e.g. 'Use when the user asks about supply chain bottlenecks, shortages, 缺货/产能瓶颈, or wants arbitrage targets behind a super-trend (AI infrastructure, energy transition, defense).' (A missing 'Use when' clause currently caps completeness at 3; here completeness scores 2.)

Remove the 'Source: skills/bottleneck-hunter.md' provenance note from the description — it consumes the description budget without describing capability or triggering.

DimensionReasoningScore

Specificity

"AI驱动的全球产业链瓶颈套利" names the domain but lists no concrete actions (no scanning, ranking, validation, or reporting verbs), matching the anchor 'Names the domain but actions are minimal or generic'. Not 3, because no specific capability is stated; not 1, because the domain is genuinely named.

2 / 5

Completeness

The 'what' is only a vague title-style claim and there is no 'when' / 'Use when...' clause at all (the guidelines cap completeness at 3 for a missing trigger clause, and this is below that). Matches anchor 2: 'Has a vague what and no when'; not 1 because the domain is still identifiable.

2 / 5

Trigger Term Quality

The description is a Chinese title (供应链瓶颈猎手 / 套利) plus a source pointer; it lacks the natural phrases a user would say when needing this skill (e.g. 'supply chain', 'shortage', 'bottleneck stock', '产能瓶颈') and no synonyms or trigger variations. Fits 'one or two generic keywords; missing the natural phrases users say'.

2 / 5

Distinctiveness Conflict Risk

The niche (supply-chain bottleneck arbitrage) is somewhat specific and distinct from generic document/code skills, but the description carries no trigger guidance and would plausibly overlap with other investing/research skills in the same suite. Sits between anchors 3 and 4.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

xbtlin/ai-berkshire

Path

codex-skills/bottleneck-hunter/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.