valuation-methods
Compact valuation discipline for DCF, multiples, and scenario analysis.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 16
- Forks
- 10
01 前言 Front Matter
- name
- valuation-methods
- description
- Compact valuation discipline for DCF, multiples, and scenario analysis.
03 SKILL.md 正文
Valuation Methods
- Match the method to the business model; do not force a DCF or multiple where its denominator is economically meaningless.
- Keep enterprise value and equity value separate, and reconcile net debt, leases, pensions, minorities, investments, and diluted shares consistently.
- Label trailing, forward, fiscal, calendarized, reported, and normalized figures.
- Anchor assumptions in operating drivers, then use bear, base, and bull cases.
- In a DCF, disclose revenue growth, margin, tax, reinvestment, discount rate, perpetual growth, net debt, and diluted shares.
- Always show sensitivity and the share of enterprise value coming from the terminal value.
- For relative valuation, justify the peer set and explain structural differences before applying a multiple.
- Avoid false precision; a range with explicit conditions is more useful than a single target.
04 同仓库更多 Skills
pilotswarm-three-tier
Reference for adding a Tier 3 worker AKS cluster to a PilotSwarm deployment. Covers provisioning, identity, Dockerfile changes, entrypoint, manifests, and verification.
pilotswarm-sdk-builder
Use when creating or updating an SDK-first app on top of PilotSwarm. Covers the client/worker split, plugin layering, tool registration, tests, and the DevOps sample structure.
pilotswarm-portal-builder
Use when creating or updating a browser portal on top of PilotSwarm. Covers portal branding, plugin.json.portal, named-agent exposure, auth add-ons, and remote deployment wiring.
pilotswarm-knowledge-harvester
Use when an SDK or CLI app needs to ingest external sources into durable, searchable knowledge and an open knowledge graph. Covers enabling the EnhancedFactStore + GraphStore providers, authoring a crawler:true agent, the crawl→graph→reader flow, ACL/scopeKey evidence, and tests.
pilotswarm-hybrid-datastore
Use when a PilotSwarm app needs stock PostgreSQL for runtime storage plus HorizonDB for enhanced facts, semantic/lexical search, and the knowledge graph. Covers env topology, horizonConfigFromEnv wiring, harvester agents, Azure secret/resource guidance, and the rule that Docker defaults remain stock Postgres.
pilotswarm-duroxide-versioning
Use when changing PilotSwarm durable orchestration behavior, continue-as-new state, or replay-sensitive control flow.