CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wealth-structure

当用户问「怎么赚钱/如何致富/该不该要期权/如何判断一个生意的结构」时调用。 核心理念: 财富=睡觉时仍在赚钱的资产; 靠「责任(押上声誉)→产权(股权/知识产权)→杠杆(无需许可的代码媒体)→避免出局」构建, 无法靠出租时间致富。 不适用于: 具体投资标的分析、理财产品的选股建议。 Triggers: 致富/赚钱/股权/期权/杠杆/被动收入/ownership/leverage/equity

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./dist/naval-almanack-pack/wealth-structure/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured knowledge skill: it compresses the book's ideas into a memorable framework, grounds them in two concrete cases, defines trigger scenarios and boundaries, and closes with sequenced steps that have explicit completion criteria and a stop condition. Remaining issues are minor: bookkeeping metadata inside the body, one dangling file reference, and completion criteria that sometimes describe user habits instead of executable checks. Suggestions: (1) Remove or relocate the "审计信息" block and metadata comments — they consume context without aiding application. (2) Fix the dangling "见 test-results.md" reference by shipping the file or dropping the pointer. (3) Rewrite step 4's "完成标准" as a concrete, executable check (e.g. the exact three diagnostic questions re-applied) consistent with the other steps.

Suggestions

Remove or relocate the "审计信息" block and leading capability/metadata comments — they consume context without helping the model apply the skill.

Fix the dangling reference "测试通过率: 见 test-results.md" by including the file in the bundle or deleting the pointer.

Rewrite step 4's "完成标准" (每季度检查) into a concrete executable check — e.g. re-run the three diagnostic questions and state the current ownership/leverage level — consistent with the other steps.

DimensionReasoningScore

Conciseness

The body is dense and distilled — the R/I sections compress the source into a short quote and a five-point skeleton, and both A1 cases are four bullets each — with every section earning its place for a knowledge-transfer skill. It is not 5 because the trailing "审计信息" block ("验证通过: V1 ✓ / V2 ✓ / V3 ✓", "蒸馏时间") and leading capability/metadata comments add tokens that do not help the model apply the skill.

4 / 5

Actionability

The E section gives concrete, checkable guidance: each step has a "完成标准" (e.g. "回答三个问题——收入是否按时间计?有无产权…有几层杠杆?") and step 2 even has a 判停条件. It is not 5 because some completion criteria (e.g. step 4's "每季度检查资产") describe user habits rather than directly executable instructions, and there is no worked example of applying the diagnostic to a concrete offer/business.

4 / 5

Workflow Clarity

The four E steps are clearly sequenced (诊断→向上迁移→加护栏→复跑) with per-step checkpoints and an explicit stop-and-loop condition in step 2. It matches anchor 4 rather than 5 because there is no full validation/re-check loop (e.g. re-diagnosing after a migration to confirm the level actually moved), though the knowledge-skill context means the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

The body is one well-organized file with clear R/I/A1/A2/E/B section headers and no nested references, which is appropriate for a skill of this size. It is not 5 because the body points to "test-results.md" ("测试通过率: 见 test-results.md") which does not exist in the bundle — a dangling reference — and the audit/related-skill metadata could live outside SKILL.md.

4 / 5

Total

16

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it explicitly covers what the skill provides (the responsibility→ownership→leverage→avoid-ruin framework), when to invoke it (concrete bilingual trigger phrases), and when not to (investment-picking requests). The main gap is that the 'what' is framed as a concept rather than as concrete diagnostic actions. Suggestions: (1) Add 1-2 explicit action verbs to the core-idea line, e.g. "诊断当前收入结构、评估 offer 的股权与杠杆层级", so the 'what' reads as concrete operations. (2) Round out trigger coverage with missing natural variants such as "财务自由/how to get rich/passive income/should I take equity". (3) Move or summarize the skill-vs-adjacent-skill distinction (e.g. vs. productize-yourself) into the description's exclusion clause to further reduce overlap risk.

Suggestions

Add 1-2 explicit action verbs to the core-idea line, e.g. "诊断当前收入结构、评估 offer 的股权与杠杆层级", so the 'what' reads as concrete operations rather than only a concept statement.

Round out the Triggers line with missing natural variants such as "财务自由/how to get rich/passive income/should I take equity" to reach comprehensive synonym coverage.

Surface the adjacent-skill distinction (e.g. vs. productize-yourself, 投资建议) in the description's 不适用于 clause to further reduce conflict risk.

DimensionReasoningScore

Specificity

The description states the domain and core framework — "财富=睡觉时仍在赚钱的资产; 靠「责任(押上声誉)→产权(股权/知识产权)→杠杆…→避免出局」构建" — and one implicit action via "如何判断一个生意的结构", but it describes a concept rather than listing concrete operations. It matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive); not 4 because no explicit action verbs like "诊断收入结构/评估股权" are given, and not 2 because the framework breakdown is specific, not generic.

3 / 5

Completeness

Both questions are explicitly answered: "what" via the core-idea statement ("靠「责任→产权→杠杆→避免出局」构建, 无法靠出租时间致富") and "when" via "当用户问「怎么赚钱/如何致富/该不该要期权/如何判断一个生意的结构」时调用" plus the dedicated Triggers line. It also adds an explicit not-when clause ("不适用于: 具体投资标的分析…"), matching anchor 5 rather than 4, where the 'when' would be less explicit.

5 / 5

Trigger Term Quality

The explicit Triggers line "致富/赚钱/股权/期权/杠杆/被动收入/ownership/leverage/equity" plus natural user phrases like "怎么赚钱/如何致富/该不该要期权" give good bilingual keyword coverage. It falls short of anchor 5 because common variations such as "财务自由", "get rich", or "passive income" in English are absent.

4 / 5

Distinctiveness Conflict Risk

The explicit exclusion "不适用于: 具体投资标的分析、理财产品的选股建议" plus fairly specific triggers (股权/期权/杠杆/被动收入) carve out a clear niche with minimal conflict. Not 5 because broad terms like "赚钱/致富/被动收入" could still overlap with adjacent wealth or investing skills whose disambiguation lives only in the body, not the description.

4 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

kangarooking/cangjie-skill

Path

dist/naval-almanack-pack/wealth-structure/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.