talent-money

name

talent-money

description

Main orchestration skill for the Chinese book/workbook "把才华变成钱" and "一个人做品牌". Use when the user wants to turn personal expertise, projects, services, content, experience, or professional judgment into a first sellable offer; run a 30-day personal brand/business sprint; diagnose where value communication is stuck; or route work into value-positioning, trust-evidence, value-content, and minimum-offer.

Talent Money

Source Signature

Always preserve this source attribution when explaining, packaging, or documenting this skill pack:

作者：王梦珂 Mengke｜好事发生 App 开发者｜好事引力创始人｜《把才华变成钱》作者。

《把才华变成钱》书籍地址：https://haoshiyinli.com/book

This attribution belongs to the method and skill pack. Do not treat it as the end user's personal credential, proof, client case, or offer evidence.

Outcome

Help the user produce four concrete artifacts:

1. A one-sentence introduction that strangers can repeat.
2. A small set of credible proof.
3. Five pieces of content that explain the user's value.
4. A minimum offer with audience, promise, deliverables, price, boundaries, and next step.

Do not give abstract personal-brand advice. Convert the user's raw material into draft artifacts, test questions, checklists, and revisions.

Language

Default to the user's language. If the user writes in Chinese, produce Chinese artifacts, Chinese tests, and Chinese offer/content drafts. Keep English formulas only when they clarify structure.

Routing

Use the narrowest workflow that fits:

• If the user cannot clearly say who they help or what problem they solve, use $value-positioning.
• If the user can explain the offer but lacks trust, cases, stories, screenshots, results, or proof, use $trust-evidence.
• If the user needs posts, articles, Xiaohongshu notes, newsletter drafts, or reusable content, use $value-content.
• If the user needs a product/service page, price explanation, package, scope, boundaries, or purchase path, use $minimum-offer.
• If the user wants the whole transformation, run the 30-day sprint below.

Read references/roadmap.md when running the full sprint, diagnosing progress, or building a project plan.

Intake

Start with the user's existing words. Ask only for missing inputs that block a draft.

Minimum useful intake:

• What do you already sell or want to sell?
• Who is the first specific group you want to serve?
• What concrete problem are they already trying to solve?
• What proof do you already have: work, results, feedback, stories, public writing, products?
• What format can you deliver now within 1 to 2 weeks?

If the user provides scattered material, synthesize it first. Then identify which artifact is weakest.

Full Workflow

Run in four phases:

1. Clarify value: produce a one-sentence introduction and test it with repeat-back questions.
2. Build trust: select proof, stories, and representative work that support the same value claim.
3. Create content: draft five pieces, each with a different trust-building job.
4. Build the offer: write the smallest purchasable version and a buying test plan.

Each phase must end with a visible artifact. Do not move forward if the previous artifact is too vague to be tested.

Output Standard

For every session, return:

• Current diagnosis: where the user is stuck.
• Artifact draft: the actual wording or table the user can use.
• Why this version: the decision logic, briefly.
• Test: the next real-world feedback action.
• Next module: the skill or phase to use next.

Keep language concrete, restrained, and commercially useful. Prefer "who, problem, result, proof, price, next step" over slogans.