agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/business-valuation/SKILL.md

business-valuation

Skill1 starsChanged 26 days agoMITView on GitHub

Estimates an indicative valuation range when a sale, investment, partner buyout or succession decision needs a defensible starting figure.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use before selling or buying a stake, negotiating with investors, settling a partner exit or planning succession.

    line 9
  2. Distinctive:

    Document the discount rate, growth and multiple assumptions and the evidence behind each.

    line 23
  3. Distinctive:

    Run sensitivity on the two assumptions that move value most.

    line 24
  4. Distinctive:

    Every adjustment and assumption is documented

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Business Valuation

When to use it

Use before selling or buying a stake, negotiating with investors, settling a partner exit or planning succession.

What Claude needs

  • client-context.md for business background
  • Purpose and date of the valuation
  • Three to five years of financial statements
  • Forecast and its key assumptions
  • Normalisation items such as owner pay or one-off costs
  • Comparable transactions or listed peers where available

Method

  1. State the purpose, valuation date and the basis of value being estimated.
  2. Normalise earnings for one-off items and non-market owner pay, documenting each adjustment.
  3. Apply at least two methods, such as earnings multiples from comparables and discounted cash flow.
  4. Document the discount rate, growth and multiple assumptions and the evidence behind each.
  5. Run sensitivity on the two assumptions that move value most.
  6. Reconcile the methods into a range and explain what would push value up or down.

Output format

Provide a valuation summary with normalised earnings table, results by method, sensitivity table, final range, and key value drivers and risks.

Quality checks

  • Gives a range, not a single precise number
  • Every adjustment and assumption is documented
  • States clearly that it is an indicative estimate, not a formal or certified valuation

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.