CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

investment-team

AI Berkshire skill: 投研团队:四角色并行分析框架. Source: skills/investment-team.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

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

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 body delivers an unusually rigorous multi-agent workflow: clear step sequencing, hard validation gates (permission precheck, data audit with a pass/fail-and-refix loop), and concrete executable commands. Weaknesses are verbosity in the adapter/step framing and a bundle structure problem — referenced companion files and tools are not present in the skill bundle, so the skill is not self-contained as shipped.

Suggestions

Bundle or inline the critical dependencies: either ship skills/financial-data.md and the tools/*.py scripts inside the skill's references/ and scripts/ directories with paths relative to SKILL.md, or inline the essential data-source rules so agents are not blocked on unresolvable paths.

Move stable, bulky reference material — the four agent prompt templates and the final report format specification — into a bundled reference file (e.g., references/report-template.md) and point to it with clear one-level-deep links, trimming SKILL.md to the orchestration workflow.

Tighten conciseness: drop the redundant 重要注意事项 items that restate earlier steps, merge the Codex adapter note into a short preamble, and rename the odd 第一步半/第一步¾ steps into a continuous numbered sequence.

DimensionReasoningScore

Conciseness

The body is dense with genuinely novel, harness-specific instructions (permission precheck behavior, tool paths, agent protocol) and avoids explaining concepts Claude already knows, but it is noticeably padded: the Codex adapter note, the quirky 第一步半/第一步¾ step numbering, and repeated requirements across the 重要注意事项 section could be tightened. Anchor 4 would require only minor trims; this has several.

3 / 5

Actionability

Guidance is mostly executable: exact CLI invocations (python3 tools/financial_rigor.py verify-market-cap ...), a complete copy-paste agent prompt template, a concrete precheck grep command, and audit/verdict commands. The gap keeping it from 5 is that several referenced resources (skills/financial-data.md, tools/report_audit.py, tools/twstock_data.py) are not part of this skill's bundle, so paths are not resolvable from the skill directory alone.

4 / 5

Workflow Clarity

A clearly sequenced ten-step workflow with explicit validation checkpoints: a hard pre-launch WebSearch permission precheck that halts before spawning agents, a shutdown step, and a 准出/打回 (audit verdict with fix-and-re-audit) feedback loop. This matches the top anchor (explicit validation steps, feedback loops for error recovery, checklists) rather than anchor 4, which allows minor validation gaps.

5 / 5

Progressive Disclosure

The single 245-line SKILL.md has good section headers, but no bundle files exist (no references/, scripts/, or assets/), and the body points to companion files (skills/financial-data.md, tools/financial_rigor.py, tools/report_audit.py) that are not shipped alongside it — an agent following the skill cannot resolve them from the skill directory. Material that belongs in reference files (the financial data source spec, the agent prompt template, the report format) is inlined. Anchor 4 requires most content appropriately placed with clear references; this has unresolvable references and inline content that should be split.

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 is effectively a title plus a source-file pointer: it names the domain but states no concrete actions and gives no trigger guidance for when to use it. A user or model scanning skill descriptions would struggle to select this skill over siblings or know when it applies.

Suggestions

Rewrite the description in third person with concrete actions, e.g., "Orchestrates a four-role parallel investment research team (business model, financials/valuation, industry, risk) to produce a structured investment research report with scored dimensions and buy/wait/avoid recommendations."

Add an explicit trigger clause, e.g., "Use when the user asks to research or analyze a company/stock for investment decisions (值不值得买、投资分析、公司研究)."

Remove the provenance metadata ("Source: skills/investment-team.md") from the description and move it into the body; it consumes trigger-matching budget without helping skill selection.

DimensionReasoningScore

Specificity

The description names the domain ("投研团队:四角色并行分析框架" — a four-role parallel investment research framework) but describes no concrete actions, spending part of its budget on a provenance note ("Source: skills/investment-team.md"). It is above anchor 1 because the domain is specifically named, but below anchor 3 because no action verbs or capabilities are listed.

2 / 5

Completeness

The 'what' is only vaguely conveyed via a framework title, and there is no 'Use when...' or equivalent trigger clause at all, which caps completeness at 3; because the 'what' itself is vague rather than clear, this matches anchor 2 rather than anchor 3.

2 / 5

Trigger Term Quality

The only keywords are the skill's own title terms ("投研团队", "四角色并行分析框架", "investment-team"), which read as a label rather than phrases a user would naturally say. Missing common variations like 投资分析, 公司研究, 值不值得买, so it sits between anchor 1 (no relevant keywords) and anchor 3 (some relevant keywords).

2 / 5

Distinctiveness Conflict Risk

The investment-research niche is somewhat specific, but the "AI Berkshire skill:" prefix implies a family of sibling analysis skills (e.g., per-master frameworks) whose descriptions would trigger on overlapping requests like company analysis. Not anchor 4 because the overlap risk with closely related siblings is real, not minor.

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