valuation-sanity-check
Skill7 starsChanged 4 months agoLicence not identifiedView on GitHub
Sanity-check an internal analyst valuation thesis against the live peer set. Input the target price, assumed revenue growth, assumed EBITDA margin, and horizon; the skill pulls the current name, builds the peer cohort, computes target-implied multiples vs the peer 25-75 band, compares the growth and margin assumptions to the peer distribution, runs a simplified reverse-DCF, and emits either a single-point fair-value estimate or a full fair-value distribution (--mc flag) as a one-page sell-side flash note answering "is this target defensible or has the model drifted from reality." Use when a banker, PM, or analyst is stress-testing a price target or pitch-deck valuation. Requires Stocks Starter.
- Reads credentials
In this repository62 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- 8-k-scannerSkill
- analyst-trackerSkill
- backtest-data-prepSkill
- change-point-detectorSkill
- commodity-cycleSkill
- corp-actions-reconcilerSkill
- corporate-actions-scannerSkill
- crypto-vol-scannerSkill
- earnings-blackoutSkill
- earnings-drilldownSkill
- earnings-week-prepSkill
- event-studySkill
- factor-researchSkill
- filing-sentimentSkill
- filing-triangulationSkill
- fixed-income-contextSkill
- guidance-trackerSkill
- hedge-suggesterSkill
- historical-analog-finderSkill
- historical-comparisonSkill
- hurst-exponentSkill
- insider-flowSkill
- macro-event-calendarSkill
- manager-portfolio-diffSkill
- market-regimeSkill
- massive-api-patternsSkill
- massive-flat-filesSkill
- massive-websocketsSkill
- mc-portfolio-simulatorSkill
- morning-briefSkill
- news-scannerSkill
- options-flowSkill
- options-structure-analyzerSkill
- pairs-scannerSkill
- pitch-compsSkill
- portfolio-macro-scenarioSkill
- portfolio-markSkill
- portfolio-rebalancerSkill
- portfolio-reviewSkill
- position-sizerSkill
- prediction-market-monitorSkill
- pre-earnings-full-stackSkill
- preflight-tradeSkill
- regime-auditSkill
- relative-strengthSkill
- risk-factor-deltaSkill
- risk-reportSkill
- rough-vol-forecastSkill
- scan-and-frameSkill
- sector-rotation-signalSkill
- signal-decaySkill
- single-name-vs-sectorSkill
- slippage-costSkill
- smart-money-clusterSkill
- stock-one-pagerSkill
- t+1-settlement-prepSkill
- technical-briefingSkill
- universe-builderSkill
- vs-benchmark-auditSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

