Business Insight Card

Problem

When a user wants to understand how a company makes money, its business structure, core contradictions, or moat, generic answers often mix valuation calls, isolated metrics, and generic industry language. This skill separates business interpretation from valuation matching: it focuses on the business model, revenue sources, moat, core contradictions, and structure without concluding whether the stock is expensive.

How It Works

The workflow calls wm.sh run first to obtain fact sources such as snapshot, sections, and metrics_bar. It then reads enrich_plan.required_reads for the industry lens and workflow context, and produces output according to output-skeleton. The design principle is XS = facts + Gate and Pack = narrative + lens + Verify, meaning the agent should not alter numbers or enrich_plan, but translate verifiable data into a buyer-perspective narrative. Tables are used only when at least two rows share the same metric basis; cash-flow types are excluded to avoid fragmented indicator comparison.

Boundaries

It is suitable for questions like “What is the business DNA? What is the core contradiction? Where is the pricing position?” It is not suitable for valuation, current price, revenue-by-segment queries, or a one-page company overview. The skill explicitly warns against using render or markdown_skeleton as the final article, and against delivering raw JSON tables as the interpretation.