CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

productize-yourself

当用户在纠结职业/副业/自由职业方向、问「我该做什么才能赚钱/不被替代」、或想找到自己的独特优势时调用。 核心理念: 特殊知识(不可培训、对你像玩对别人像工作) × 产品化(杠杆规模化) = 无可替代的致富定位。 不适用于: 纯求职投递、写简历、已有明确方向的执行细节。 Triggers: 找方向/独特优势/副业/不可替代/productize/special knowledge/moat

Quality

73%

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/productize-yourself/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 distillation with a genuinely actionable 4-step execution workflow including a retry loop, and honest boundary sections (failure modes, author blind spots). Main deductions are for repeated adjacent-skill distinctions, audit metadata, and a dangling test-results.md reference.

Suggestions

State the adjacent-skill distinction once (keep the A2 section or the B section) and drop the other two mentions plus the audit section to tighten the token budget.

Add failure handling for steps 2–3 of the workflow (e.g., what to do when no candidate passes the uniqueness×scalability test) and one worked example of a passing special-knowledge candidate.

Fix or remove the dangling 「见 test-results.md」 reference and the unresolvable sibling-skill pointers, or move them to a properly linked references file.

DimensionReasoningScore

Conciseness

The body is mostly tight and bullet-driven, but there is redundancy and meta-padding: the adjacent-skill distinction (wealth-structure / reading-metaskill) is stated three times (A2 「与相邻 skill 的区分」, B 「容易混淆的邻近方法论」, and 「相关 skills」), and the audit section (「验证通过」「测试通过率: 见 test-results.md」「蒸馏时间」) adds tokens with no usage value. This fits anchor 3 (mostly efficient but could be tightened) rather than 4, where only minor trimming would be needed.

3 / 5

Actionability

The E section gives four concrete steps with explicit completion criteria and numeric specifics (「列出 3–5 个『对你像玩、对别人像工作』的事」「30 天内发布一个最小作品(一篇文章/一个工具/一个内容系列),公开署名」「每季度重问」) — actionable instruction-only guidance. Not a 5 because steps 2–4 rely on self-assessment questions without example prompts, templates, or worked cases of what a passing candidate looks like.

4 / 5

Workflow Clarity

The E section is a clearly sequenced 1→4 workflow with an explicit feedback loop in step 1 (「判停条件: 若找到的事可以被培训/被替代,回到步骤 1 继续找」) and a quarterly re-check loop in step 4. It misses anchor 5 because steps 2–3 have completion criteria but no failure handling — e.g., what to do if no candidate passes the uniqueness×scalability test in step 2.

4 / 5

Progressive Disclosure

A single-file skill with clean, well-labeled sections (R/I/A1/A2/E/B) and no nested references — appropriate for a ~100-line framework skill that needs no bundle files. It does not reach 5 because 「测试通过率: 见 test-results.md」 references a file that does not exist in the skill bundle (a dangling pointer), and the cross-references to sibling skills (wealth-structure, reading-metaskill, long-term-compounding) are not resolvable from this skill's directory.

4 / 5

Total

15

/

20

Passed

Description

70%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 well-formed, third-person description with an explicit trigger clause, concrete user phrasings, and clear exclusions. Its main weakness is that the 'what' is expressed as a concept formula instead of concrete actions the skill performs, and a few natural trigger synonyms (notably Chinese '护城河') are missing.

Suggestions

Convert the 'what' into action-oriented phrasing (e.g., 帮用户盘点特殊知识信号、检验独特性×可规模化、定义并发布最小产品) so the description states what the skill does, not just the concept it embodies.

Add missing natural trigger synonyms, especially the Chinese 「护城河」「职业方向」 and English 'career direction / freelance', to raise trigger coverage.

Add a one-line disambiguation against the closest sibling skill (e.g., 定位问题用本 skill, 资产结构问题用 wealth-structure) to reduce overlap on ambiguous queries like 「副业怎么赚钱」.

DimensionReasoningScore

Specificity

The description names the domain clearly and characterizes the framework with specifics (「特殊知识(不可培训、对你像玩对别人像工作) × 产品化(杠杆规模化) = 无可替代的致富定位」), but it states a concept formula rather than concrete actions the skill performs — there are no action verbs like '盘点/检验/定义定位'. It sits above anchor 2 (which would be a generic domain name with no specifics) but does not list the several concrete actions anchor 4 requires.

3 / 5

Completeness

Both what and when are present: the when is explicit and strong (「当用户在纠结职业/副业/自由职业方向、问『我该做什么才能赚钱/不被替代』...时调用」) with concrete trigger phrases, and the what is given via the core concept plus explicit exclusions (「不适用于: 纯求职投递、写简历、已有明确方向的执行细节」). The what leans on a formula statement rather than explicitly stating what the skill does for the user, keeping it below the fully explicit anchor 5.

4 / 5

Trigger Term Quality

Good bilingual coverage: 「找方向/独特优势/副业/不可替代/productize/special knowledge/moat」plus natural user phrasings embedded in the when-clause (「我该做什么才能赚钱/不被替代」「想找到自己的独特优势」). Not a 5 because a few natural terms are missing — notably the Chinese '护城河' (only the English 'moat' appears) and common variations like '职业方向/自由职业' in the trigger list itself.

4 / 5

Distinctiveness Conflict Risk

Distinctive triggers ('productize', 'special knowledge', 'moat', 「不可替代」) plus an explicit not-applicable clause carve out a clear niche from resume/job-application skills. Minor overlap risk remains with adjacent career/wealth skills (e.g., a query like 「副业怎么赚钱」 could plausibly match a wealth-structure sibling skill), which the description does not disambiguate — matching anchor 4 rather than 5.

4 / 5

Total

15

/

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/productize-yourself/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.