CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

industry-research

AI Berkshire skill: 行业投资研究:产业链全景扫描 + 四大师个股分析框架. Source: skills/industry-research.md.

Quality

71%

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/industry-research/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.

The body is a well-sequenced, highly actionable research workflow with explicit validation gates and a re-audit feedback loop. Its main weaknesses are progressive disclosure — everything is inlined in one long file with dangling references to non-bundled files — and minor over-explanation in the bias-awareness and adapter sections.

Suggestions

Move the detailed per-master analysis templates (第四步) and bias-awareness tables into reference files under references/ and link them from SKILL.md so the main file stays a lean overview.

Define the JSON schema for the report_audit.py verdict step's --results argument inline or in a bundled reference, since '<填好的JSON>' is currently not actionable.

Either bundle the referenced tools (tools/report_audit.py, tools/financial_rigor.py) and skills/financial-data.md or replace those references with self-contained instructions, as they are currently dangling paths.

DimensionReasoningScore

Conciseness

The body is directive throughout — step tables, scoring scales, and output templates rather than explanations of concepts Claude already knows — matching 'Efficient; minor instances of over-explanation that could be trimmed'. It is not level 5 because the 'AI研究偏见自觉' section and the Codex adapter note carry padding that could be tightened or moved to a reference file.

4 / 5

Actionability

Concrete executable commands are provided (`python3 tools/report_audit.py extract --report <报告文件路径>`, `date` for baseline) plus defined Tier 1-4 layers, ★1-5 rating scales, and filled-in output table templates, matching 'Mostly executable guidance; concrete code or commands with minor gaps'. Not level 5 because the audit `<填好的JSON>` results format is undefined and referenced files (tools/report_audit.py, skills/financial-data.md) are not present in the skill bundle.

4 / 5

Workflow Clarity

Eight explicitly numbered steps (第一步 through 第八步) each carry their own validation requirements — per-link logic-chain verification in 1.2, verification events in 1.3, risk checklists and bias self-checks in 第五步 — and the 数据抽检 exit process forms an explicit validate→fix→re-audit feedback loop ('【打回】 有不通过 → 修正后重审'), matching the 'clear sequence with explicit validation steps; feedback loops for error recovery' anchor.

5 / 5

Progressive Disclosure

The single file has clear section structure, but ~280 lines of content are fully inlined with no bundle files (references/, scripts/, assets/ are absent) while the body points to external paths (skills/industry-research.md, skills/financial-data.md, AGENTS.md, tools/*.py) that are neither clearly signaled nor available in the bundle, matching 'Some structure but could be better organized; references present but not clearly signaled'.

3 / 5

Total

16

/

20

Passed

Description

50%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 identifies a specific domain and framework but reads more like a title plus provenance note than a capability description. It lacks any 'Use when' trigger guidance, which caps completeness and weakens trigger-term quality. Rewriting it as a third-person capability statement with explicit trigger phrases would substantially improve it.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user asks for industry-chain investment research, a sector panorama scan, or four-master (Buffett/Munger/Duan/Li Lu) stock analysis of an industry.'

Replace meta-text ('AI Berkshire skill:', 'Source: skills/industry-research.md.') with concrete actions the skill performs: verify the investment logic chain, scan global listed companies by chain segment, and output portfolio allocation recommendations.

Include natural trigger synonyms users would say (行业分析, 板块研究, 产业链研究, 个股筛选) so the description surfaces for a wider range of phrasings.

DimensionReasoningScore

Specificity

The description names the domain ("行业投资研究") and 1-2 concrete framework components ("产业链全景扫描 + 四大师个股分析框架"), matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It is not level 2 because the two named components are more concrete than minimal/generic actions, and not level 4 because no further specific actions (verify logic chain, scan listed companies, output portfolio) are stated.

3 / 5

Completeness

It has a clear 'what' (industry investment research: supply-chain panorama scan plus four-master stock analysis framework) but no 'when / Use when...' clause or equivalent trigger guidance, so completeness is capped at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Relevant natural keywords are present ("行业", "投资研究", "产业链", "个股分析") but common variations and synonyms are missing, matching 'Some relevant keywords but missing common variations or synonyms'. Meta-text ("AI Berkshire skill:", "Source: skills/industry-research.md.") crowds out trigger terms rather than adding natural phrasing users would say.

3 / 5

Distinctiveness Conflict Risk

The combined framing (industry chain scanning plus four-master analysis) is fairly specific, but generic terms like "AI Berkshire skill" and "投资研究" would overlap with sibling value-investing/stock-analysis skills, matching 'Somewhat specific but could still overlap with similar skills'. Not level 4 because no distinct trigger phrase separates it from those related skills.

3 / 5

Total

12

/

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/industry-research/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.