# Andy-company-analysis-financial-metrics

Adopt this skill: https://proskills.md/skills/other/harlan66-harlan-openclaw-skills-skills-andy-company-analysis-financial-metrics

Page: https://proskills.md/skills/other/harlan66-harlan-openclaw-skills-skills-andy-company-analysis-financial-metrics
This document is the public skill bundle for that page. It contains SKILL.md and every helper file the catalog carries. No login is required.

## File: skills/Andy-company-analysis-financial-metrics/SKILL.md
size: 8070
upstream: https://github.com/harlan66/harlan-openclaw-skills/blob/main/skills/Andy-company-analysis-financial-metrics/SKILL.md

````text
---
name: Andy-company-analysis-financial-metrics
description: Systematically analyze a company, product, or business model and interpret key financial indicators for investing, research, deep-dive articles, workshop prep, or stock/company homework. Use this skill whenever the user asks to analyze a company, read a financial report, understand business quality, compare firms, study an industry, interpret profitability/ROE/ROA/margins/cash flow/working capital, or turn scattered company information into a structured investment-style analysis — even if they do not explicitly mention "company analysis" or "financial analysis." This version is distilled from Andy's workshop on 企业分析与财务指标解读.
---

# Andy Company Analysis & Financial Metrics

Turn messy company information into a structured, investor-style analysis.

This skill is for situations where the user wants more than a shallow summary. Use it when the task involves understanding **what the business is, how it makes money, where its moat or fragility comes from, and what the financials actually mean**.

## Source note

This skill is derived from Andy's sharing / workshop on 企业分析与财务指标解读. Keep the practical, workshop-style framing: explain how to think, not just what a metric is called.

## What this skill should produce

Choose the output shape based on the user's request, but keep the reasoning structure consistent.

Common output modes:
1. **Quick scan** — short investment-style memo
2. **Deep dive** — structured company analysis report
3. **Financial interpretation** — explain what specific metrics imply
4. **Comparison** — compare 2+ companies on business quality and financial health using the same evaluation axes
5. **Article scaffold** — convert research into a publishable outline

## Core workflow

Follow this order unless the user clearly wants only one slice.

### 1) Define the analysis target
Clarify what exactly is being analyzed:
- company
- product line
- business segment
- industry position
- listed stock as an investment target
- business model of a startup/private company

If the user is vague, infer the likely target first and state your assumption.

### 2) Build the four-part analysis frame
Organize the analysis into these four buckets.

#### A. Company overview
Cover:
- what the company does
- history and development stage
- ownership / shareholding structure if relevant
- governance structure if available
- key management or founder influence
- macro factors that materially affect the company

Why this matters: a business is not just a product. Ownership, control, governance, and macro exposure often explain incentives, strategic direction, and hidden risks.

#### B. Industry and market
Cover:
- market size and growth
- market structure: monopoly / oligopoly / fragmented / highly competitive
- competitive landscape and market share
- industry chain position
- supplier power and customer power
- whether the company has pricing power

Why this matters: good companies inside brutal industries can still earn poor returns. Industry structure often sets the ceiling for margins.

#### C. Business operations
Cover:
- main products / services / business lines
- product mix and revenue mix
- technology or capability edge
- customer structure
- To B vs To C differences
- business model in one sentence: **use what method to sell what product/service to whom**
- major risks: regulation, concentration, cyclicality, geography, founder dependence, commercialization delay, etc.

Why this matters: reported growth means little if the underlying revenue engine is fragile or low quality.

#### D. Financials and valuation sense
Cover:
- revenue and cost structure
- gross margin, operating margin, net margin
- margin quality and whether profit depends on non-recurring items
- cash position and liquidity
- working capital signals
- fixed assets / capex / construction-in-progress when relevant
- return metrics like ROE / ROA
- turnover metrics such as inventory, receivables, payables
- balance-sheet stress and cash-flow confirmation
- valuation framing if the user asks for it

Why this matters: numbers are evidence, not decoration. The point is to explain what the metrics say about moat, risk, and future earning power.

## Financial interpretation rules

When discussing metrics, do not only define them. Explain the business meaning.

### Margin stack
Interpret profit quality in layers:
1. **Gross profit / gross margin** — does the product itself make money? does the firm have pricing power?
2. **Operating profit / operating margin** — does the business model make money after running the organization?
3. **Net profit / net margin** — is the final profit real, or distorted by subsidies, fair-value changes, one-off gains/losses, or financing effects?

### High-priority metrics
When relevant, prioritize these:
- **Gross margin**: strongest quick signal for moat, industry economics, and pricing power
- **ROE**: how effectively equity produces returns
- **ROA**: how effectively the full asset base is used
- **Cash / liquidity**: survival line, especially for fragile or early-stage firms
- **Inventory turnover**: especially important for consumer and retail businesses
- **Receivables days**: collection discipline and customer power dynamics
- **Payables days**: bargaining power and supplier financing
- **Book value / net assets per share**: useful for asset-heavy or deep-value contexts

### Interpret metrics contextually
A metric is rarely good or bad on its own.
Examples:
- low sales expense ratio can mean efficiency **or** weak growth effort
- high cash can mean safety **or** poor capital allocation
- long payables can mean bargaining power **or** supplier stress
- low margins can be acceptable in scale-driven sectors, but fatal in commodity businesses without moat

Always tie the metric back to the business model and industry structure.

## Forecasting guidance

If the user asks about future performance, avoid pretending precision.
Ground forecasts in evidence such as:
- new capacity or factory ramp
- product launch pipeline
- regulatory approval milestones
- management guidance
- industry demand changes
- pricing trends in key inputs
- macro/geopolitical shocks

Prefer scenario language:
- base case
- upside case
- downside case

## Data gathering checklist

When source collection is part of the task, look for information in roughly this order:
1. company IR / official website
2. annual report / interim report / quarterly report
3. prospectus / IPO filing
4. exchange filings / regulator-hosted disclosures
5. investor platforms and financial data sites
6. industry associations / sector reports
7. management interviews or founder speeches when leadership quality matters

If data is incomplete, say what is missing and how that limits the conclusion.

## Output templates

### Template A — Quick scan
Use when the user wants a compact answer.

```markdown
# Company quick scan: [Name]
## Bottom line
## What the business does
## Industry structure
## Revenue and profit quality
## Key risks
## What to watch next
```

### Template B — Deep dive
Use when the user wants a serious write-up.

```markdown
# [Company name] analysis
## 1. Executive view
## 2. Company overview
## 3. Industry and market
## 4. Business model and operations
## 5. Financial interpretation
## 6. Risks and open questions
## 7. Valuation lens / investment take
## 8. Evidence gaps
```

### Template C — Metrics explanation
Use when the user asks about financial indicators directly.

```markdown
# Financial metric interpretation: [Company / Scenario]
## Metric snapshot
## What each metric means here
## Positive signals
## Warning signals
## What extra data would change the conclusion
```

### Template D — Comparison
Use when the user wants to compare two or more companies.

```markdown
# Company comparison: [A] vs [B]
## Bottom line
## 1. What each business actually sells and to whom
## 2. Industry structure and pricing power
## 3. Revenue quality and
````

## File: README.md
upstream: https://github.com/harlan66/harlan-openclaw-skills/blob/main/README.md

```text
# Andy-company-analysis-financial-metrics

A reusable OpenClaw skill for turning scattered company information into a structured, investor-style analysis.

## What this skill is for
Use this skill when the task is not just “summarize the company,” but to explain:
- what the business actually does
- how it makes money
- whether industry structure supports healthy returns
- whether the financial metrics reflect real business quality or just surface-level optics

It is especially useful for:
- company deep dives
- investment-style memos
- workshop prep or study notes
- interpreting ROE / ROA / margins / cash flow / working capital in context
- comparing two businesses on quality, moat, and financial health
- turning rough research into a long-form article outline

## What makes it different
The skill is designed to push beyond ratio definitions.
It emphasizes:
- business model before valuation
- industry structure before simplistic “good company / bad company” judgments
- profit quality over reported profit alone
- scenario-based forward views instead of fake precision

## Included files
- `SKILL.md` — model-facing instructions
- `evals/evals.json` — lightweight eval prompts
- `references/source-summary.md` — condensed workshop notes
- `examples/prompt-ideas.md` — extra prompt ideas

## Notes for reviewers
This skill is distilled from Andy's workshop / sharing on 企业分析与财务指标解读, but the package is written to stand on its own for public reuse.

It works best when the user wants structured reasoning rather than live market data, exact valuation models, or personalized investment advice.

## Suggested next validation focus
If you keep iterating, the highest-value next step is to test it on:
- one asset-heavy industrial company
- one software / platform company
- one regulated healthcare or medtech company
- one direct A-vs-B comparison prompt

#huanyuan
```
