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.

52

Quality

58%

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

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-organized and concrete for an analysis methodology, but it is a dense single-file wall with illustrative tables that inflate token cost and lacks executable code and explicit validation checkpoints.

Suggestions

Move the full valuation-trap table, reference WACC/EV-EBITDA ranges, and the output-format template into separate reference files, keeping SKILL.md a lean overview.

Tighten or trim the worked example tables (5-year FCFF projection and sensitivity matrix) to one compact illustrative row/column, since Claude already understands these mechanics.

Add an explicit validation checkpoint to the DCF workflow (e.g., sanity-check that WACC > g and that the terminal value is <75% of enterprise value before trusting the output).

DimensionReasoningScore

Conciseness

The body is dense and assumes competence without explaining basic concepts, but the full FCFF projection table, sensitivity matrix, and output template pad the token budget beyond what Claude needs for a methodology it largely already knows.

2 / 3

Actionability

Concrete formulas, parameter ranges, and a decision tree are provided, but the guidance is math notation and reference values rather than executable, copy-paste-ready code.

2 / 3

Workflow Clarity

A clear method-selection decision tree and cross-validation procedure exist, but the DCF steps lack explicit validation checkpoints or error-recovery feedback loops.

2 / 3

Progressive Disclosure

A single monolithic file holds everything inline — the trap table, full output template, and reference ranges could be split into separate reference files — though headings provide reasonable internal organization.

2 / 3

Total

8

/

12

Passed

Description

67%

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 and distinctive, clearly conveying the valuation methods covered, but it lacks an explicit "Use when…" trigger clause and broader natural-language triggers that users would actually say.

Suggestions

Add an explicit "Use when…" clause (e.g., "Use when valuing a company, building a DCF, or checking whether a stock is over/undervalued") to raise completeness.

Include common user phrasings such as "intrinsic value", "price target", and "is this stock overvalued/undervalued" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Enumerates multiple concrete capabilities — "DCF / DDM / SOTP", "PE-Band / PB-ROE / EV-EBITDA", "sensitivity analysis", "valuation-trap detection" — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Clearly states what the skill does but has no "Use when…" trigger clause, so the when-to-use guidance is only implied — capping completeness at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

Contains relevant domain keywords ("valuation", DCF, PE-Band, EV-EBITDA) but omits common lay phrasings like "value a stock", "intrinsic value", or "is this overvalued", leaving some natural variations missing.

2 / 3

Distinctiveness Conflict Risk

The named corporate-valuation methods carve out a clear niche with distinct triggers that would not collide with other skills.

3 / 3

Total

10

/

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.