valuation-red-team

Audits completed valuations for bias, double counting, and route violations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Finished valuations often contain hidden defects: double-counted risks, verdict-first bias, implausible terminal values, and route violations that quietly void the result. This Skill provides a systematic adversarial review that finds those defects and reports them as actionable findings before anyone acts on the number. ## Core Features & Use Cases - Eleven-attack sequence: Runs ordered attacks covering route conformance, bias diagnostics, single-charge-per-risk, growth-reinvestment reconciliation, terminal value plausibility, equity bridge double counts, implied expectations, comparable-set bias, the seven sins of acquisition analysis, narrative traceability, and uncertainty. - Structured findings output: Produces challenge.json with severity-graded findings (id, severity, target_stage, claim, evidence, suggested_fix) plus a prose challenge.md companion, routed to the owning stage for fixes. - Mechanical gate integration: Converts validator output (ERROR/WARN/INFO/SKIP) into findings and invokes sibling toolkits such as dcf-valuation-engine, relative-valuation-toolkit, and cost-of-capital-toolkit for implied-expectation solves and peer statistics. - Use Case: Before an investment committee acts on a DCF, run this review to catch a country risk premium charged alongside an expropriation haircut, quantify the double count per share, and route the fix to the cost-of-capital stage. ## Quick Start Red-team the completed valuation artifacts in this workspace and write challenge.json and challenge.md with severity-graded findings.

Frequently Asked Questions about valuation-red-team

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

FAQPage Schema
How do I red-team a DCF valuation for errors?

Run the mechanical consistency validator first, then work the eleven-attack sequence: route conformance, bias, single charge per risk, growth-reinvestment reconciliation, terminal value tests, equity bridge double counts, implied expectations, comparable-set bias, acquisition sins, narrative traceability, and uncertainty.

What inputs does a valuation review need before starting?

At minimum it needs classification.json, cost-of-capital.json, forecast.json, dcf-result.json, and the prose artifacts carrying the argument. Acquisition, restructuring, and IPO modes also require their stage artifacts, and gate G6_valued must have passed.

How are valuation review findings structured and routed?

Each finding carries an id, severity (high, medium, low), target_stage, claim, evidence with quoted numbers, and a suggested fix. Findings route to the single owning stage of the defective artifact, and high findings block the verdict gate until resolved or disclosed.

Can this review modify the valuation model it audits?

No. The review only raises findings with evidence and suggested fixes; it never edits forecast.json, dcf-result.json, or any other agent's artifact. Any rebuild done to test a claim is recorded as evidence inside a finding, not as a corrected model.

What is the implied-expectations attack in valuation review?

It solves the analyst's own driver payload backwards against the market price using the DCF engine's implied subcommand, then locates the solved value in the sector distribution. An impossible implied margin, share, or perpetual return is a high finding; an unstated disagreement with the market is medium.