valuation-critic

Attacks finished valuation analyses and raises structured findings with evidence and fixes.

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/lyndonkl/hermesworld --skill valuation-critic-lyndonkl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: valuation-critic
Source: https://github.com/lyndonkl/hermesworld/tree/main/packages/valuation-critic/skills/valuation-specialists/valuation-critic
Command: npx skills add https://github.com/lyndonkl/hermesworld --skill valuation-critic-lyndonkl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finished valuation models often contain double-counted risks, route violations, and unsupported terminal assumptions that pass internal consistency checks. This Skill provides the adversarial review stage that systematically attacks a completed DCF, relative, or deal analysis and converts every defect into an actionable finding. ## Core Features & Use Cases - Eleven-step attack sequence: Runs route-conformance, bias, single-charge-per-risk, growth-cost, terminal-value, equity-bridge, implied-expectations, comparable-set, seven-sins, traceability, and uncertainty attacks in a fixed order. - Mechanical validation gate: Executes the valuation-consistency-checks validator first and converts ERROR/WARN output into severity-ranked findings. - Structured findings output: Writes challenge.json with six-key findings (id, severity, target_stage, claim, evidence, suggested_fix) plus a five-section challenge.md prose companion. - Use Case: After an orchestrated DCF run values a company, this Skill recomputes what growth costs, reverse-solves the market price against the analyst's drivers, and reports that country risk was charged twice — once as a premium and once as a haircut. ## Quick Start Ask the agent to run the valuation critic stage against the mandate, classification, forecast, and DCF result artifacts and produce challenge.json and challenge.md.

Frequently Asked Questions about valuation-critic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a DCF valuation for errors?

Run the mechanical validator first, then work the eleven-attack sequence: route conformance, bias chronology, single-charge-per-risk, growth cost, terminal value, equity bridge, implied expectations, comparable-set bias, traceability, and the closing claim. Each defect becomes a finding with evidence and a suggested fix.

What is a single-charge-per-risk check in valuation?

It builds a register with one row per risk and one column per channel it could enter — premiums, haircuts, probability weights, bridge discounts. Any risk marked in two channels, such as a country premium plus an expropriation haircut, is a high-severity double-count finding.

Can this Skill be used outside the orchestrated team run?

No. It is a stage brief loaded by the valuation orchestrator after gate G6_valued and is not for direct use. For standalone adversarial review, load the valuation-red-team skill instead, which carries the full attack sequence.

Why does a clean validator run not guarantee a correct valuation?

A fitted model passes every internal consistency check because nothing inside it contradicts anything else. The critic therefore reads process chronology, compares drivers to sector benchmarks, and reverse-solves the market price to detect bias the arithmetic cannot reveal.

What happens when a required valuation artifact is missing?

The critic returns blocked status naming the exact missing or malformed artifact and field. It never reviews a half-built model as though it were finished, since that produces findings the owning stage already planned to fix.