CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wealth-structure

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

Quality

85%

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

The canonical home for this skill is wealth-structure in kangarooking/cangjie-skill

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 conceptual skill: the I section gives a crisp five-part framework, the A1 cases ground it, and the E section is unusually actionable with per-step completion criteria, a stop-condition, and a quarterly review loop. Remaining issues are minor: trimmable audit/meta sections, a duplicated related-skills list, and a dangling reference to a nonexistent test-results.md.

Suggestions

Trim the audit section and the '(阶段 3 定稿)' label, and drop the duplicate related-skills list in the body since the frontmatter already records the same relations — this tightens conciseness toward anchor 5.

Remove or fix the dangling "见 test-results.md" reference (the file does not exist in the bundle), or move the audit metadata into that file so navigation is accurate.

Add a brief validation cue to steps 1, 3, and 4 of the E section (e.g., how to verify the three red lines were actually written down, or what to do if no leverage layer can be identified) to give every step a checkpoint like step 2's stop-condition.

DimensionReasoningScore

Conciseness

The body is dense and structured with no padding or explanation of concepts Claude already knows, but it includes trimmable meta-content: the audit section ("验证通过: V1 ✓ / V2 ✓ / V3 ✓ (v02)", "蒸馏时间: 2026-08-01"), the "(阶段 3 定稿)" label, and a related-skills list that duplicates the frontmatter — minor over-content that could be trimmed (anchor 4, not the every-token-earns-its-place of anchor 5).

4 / 5

Actionability

For an instruction-only skill the E section is fully actionable: each step has explicit completion criteria ("回答三个问题——收入是否按时间计?有无产权…?有几层杠杆?"), concrete example actions ("要期权、做产品、写内容、入股"), a written deliverable ("明确写下…三条红线"), and a review cadence ("每季度检查") — specific, executable guidance covering the common cases, matching anchor 5 for non-code skills.

5 / 5

Workflow Clarity

The four E steps are clearly sequenced with per-step completion criteria acting as checkpoints, and step 2 includes an explicit feedback loop ("判停条件: 若下一步涉及孤注一掷…跳过该动作并回到步骤 2") — a clear sequence with most checkpoints present. It falls short of anchor 5 because steps 1, 3, and 4 have no validation or error-recovery guidance of their own, only completion criteria.

4 / 5

Progressive Disclosure

As a single-file skill (~104 lines) it is well organized into clear R/I/A1/A2/E/B sections with no content that clearly belongs in separate files, but it is over the ~50-line simple-skill threshold and contains a dangling reference — "测试通过率: 见 test-results.md" points to a file that does not exist in the bundle — a minor navigation/organization gap that keeps it at anchor 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Description

83%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: explicit when-to-invoke clause with concrete trigger phrases in both Chinese and English, a clearly stated core framework, and explicit negative scope. Main gaps are a few missing common trigger variations (财富自由/财务自由/passive income) and framework-component framing rather than action framing.

DimensionReasoningScore

Specificity

The description names the domain and several concrete framework elements — "责任(押上声誉)→产权(股权/知识产权)→杠杆(无需许可的代码媒体)→避免出局" and "财富=睡觉时仍在赚钱的资产" — going well beyond the 1-2 actions of anchor 3, but it describes framework components rather than the skill's concrete actions, so it does not reach the comprehensive coverage of anchor 5.

4 / 5

Completeness

Both 'what' and 'when' are explicit and concrete: "当用户问「怎么赚钱/如何致富/该不该要期权…」时调用" is an explicit use-when clause with concrete trigger phrases, "核心理念: 财富=睡觉时仍在赚钱的资产…" states what the skill does, and "不适用于: 具体投资标的分析…" adds negative scope — matching anchor 5 exactly.

5 / 5

Trigger Term Quality

Trigger coverage is good and bilingual — "怎么赚钱/如何致富/该不该要期权" plus a dedicated Triggers line "致富/赚钱/股权/期权/杠杆/被动收入/ownership/leverage/equity" — but common natural variations like "财富自由/财务自由" and "passive income" appear only in the body, not the description, so a few natural terms are missing (anchor 4, not the comprehensive synonym coverage of anchor 5).

4 / 5

Distinctiveness Conflict Risk

The niche is clear (personal wealth structure: ownership/leverage/equity, sourced from 《纳瓦尔宝典》) and the explicit exclusion "不适用于: 具体投资标的分析、理财产品的选股建议" reduces overlap with investment-advice skills; however, broad triggers like "赚钱/致富/被动收入" could overlap with adjacent skills (e.g. long-term-compounding, productize-yourself) that are not distinguished within the description itself — minor overlap risk, anchor 4.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

kangarooking/cangjie-skill

Path

books/naval-almanack-skill/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.