CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

thesis-tracker

AI Berkshire skill: 投资论文追踪:买入后的纪律系统. Source: skills/thesis-tracker.md.

Quality

69%

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/thesis-tracker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, two-mode workflow with concrete templates, explicit redline-to-action mappings, and a quantified health-score formula — highly actionable with clear sequencing. The main defects are cosmetic-mechanical: a malformed table in B6, an unspecified tool invocation, and a few motivational sections that could be trimmed.

Suggestions

Fix the malformed B6 table: the block at '#### 论文健康度评分标准' renders a bare table header followed by the bold formula line, then repeats the header — merge the formula into a normal paragraph or table row so the score bands render correctly.

Specify the arguments for the verification command, e.g. 'python3 tools/financial_rigor.py verify-valuation --ticker <代码> --data <估值数据>', so the A0 checkpoint is copy-paste executable.

Trim the epigraphs and 设计理念 section (or fold them into 关键原则) and move the Codex adapter note to the end of the file so the workflow starts immediately after the title.

DimensionReasoningScore

Conciseness

The body is dominated by lean fill-in tables and templates where every token earns its place (thesis template, assumption/redline tables, health-score formula), with only minor trimmable material: the epigraph quotes from 李录/凯恩斯, the 设计理念 rationale section, and the 6-bullet Codex adapter note. This matches anchor 4 (efficient, minor instances of over-explanation) rather than 5, since those sections are motivation/meta rather than executable guidance.

4 / 5

Actionability

Concrete file paths ('reports/{公司名}-thesis.md'), a runnable command ('tools/financial_rigor.py verify-valuation'), a fill-in 5-sentence thesis template, status definitions, and an explicit health-score formula make the guidance mostly executable. Minor gaps keep it below anchor 5: the verify-valuation command's required arguments are unspecified, and the B6 health-score table is malformed (a stray header row followed by the formula line, then the table repeats).

4 / 5

Workflow Clarity

A clear mode-dispatch step branches into A0-A5 and B1-B7 with explicit checkpoints (the 5-question litmus test '如果5句话写不完整...', redline-to-action mapping, mandatory report structure, and the three mandatory conclusion questions). Not anchor 5: there is no validate-and-retry feedback loop around data collection or report output, and the malformed B6 table obscures one checkpoint.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ absent) and the content is appropriately single-file with clean, navigable section headers (模式A/模式B split). Structure is good with minor gaps — the Codex adapter note and 设计理念 sit above the actual workflow — matching anchor 4; the under-50-line exception for a 5 does not apply to this ~220-line body.

4 / 5

Total

16

/

20

Passed

Description

48%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 clear and distinctive domain but never says what the skill actually does or when to invoke it. It is essentially a title plus a source-file pointer, not a capability statement with trigger guidance.

Suggestions

State the concrete actions in the description, e.g. '建立并持续追踪投资论文:写入核心假设与红线清单,按季报逐条验证假设、更新估值锚点并输出健康度评分与加/减仓建议' (establish and track investment theses: write core assumptions and redline list, verify assumptions per quarterly report, update valuation anchors, output health score and position advice).

Add an explicit trigger clause, e.g. 'Use when the user mentions a stock they hold/bought, asks 投资论文/论文检查/该不该卖/持仓复查, or requests a quarterly thesis review.'

Remove or compress the 'AI Berkshire skill:' and 'Source: skills/thesis-tracker.md.' fragments; they are internal metadata and dilute the token budget of the description.

DimensionReasoningScore

Specificity

The description names the domain ("投资论文追踪:买入后的纪律系统") but lists no concrete actions such as establishing a thesis, running quarterly checks, or redline review; "Source: skills/thesis-tracker.md" is metadata rather than capability. It names the domain with only generic actions, matching anchor 2, not anchor 3 which requires 1-2 explicit actions.

2 / 5

Completeness

The "what" is stated at domain level (post-purchase thesis tracking/discipline system), but there is no "Use when..." or equivalent trigger guidance, which caps completeness at 3. It is above 2 because the what is genuinely stated rather than vague.

3 / 5

Trigger Term Quality

"投资论文", "追踪", and "买入后" are plausible user phrases, but the description omits natural synonyms and variations users would actually say (e.g. "论文检查", "该不该卖", "持仓复查", "thesis check"), matching anchor 3.

3 / 5

Distinctiveness Conflict Risk

"买入后的纪律系统" carves a fairly distinct post-purchase niche, but the generic "AI Berkshire skill" prefix and overlap with sibling investment-research skills leave minor conflict risk, matching anchor 4 (mostly distinct, minor overlap risk) rather than 5 (clear niche with distinct triggers).

4 / 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/thesis-tracker/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.