CtrlK
BlogDocsLog inGet started
Tessl Logo

investment-team

AI Berkshire skill: 投研团队:四角色并行分析框架. Source: skills/investment-team.md.

56

Quality

63%

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-team/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 content is a strong, actionable multi-agent workflow with concrete commands, explicit tool configuration, and a genuine validation/feedback gate in the audit step. Its main weaknesses are minor redundancy/editorializing and a monolithic single-file structure whose external references are not bundled alongside it.

Suggestions

Tighten the "AI研究偏见评估" section to operational rules only and remove points in "重要注意事项" that already appear in the numbered steps (e.g. the parallel-launch and SendMessage reminders) to reduce redundancy.

Consider moving the detailed financial-data source rules and the agent prompt template into a bundled reference file (e.g. references/financial-data.md) referenced one level deep, so SKILL.md reads as a tighter overview with real progressive disclosure.

Since referenced tools (tools/financial_rigor.py, tools/report_audit.py) are not bundled here, add a one-line note on where to obtain them or confirm they exist in the host repo, so the commands are guaranteed executable.

DimensionReasoningScore

Conciseness

The body is mostly procedural and efficient (tables, commands, prompt templates), but the "AI研究偏见评估" section editorializes concepts and "重要注意事项" re-states points already covered in the steps, so it could be tightened; it is not the padded concept-explanation of a 1 nor the fully lean every-token-earns-its-place of a 3.

2 / 3

Actionability

It provides fully executable, parameterized commands (e.g. "python3 tools/financial_rigor.py verify-market-cap --price {价格} --shares {股本} --reported {报告市值} --currency {币种}") plus concrete Task tool config (subagent_type, run_in_background, team_name) and a ready-to-use agent prompt template, matching the copy-paste-ready anchor at 3.

3 / 3

Workflow Clarity

Ten explicitly numbered steps (第一步–第十步) sequence the process, and Step 9 (数据抽检/准出流程) implements a real validation gate with a feedback loop (extract → verify → verdict → 准出/打回 → 修正后重审), satisfying the clear-sequence-with-explicit-validation anchor at 3.

3 / 3

Progressive Disclosure

The file is well-sectioned but monolithic at ~225 lines, with detailed prompt templates and report-structure specs kept inline; its references (skills/financial-data.md, tools/financial_rigor.py, tools/report_audit.py) point to external repo paths rather than bundled files present in the skill directory, so it is not the clean overview→one-level-reference split of a 3.

2 / 3

Total

10

/

12

Passed

Description

50%

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 niche (four-role parallel investment research) but functions more as a titled label than a capability description: it has no concrete actions, no explicit "when to use" trigger, and is padded with non-functional metadata ("Source: skills/investment-team.md"). It is acceptable but leaves trigger clarity and actionability unspecified.

Suggestions

Replace the vague "AI Berkshire skill" label with concrete actions, e.g. "Conducts team-based investment research by spinning up four parallel analyst agents (business, financial, industry, risk) and synthesizing a scored buy/sell report."

Add an explicit trigger clause such as "Use when the user asks for in-depth investment analysis, stock research, valuation, or a multi-perspective buy/sell recommendation on a company."

Drop the non-functional metadata ("Source: skills/investment-team.md") from the description, as it is not a capability or trigger.

DimensionReasoningScore

Specificity

The description names a specific domain and structural method ("投研团队:四角色并行分析框架" / four-role parallel analysis framework), but lists no concrete action verbs, keeping it short of the multiple-specific-actions anchor at 3 and above the purely vague "helps with documents" anchor at 1.

2 / 3

Completeness

It partially answers "what" (a four-role parallel investment-research framework) but provides no "when" trigger; per the guideline a missing "Use when..." clause caps completeness at 2.

2 / 3

Trigger Term Quality

It carries domain-relevant keywords (投研, 投资, 分析, 四角色并行) but includes no "Use when..." trigger clause and omits common variations (股票研究, 估值, 投资分析), while "AI Berkshire skill" is internal jargon rather than a natural user phrase.

2 / 3

Distinctiveness Conflict Risk

The four-role investment-research niche is fairly specific and unlikely to conflict broadly, but the generic "AI Berkshire skill" prefix and absence of distinct triggers leave it overlapping with other financial-analysis skills.

2 / 3

Total

8

/

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.