CtrlK
BlogDocsLog inGet started
Tessl Logo

wealth-structure

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

65

Quality

79%

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 ./benchmarks/naval/prototypes/compact-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.

The body is a well-structured, actionable conceptual skill with a sequenced workflow, completion criteria, and boundary/limitation notes. It is concise and clear but has light trimmable prose and lacks the explicit validate-retry loop and quick-start/advanced split that would reach the top anchors.

Suggestions

Tighten the I (方法论骨架) and A1 case-study prose to declarative bullets to lift conciseness toward 5.

Add an explicit validate→fix→retry checkpoint in the E workflow (e.g. re-run the income-structure diagnosis after each migration and abort on red-line breach) to push workflow_clarity to 5.

Split a one-line 'Quick diagnosis' summary at the top from the deeper RIAA sections to strengthen progressive disclosure and navigation.

DimensionReasoningScore

Conciseness

The RIAA-structured body is efficient and assumes competence, but the methodology-skeleton and case-study prose contain a few explanatory sentences that could be tightened without losing meaning, placing it just below the lean 5 anchor.

4 / 5

Actionability

The E-section delivers four concrete steps with explicit '完成标准' and a '判停条件' stop guard (e.g. '回答三个问题——收入是否按时间计?有无产权?有几层杠杆?'); guidance is mostly executable with only minor gaps, below the fully copy-paste 5 anchor suited to code skills.

4 / 5

Workflow Clarity

A clearly sequenced four-step workflow carries explicit completion checkpoints and a stop-condition feedback guard, with step 4 establishing a quarterly re-run loop; it stops short of the explicit validate→fix→retry checklist pattern of the 5 anchor.

4 / 5

Progressive Disclosure

The single file is well-organized under clear R/I/A1/A2/E/B headers with no nested references and no bundle files to misroute; it exceeds the ~50-line simple-skill threshold so it does not reach the 5 anchor reserved for compact single-purpose skills.

4 / 5

Total

16

/

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.

The description is strong: it states a concrete core thesis, gives explicit trigger questions and a keyword list, and scopes out adjacent use cases. It is a conceptual skill so its 'actions' are structural levers rather than tool operations, which caps specificity just below the top.

DimensionReasoningScore

Specificity

Names the wealth-structure domain and lists several specific components ('责任(押上声誉)→产权(股权/知识产权)→杠杆(无需许可的代码媒体)→避免出局'); it is a conceptual framework rather than discrete tool actions, so it falls just below the comprehensive-action anchor of 5.

4 / 5

Completeness

It explicitly answers both 'what' ('财富=睡觉时仍在赚钱的资产' and the four-pillar construction) and 'when' ('当用户问「怎么赚钱/如何致富/该不该要期权/如何判断一个生意的结构」时调用' plus the Triggers line) with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

An explicit 'Triggers:' line surfaces natural CN and EN terms users would actually say (致富/赚钱/股权/期权/杠杆/被动收入/ownership/leverage/equity); coverage is strong with synonyms in two languages but a few common variations are missing, sitting below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

A clear niche (asset structure via ownership/leverage) with distinct triggers and an explicit '不适用于: 具体投资标的分析、理财产品的选股建议' boundary reduces conflict risk; minor overlap with adjacent finance/wealth skills keeps it just below 5.

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.

Validation15 / 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
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.