CtrlK
BlogDocsLog inGet started
Tessl Logo

dcf-model

Build discounted cash flow valuation workbooks in Excel.

50

Quality

58%

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 ./optional-skills/finance/dcf-model/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is highly actionable and exceptionally well-structured for execution, with concrete formulas, a clear stepwise workflow, and strong validation/feedback loops. Its main weakness is conciseness — heavy repetition and re-explanation of finance fundamentals Claude already knows — and limited progressive disclosure, with most guidance inlined and a referenced TROUBLESHOOTING.md missing from the bundle.

Suggestions

De-duplicate the sensitivity-table, scenario-block, formatting, and validation guidance that recurs across Critical Constraints, correct_patterns, common_mistakes, Excel File Creation, and Final Output Checklist — consolidate into a single authoritative statement.

Trim explanations of DCF/WACC/CAPM fundamentals (e.g. the Cost of Equity, Cost of Debt, and capital-structure formula walkthroughs) that Claude already knows; keep only the skill-specific conventions.

Move large reference material (detailed sheet layouts, color/border specs, troubleshooting) into referenced files under references/ and verify ./TROUBLESHOOTING.md actually exists before linking to it.

DimensionReasoningScore

Conciseness

The body is noticeably verbose (~1270 lines): it re-explains CAPM, WACC, terminal-value mechanics, and FCF build-ups that Claude already knows, repeats the sensitivity-table and scenario-block guidance multiple times (Critical Constraints, correct_patterns, common_mistakes, Excel File Creation, Final Output Checklist), and restates constraints in near-identical wording, fitting 'noticeably verbose; several unnecessary explanations or padded sections'.

2 / 5

Actionability

It provides fully executable, copy-paste-ready Excel formula patterns (e.g. '=E29*(1+$E$10)', '=INDEX(B10:D10, 1, $B$6)'), concrete openpyxl loop pseudocode, exact recalc commands ('python recalc.py model.xlsx 30'), and full CSV-layout templates covering the common cases, matching the 'fully executable; copy-paste ready' anchor.

5 / 5

Workflow Clarity

The 'Verify Step-by-Step With the User' block gives explicit confirm-after-each-stage checkpoints, and the 'Before Delivering Model (MANDATORY)' section gives a validate→fix→re-run recalc.py loop with explicit 'until status is success' and error-recovery guidance, satisfying 'clear sequence with explicit validation steps; feedback loops for error recovery'.

5 / 5

Progressive Disclosure

Most material is inlined monolithically in SKILL.md rather than split across reference files; the only bundle artifacts are scripts/validate_dcf.py and a referenced ./TROUBLESHOOTING.md that does not exist, and the body repeats large blocks (correct_patterns, common_mistakes, formatting, checklists) that read as candidates for separate files. This fits 'some structure but could be better organized; references present but not clearly signaled; content that should be separate is inline'.

3 / 5

Total

15

/

20

Passed

Description

46%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 concrete and distinct but terse: it states what the skill does in one short clause without any 'when to use it' trigger guidance or the natural term 'DCF'. Completeness is capped at 3 by the missing trigger clause, and trigger-term coverage is weak for a finance skill that users will request as 'DCF'.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks for a DCF model, intrinsic/equity valuation, or discounted cash flow analysis of a company.'

Include the natural trigger term 'DCF' (and 'DCF model', 'intrinsic value') so users' common phrasing matches the description.

Optionally name one or two companion actions (e.g. 'with scenario and sensitivity analysis') to lift specificity from a single action toward comprehensive coverage.

DimensionReasoningScore

Specificity

The phrase 'Build discounted cash flow valuation workbooks in Excel' names a single concrete action ('build DCF valuation workbooks') with a concrete target (Excel), but it lists only one action and no companion operations, matching the 'domain and 1-2 concrete actions, but not comprehensive' anchor.

3 / 5

Completeness

It clearly states what the skill does ('Build discounted cash flow valuation workbooks in Excel') but has no 'Use when...' clause or equivalent trigger guidance, so per the rubric completeness is capped at 3 ('clear what but when missing or only weakly implied').

3 / 5

Trigger Term Quality

It contains 'discounted cash flow', 'valuation', and 'workbooks'/'Excel', but omits the natural phrases and synonyms users say ('DCF', 'DCF model', 'model a company', 'intrinsic value', '.xlsx'), landing at 'one or two generic keywords; missing the natural phrases users say'.

2 / 5

Distinctiveness Conflict Risk

'Discounted cash flow valuation workbooks in Excel' carves a fairly specific niche that overlaps mainly with closely related finance skills (lbo-model, 3-statement-model), fitting 'mostly distinct; minor overlap risk with closely related skills'; it is not so generic as to score 3.

4 / 5

Total

12

/

20

Passed

Validation

68%

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

Validation11 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1271 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 2 missing

Warning

Total

11

/

16

Passed

Repository
NousResearch/hermes-agent
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.