Company Classification Routing

Classifies a company and routes it to the correct analytical treatment — life cycle stage, sector type, earnings status, ownership, distress markers, geography — then compiles the hard constraints that follow into classification.json. Use before any valuation begins, when deciding which valuation model applies, or when a company looks non-standard — a bank or insurer, a pre-revenue or loss-making firm, a distressed or declining business, a private company or an IPO, a cyclical or commodity producer, an emerging-market firm, or a multi-business group.

200 stars 25 forksMarketing, Sales & Business Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add lyndonkl/claude

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add lyndonkl/claude --skill company-classification-routing
Manual install
git clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/company-classification-routing ~/.claude/skills/company-classification-routing

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Company classification and routing

Standard valuation machinery assumes a lot. It assumes the firm survives long enough to
reach stable growth. It assumes debt is a financing choice rather than raw material. It
assumes this year's earnings say something about a normal year, and that there are
earnings at all. It assumes the owner is diversified and the shares trade.

Point that machinery at a bank, a pre-revenue startup, or a firm at a cycle trough and it
still returns a number. The number is confident and wrong. That is the most expensive
failure mode in this domain, because nothing downstream flags it: the arithmetic is
correct, the spreadsheet balances, and the answer is nonsense.

Routing comes first for that reason. This skill converts what is knowable about a company
into a *route* — one primary engine, a set of overlays, an ordered pipeline, and a list of
methods that must not be attempted. Gate `G2_classified` passes only when that route is
written and valid. Every stage after it reads the route and honors it.

**Full framework:** `knowledge/frameworks/special-situations-routing.md`. This skill is its
operating manual, and carries the parts an agent needs in hand.

## Contents

- [What this produces](#what-this-produces)
- [The four questions](#the-four-questions)
- [S0 · Evidence intake](#s0--evidence-intake)
- [S1 · Signal extraction](#s1--signal-extraction)
- [S2 · Sector gate](#s2--sector-gate)
- [S3 · Statement-repair gate](#s3--statement-repair-gate)
Read the full skill on GitHub

Details

Skill name
company-classification-routing
Path
skills/company-classification-routing/SKILL.md
Repo updated
1 September 2026

FAQ

What does the Company Classification Routing skill do?

Classifies a company and routes it to the correct analytical treatment — life cycle stage, sector type, earnings status, ownership, distress markers, geography — then compiles the hard constraints that follow into classification.json. Use before any valuation begins, when deciding which valuation model applies, or when a company looks non-standard — a bank or insurer, a pre-revenue or loss-making firm, a distressed or declining business, a private company or an IPO, a cyclical or commodity producer, an emerging-market firm, or a multi-business group.

How do I install the Company Classification Routing skill?

Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Company Classification Routing popular?

It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.

Related skills

Abstraction Concrete Examples

200

lyndonkl/claude

Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.

Testing & QA25

Academic Letter Architect

200

lyndonkl/claude

Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.

Research & Science25

Adr Architecture

200

lyndonkl/claude

Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.

Software Development25

Competitor Alternatives

213

TerminalSkills/skills

Plans, researches and writes comparison pages: "[rival] alternatives", "[product] vs [rival]", "[rival A] vs [rival B]" and switching guides. Builds each page from a ledger of sourced, dated facts and ends with an honest verdict on who should choose which product. Use when someone asks for an "alternative page", a "vs page", a "competitor comparison", "comparison landing pages", "why us instead of them", or wants existing comparison pages checked for outdated prices and claims that cannot be backed up.

Marketing, Sales & Business34

Clay

213

TerminalSkills/skills

Clay is a go-to-market data platform that finds companies and people, enriches them through many data providers (waterfalls), scores leads with AI and syncs them to a CRM or sequencer. Use when someone asks to "enrich leads with Clay", "build a prospect list", "set up a Clay table", "send data to a Clay webhook", "call the Clay API", "use the Clay CLI or plugin in Claude Code", "score leads against our ICP", or "automate outbound research".

Marketing, Sales & Business34

Contract Review

213

TerminalSkills/skills

Analyze contracts for risks, check completeness, and provide actionable recommendations. Use when a user asks to review a contract, check an agreement for red flags, analyze contract terms, find risky clauses, review an NDA, evaluate a service agreement, or audit employment contract terms. Supports employment contracts, NDAs, service agreements, and vendor contracts.

Marketing, Sales & Business34

Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.