ljg-business-model

Original：🇨🇳 Chinese

Translated

2 scripts

Based on the Business Model Canvas from Business Model Generation, organize user-provided project introductions, interviews, product materials, or business plans into nine-module Business Model Canvas cards, delivered as PNG and editable HTML. USE WHEN the user invokes ljg-business-model, asks to draw a Business Model Canvas, requests a nine-grid business model, or asks to turn business information into canvas cards. NOT FOR ordinary business analysis, investment valuation, Lean Canvas, or merely explaining business model concepts.

9installs

Sourcelijigang/ljg-skills

Added on2026-10-19

NPX Install

npx skill4agent add lijigang/ljg-skills ljg-business-model

SKILL.md Content (Chinese)

View Translation Comparison →

ljg-business-model

Turn the user's information into a Business Model Canvas that clearly shows who is served, what value is created, how that value is delivered, and how revenue and costs work. The primary deliverable is a landscape PNG in Chinese; HTML and structured JSON are also retained to support editing, traceability, and redrawing.

Workflow Routing

Input	Processing and delivery
Project introductions, interviews, documents, or scattered descriptions	Organize the information according to the contract below, run `Tools/Render.ts` , validate the output, and deliver the canvas
An existing canvas and additional materials	Update the specified model with the new information; preserve unaffected information and regenerate the canvas
Multiple independent businesses or business models	Create one canvas for each model; keep the different customer groups of the same multi-sided platform on one canvas and link them with C1, C2, etc.

Content Contract

Before starting, confirm the target and scope. If only a company name is provided and there is no business material, ask for a business description or conduct supplemental research with the user's authorization; if there is enough information for a draft, create it directly and mark missing items as “To be added.” If several possible targets would materially change the canvas, first ask one focused question.
Read CanvasGuide.md to calibrate the definitions, relationships, and canonical layout of the nine modules. Treat the user's materials as the primary source, and do not automatically turn industry assumptions into facts.
Tag every bullet point as
```
given
```
(provided by the material),
```
inferred
```
(an inference), or
```
unknown
```
(to be added). “Provided by the material” does not mean externally verified. Associate each
```
given
```
item with a source number, and include supporting reasoning for each
```
inferred
```
item. A plan explicitly stated by the user must still be written as “proposed” or “planned” and must not be changed into something already happening.
Prefer 2–4 specific bullet points in each box. Preserve distinctions such as who the customer is, what they buy, who pays, and the pricing unit. Write bullet points as “object + action or result” where possible. For revenue, retain the price and billing cycle; for costs, retain the main cost drivers. Do not invent amounts, scale, partners, or conclusions when the material does not support them.
Keep all nine boxes in the same view. Preserve the canonical spatial relationships, with costs and revenue at the bottom. Do not create an equal-width 3×3 grid, and do not replace the canvas with a Lean Canvas. Use color to support grouping and customer correspondence, and label inferred information with text as well so that meaning is not conveyed by color alone.

Generation and Acceptance

Prepare the input JSON in a unique temporary directory. Its structure is documented in Tools/Render.help.md, a complete fictional example is available in Example.json, and the layout reference is provided in Example.png. Record the actual skill directory as

SKILL_DIR

and run the following command from any working directory:

sh

bun "$SKILL_DIR/Tools/Render.ts" --input "$WORK_DIR/model.json" --output "$WORK_DIR/model.html"

User intent	Parameters or behavior
Draw cards by default	Use a default width of 1600 CSS px and export the final PNG
Specify a width	Use `--width 1200` through `--width 2400` ; readability must still be checked
Save to a specified location	After acceptance, place the final PNG, HTML, and JSON in that directory

Open the HTML in a real local browser, wait for fonts to become ready, and check the order of the nine boxes, all text, and any overflow. If Interceptor is available in the current environment, follow its isolation and screenshot contract; otherwise, use an available real-browser tool.

window.businessModelAudit()

provides checks for block count, missing items, inferred information, and geometric overflow. Export the entire

#canvas

element as a PNG, preferably at 2× pixel density. If screenshot capability is unavailable, retain the HTML and explicitly state that the PNG is incomplete; do not pass an HTML link off as an image.

Open the final PNG to inspect the full image, then zoom into dense areas. If the text is too dense, first simplify repeated wording or increase the canvas height; preserve all key conditions, and do not crop content, hide overflow, or shrink the text to force it to fit. If the renderer rejects overly long or excessive entries, reorganize the input and rerun it rather than bypassing validation.

Finally, display the PNG directly in the conversation and provide file links to the HTML and JSON. Briefly identify any missing information that affects understanding. Keep all drafts and screenshots in the temporary directory, and allow only accepted deliverables to enter the delivery directory.

Gotchas

The customer segment is the group being served; the payer may differ from the user. For a multi-sided platform, preserve the corresponding relationships across value, channels, and revenue.
Channels describe how customers are acquired, transactions are completed, and the offering is delivered. Customer relationships describe how interactions are established and maintained. Resources are things the company owns or can access, activities are things it does repeatedly, and partners are external participants.
Revenue sources describe how the business charges customers. Financing is not revenue. The cost structure describes spending logic and must not be used to infer profit or to add together data that has no stated time period.
Clear categorization does not mean the business model is viable. Conflicting material, unvalidated demand, and missing payment logic should remain visible rather than being smoothed over by a polished summary.
Retain the Business Model Canvas, Strategyzer.com, and CC BY-SA 3.0 attribution in the footer. This is a Chinese adapted layout, not the official original or a complete restatement of the book. The license applies to the canvas template and does not change the user's rights to the underlying business material.

Examples

“ljg-business-model: We provide procurement services for small restaurants and charge based on transaction value…” → Draw one card using the available information; mark missing partner and cost information as “To be added.”
“Turn this two-sided platform interview into a Business Model Canvas” → Label users and payers separately, and trace each side's value and revenue path.
“This is yesterday's canvas; now change it to an annual-fee subscription” → Update the charging method and, based on the additional material, check whether customer relationships and costs should also change; mark changes without supporting evidence as
```
inferred
```
.

ljg-business-model

NPX Install

Tags

SKILL.md Content (Chinese)

ljg-business-model

Workflow Routing

Content Contract

Generation and Acceptance

Gotchas

Examples