company-diagnostician

Classifies companies and compiles valuation routing with engines, overlays, and constraints.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing the wrong valuation method produces confident nonsense: a cost of capital for a bank, a P/E multiple at a cyclical trough, or a going-concern value for a firm near failure. This Skill classifies a company and compiles the exact valuation route — one engine, overlays, an ordered pipeline, and closed methods — so every downstream stage works from a correct foundation. ## Core Features & Use Cases - Signal extraction and gating: Computes margins, coverage, leverage, and distress signals via Python scripts, then applies sequential gates (sector, ownership, life-cycle, survival) to select one of sixteen engine branches. - Route compilation: Emits a machine-readable classification.json with the primary path, overlays, discount stack, sourced constraints, and pipeline order, plus a human-readable diagnosis.md explaining every judgment. - Use Case: As the classification stage of a valuation orchestrator run, it receives mandate.json, raw-financials.json, market-data.json, and gaps.json, then routes a loss-making cyclical manufacturer to a normalized-earnings engine with distress overlays before any forecasting begins. ## Quick Start Ask the valuation orchestrator to classify the target company and produce its valuation route from the collected financial and market data files.

Frequently Asked Questions about company-diagnostician

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

FAQPage Schema
How do I choose the right valuation method for a company?

Classify the company first: extract signals like margins, leverage, and earnings status, then apply sector, ownership, life-cycle, and survival gates in order. This Skill automates that process, selecting exactly one engine branch from sixteen and listing which methods are closed.

How to classify a company for DCF valuation routing?

Run the S0-S8 gate sequence: evidence intake, signal extraction, sector gate, provisional statement repair, ownership gate, life-cycle gate, survival gate, then overlays and constraints. The output classification.json records the primary path, engine branch, and pipeline order.

Can this skill be used standalone outside the valuation orchestrator?

No, it is a stage brief designed for orchestrator delegation with supplied absolute input paths. For direct use, load the company-classification-routing skill instead, which carries the full underlying procedure and reference files.

What happens when input financial data is missing or malformed?

The stage returns blocked and names the exact missing file or malformed field rather than routing on partial data. When a judgment call cannot be settled by evidence, it returns needs_input with the question and concrete routing options.

Why must constraints come only from fired branches?

Every downstream stage obeys the constraint list, so an invented constraint blocks valid methods just as an omitted one permits invalid ones. Each constraint must carry a source_branch, plus the two universal constraints on perpetual growth and single-charge-per-risk.