CtrlK
BlogDocsLog inGet started
Tessl Logo

valuation-model

Valuation methodology — absolute valuation with DCF / DDM / SOTP, relative valuation with PE-Band / PB-ROE / EV-EBITDA, sensitivity analysis, and valuation-trap detection.

58

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./agent/src/skills/valuation-model/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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, information-dense methodology document whose real value is the China A-share-specific reference data and the decision-tree/checklist/output scaffolding. It is weakened by re-explaining textbook formulas Claude already knows, by leaving the full analysis workflow implicit in section order, and by inlining hundreds of lines of reference tables that belong in separate reference files.

Suggestions

Move the bulk reference tables (industry WACC ranges, EV/EBITDA multiples, top-10 valuation traps, PE percentile examples) into references/ files and keep a lean overview with one-level-deep, clearly signaled links in SKILL.md.

Cut the standard formula derivations Claude already knows (WACC build-up, CAPM, Gordon model) and keep only the A-share-specific parameter values and judgment rules they feed.

State the end-to-end workflow as one explicit numbered procedure (classify → select methods → build model → cross-validate → sensitivity → trap check → output) with the >30% divergence checkpoint as an explicit validation step.

DimensionReasoningScore

Conciseness

The body is dense and much of it is genuinely non-obvious reference data (China A-share WACC ranges, industry EV/EBITDA medians, A-share-specific notes), but it also re-derives standard textbook formulas Claude already knows — the WACC build-up 'WACC = E/(D+E) × Ke + D/(D+E) × Kd × (1-T)', CAPM 'Ke = Rf + β × (Rm - Rf)', and the Gordon model. Mostly efficient with some unnecessary explanation, matching anchor 3; not 4 because several such derivations could simply be replaced by the skill-specific parameter values.

3 / 5

Actionability

Provides concrete, executable guidance for an instruction-only skill: exact formulas, quantitative thresholds (e.g. 'Goodwill / net assets >30% implies impairment risk', 'if the difference >30% -> check whether assumptions are reasonable'), a method-selection decision tree, and a copy-paste-ready output-format template. Not 5 because the illustrative tables (sensitivity matrix, PE band) are format examples rather than a single worked end-to-end case showing the inputs being derived.

4 / 5

Workflow Clarity

A clear sequence is established: company-type decision tree → chosen methods → mandatory sensitivity analysis ('sensitivity analysis is mandatory') → cross-validation with an explicit divergence checkpoint ('If the difference >30% -> check whether assumptions are reasonable') → trap checklist → structured output. Not 5 because the workflow is implied by section ordering rather than stated as one explicit numbered procedure with validation feedback loops.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent), so the skill is self-contained — but over 200 lines of reference material (WACC ranges by industry, EV/EBITDA multiples by industry, the top-10 valuation-trap table, historical PE percentile tables) are fully inlined in SKILL.md where a leaner overview plus references/ files would serve better. Structure and headings are clear, matching anchor 3 rather than 2, but the bulk inline reference content fits 3, not 4.

3 / 5

Total

14

/

20

Passed

Description

71%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.

A specific, well-scoped description that comprehensively enumerates the skill's valuation capabilities and uses natural domain terminology. Its main weakness is the absence of any 'Use when...' trigger clause, which both caps completeness and leaves the activation conditions implicit, and it lacks a few common synonym phrases users naturally use.

Suggestions

Add an explicit trigger clause, e.g. 'Use when valuing a company or stock, building a DCF/target price, or comparing valuation multiples like PE, PB, or EV/EBITDA.'

Spell out key acronyms once so natural-language queries match: 'discounted cash flow (DCF)', 'dividend discount model (DDM)', 'sum of the parts (SOTP)'.

Include everyday user phrasings such as 'fair value', 'target price', and 'is this stock overvalued or undervalued' as trigger terms.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capabilities with comprehensive coverage: 'absolute valuation with DCF / DDM / SOTP, relative valuation with PE-Band / PB-ROE / EV-EBITDA, sensitivity analysis, and valuation-trap detection' spans all major valuation approaches. Fits the top anchor rather than 4 because coverage is comprehensive rather than having minor gaps.

5 / 5

Completeness

Has a clear, detailed 'what' (the enumerated methods) but no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description; the opening noun phrase 'Valuation methodology —' only weakly implies when to use it. Per rubric guideline, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Contains strong natural domain keywords (DCF, PE, PB, EV-EBITDA, sensitivity analysis, valuation trap) that users would say, but misses common synonyms and full phrases like 'discounted cash flow', 'fair value', 'target price', or 'how much is a stock worth'. Good coverage with a few natural terms missing, matching the 4 anchor.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (corporate equity valuation) with method-specific triggers (DCF, SOTP, PB-ROE) unlikely to fire for unrelated skills. Not 5 because it could mildly overlap with adjacent general financial-analysis or fundamental-analysis skills covering the same stocks.

4 / 5

Total

16

/

20

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.

Validation — 15 / 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.