CtrlK
BlogDocsLog inGet started
Tessl Logo

thesis-tracker

Buy-side discipline system. For each holding, maintain a written investment thesis — core thesis in 5 sentences, falsifiable assumptions, red lines, valuation anchors — and re-check it each quarter against new earnings/events. Scores thesis health 1-10 from assumption breakage and red-line triggers, and recommends hold / add / trim / exit. Use it right after buying a stock (to write the thesis) and every earnings season (to check it). Bridges the research→buy→monitor gap that most investors skip.

74

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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-structured, highly actionable methodology with clear sequenced workflows, verification checkpoints, and concrete templates/formulas. Its main weakness is conciseness: motivational quotes and explanatory prose add tokens that do not advance execution.

Suggestions

Remove the Li Lu, Keynes, and Duan Yongping quotes and condense the 'Design Philosophy' section into a one-line rationale, since they explain motivation Claude already grasps rather than instructing action.

Tighten the multi-paragraph macro-trend red-line blockquote into the table's 'Action on trigger' cell to keep the red-line catalog self-contained and scannable.

Consider moving the static reference tables (valuation anchors, action matrix) into a references/ file and linking from the body, which would shorten SKILL.md while preserving the workflow overview.

DimensionReasoningScore

Conciseness

The core methodology (templates, tables, the health formula, tool calls) is lean and earns its place, but motivational quotes from Li Lu, Keynes, and Duan Yongping plus the explanatory 'Design Philosophy' prose are unnecessary context that could be trimmed. It is not a 3 because not every token earns its place, and not a 1 because the bulk is structured domain-specific instruction rather than generic concept explanation.

2 / 3

Actionability

Provides concrete, copy-paste-ready guidance: specific tool calls ('web_search', 'read_file', 'financial_rigor (command=verify_valuation)'), exact file paths ('reports/{company}-thesis.md'), a 5-sentence thesis template, and a precise health formula '10 - (⚫broken × 3) - (🔴impaired × 2) - (🟡weakening × 1) - (red-lines triggered × 5)'. It is not a 2 because the guidance is complete and specific rather than pseudocode or partial.

3 / 3

Workflow Clarity

Mode A (A0→A5) and Mode B (B1→B7) are clearly sequenced, with explicit verification checkpoints — 'financial_rigor (command=verify_valuation)' to recompute metrics, the B3 assumption status check, and the B4 red-line check that forces re-evaluation. It is not a 2 because checkpoints are explicit rather than implicit; the file operations are non-destructive appends, so the missing-retry-loop cap does not apply.

3 / 3

Progressive Disclosure

No bundle files exist, so scoring is on organization: the body opens with a concise overview and supported-input summary, then branches cleanly into Mode A and Mode B with labeled sub-steps and a Key Principles section — easy to navigate with no nested references. It is not a 2 because there is no poorly-signaled or deeply-nested reference structure, and the methodology genuinely belongs inline.

3 / 3

Total

11

/

12

Passed

Description

100%

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 specific, complete, and distinctive: it names concrete actions, provides explicit 'use when' triggers tied to buying and earnings, and carves out a niche unlikely to conflict. It is concise without padding and uses appropriate third-person imperative voice.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'maintain a written investment thesis — core thesis in 5 sentences, falsifiable assumptions, red lines, valuation anchors', 'Scores thesis health 1-10', and 'recommends hold / add / trim / exit' — matching the anchor for multiple specific concrete actions. The imperative 'Use it' is third-person instruction (matching the rubric's own good examples), so no voice penalty applies; it is not a 2 because the action coverage is comprehensive rather than partial.

3 / 3

Completeness

Clearly states what it does (maintain/score/recommend on a thesis) and gives an explicit when-clause: 'Use it right after buying a stock (to write the thesis) and every earnings season (to check it).' It is not a 2 because the when guidance is explicit, not merely implied.

3 / 3

Trigger Term Quality

Contains natural phrases a target user would say — 'right after buying a stock', 'every earnings season', 'investment thesis', and 'hold / add / trim / exit' — giving good coverage of natural trigger terms. It is not a 2 because common variations are well represented rather than only partially covered.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (post-buy thesis tracking for buy-side investing) with distinct triggers unlikely to fire for unrelated skills. It is not a 2 because the domain and triggers are specific enough to avoid meaningful overlap with other skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
HKUDS/Vibe-Trading
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.