CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

thesis-drift

AI Berkshire skill: 投资论文漂移检测:分清事实变化与措辞变化. Source: skills/thesis-drift.md.

Quality

76%

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

Quality

Content

88%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 strong, highly actionable instruction-only skill: it fixes the five judgment dimensions, mandates tool-verified arithmetic, and defines exact output formats, with explicit handling for wrong pairings and missing baselines. Its weaknesses are the absence of any progressive disclosure (all reference material inlined in one long file) and minor padding from meta-notes and repeated principles.

Suggestions

Move the per-dimension judgment criteria tables and the output report/drift-table templates into a references/ file (e.g. references/dimensions.md), keeping SKILL.md as the workflow overview with well-signaled one-level-deep links.

Trim the epigraph quotes and condense the 'Codex adapter note' section, which is meta-infrastructure rather than skill content, to reduce token overhead.

De-duplicate the rules stated twice (e.g. wording-is-not-drift appears in A2, A5, and 关键原则; tool-verified arithmetic appears in A3 and 关键原则), keeping each rule in one canonical place.

DimensionReasoningScore

Conciseness

The body is dense and operational — judgment tables, command templates, and output formats with almost no explanation of concepts Claude already knows. Minor trims are available: the epigraph quotes, the meta 'Codex adapter note' section, and some principles repeated between A5 and 关键原则. Not 5: these few padded passages do not earn their tokens.

4 / 5

Actionability

Fully concrete guidance: exact executable commands (python3 tools/financial_rigor.py verify-valuation / cross-validate / three-scenario / calc with argument placeholders), fixed 5-dimension judgment table with Improved/Unchanged/Weakened criteria, and a complete copy-paste output report structure and drift table. Not 4: there are no gaps in coverage of the common cases.

5 / 5

Workflow Clarity

Explicit mode dispatch (A: specified reports, B: auto snapshot discovery, C: missing baseline) with a sequenced A1–A6 pipeline and validation checkpoints throughout: two-source cross-validation of key figures, wrong-company pairing guard, structural-missingness handling, and a full missing-baseline fallback that refuses to fabricate a comparison. Not 4: error-recovery paths are explicit rather than implicit.

5 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and the single file is well-sectioned with clear headers and one-level-deep pointers to external repo tools (tools/financial_rigor.py, /thesis-tracker). Not 5: at ~210 lines with large judgment-table and report-template reference material inlined, some content (e.g. the per-dimension criteria tables and output templates) would be better split into a reference file; the under-50-line simple-skill exception does not apply.

4 / 5

Total

18

/

20

Passed

Description

53%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 terse and names a clear niche, but it reads more like a title than a capability description: it lists only one action, omits when to use the skill, and provides no trigger variants. Adding a 'Use when...' clause and 2-3 concrete actions would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when comparing two research reports or thesis snapshots for the same company, or when deciding whether an investment thesis has actually changed.'

Enumerate the concrete actions the skill performs: compares two thesis reports across fixed dimensions (valuation, assumptions, red lines, management, moat), verifies numbers with a precision tool, and outputs a drift report with action migration.

Include natural trigger synonyms (Chinese and English) such as '论文变化', 'thesis drift', '报告对比', '快照对比' so the skill surfaces for varied user phrasing.

DimensionReasoningScore

Specificity

The description names the domain ('投资论文漂移检测' — investment thesis drift detection) and one concrete capability ('分清事实变化与措辞变化'), but does not enumerate the skill's other concrete actions (report comparison, per-dimension drift judgment, action-migration reporting). Not 4: the coverage gap is substantial rather than minor.

3 / 5

Completeness

The 'what' is clear (detect thesis drift, distinguish fact changes from wording changes), but there is no 'Use when...' or equivalent trigger clause, capping completeness at 3. Not 2: the 'what' is specific and informative, not vague.

3 / 5

Trigger Term Quality

Relevant keywords are present ('投资论文', '漂移', '事实变化', '措辞变化') but natural variations users would say are missing (e.g. '论文变化', 'thesis drift', '报告对比', '快照对比'). Not 4: more than a few natural terms are absent, including any English triggers.

3 / 5

Distinctiveness Conflict Risk

'投资论文漂移检测' carves out a clear niche with minimal generic overlap. Not 5: the description does not differentiate it from the sibling '/thesis-tracker' skill it depends on, leaving some risk of triggering the wrong skill on '论文'-related requests.

4 / 5

Total

13

/

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-drift/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.