CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

self-liberation

当用户被别人的期望压垮、容易愤怒、或感觉被工作/责任困住、问「怎么说不/怎么不生气/怎么更自由」时调用。 核心理念: 期望不是你的合同(约定才是); 愤怒是自我惩罚; 就业自由来自低生活成本; 自由=免于被迫反应的自由。 不适用于: 违约/欠债等真正的约定责任。 Triggers: 期望/愤怒/自由/取悦别人/说不/就业自由/freedom/anger/expectations

Quality

77%

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 ./books/naval-almanack-skill/self-liberation/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, lean instruction-only skill: concrete four-step execution guidance with completion criteria and stop conditions, clearly bounded against misuse. Its main weaknesses are a dangling reference (test-results.md), a verbatim repeated quote, a few typos, and the absence of a worked application example or error-recovery guidance.

Suggestions

Remove or fix the dangling '见 test-results.md' reference — the file does not exist in the bundle.

Fix the typos ('握煤' → '握着热煤', '在我年轻充满睾丸的时候' → likely '充满睾丸素', '等着把他扔给别人' → '把它扔给别人') and drop the verbatim duplicate of the R-section quote in A1 案例 2.

Add one short worked example (user language signal → applied 区分期望/约定 response) to lift actionability, and a recovery note for when step 2 (期望断舍离) damages a relationship.

DimensionReasoningScore

Conciseness

The body is dense and sectioned with no concept-padding (no explanation of what anger or freedom 'is' in the abstract), assuming reader competence. Minor redundancy keeps it below anchor 5: the R-section quote is repeated verbatim in A1 案例 2, and the '相关 skills' section restates the frontmatter related_skills, plus small typos ('握煤', '充满睾丸', '等着把他扔给别人').

4 / 5

Actionability

The E section provides concrete, executable guidance with explicit completion criteria — '列出你感到压力的所有「应该」,逐个标注…', '计算支出/收入比;若接近 1:1,制定 3 个月降支计划' — even including a scripted sentence to deliver ('这是你的期望,不是我的约定'). It stops short of anchor 5 because there is no worked example dialogue showing the framework applied to a real user scenario.

4 / 5

Workflow Clarity

Four clearly sequenced steps, each with an explicit checkpoint ('完成标准') and one conditional guard ('判停条件: 若涉及真实合同/债务/承诺,先履行约定再谈自由'), plus a Boundary section listing failure modes. Not anchor 5 because there is no feedback/recovery loop — e.g., what to do if the 期望断舍离 step backfires or the 3-month spending plan fails.

4 / 5

Progressive Disclosure

The ~100-line body is appropriately self-contained with well-signaled sections (R/I/A1/A2/E/B) and no nested references. The one flaw is the dangling reference '测试通过率: 见 test-results.md' — no bundle directories (references/, scripts/, assets/) or test-results.md exist, so this points to nothing.

4 / 5

Total

16

/

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 strong bilingual description with an explicit, naturally-phrased trigger section and a useful negative-scope clause. Its main gap is that the 'what' is expressed as philosophical theses rather than concrete capabilities, and a few common trigger variations are missing.

Suggestions

Rewrite the '核心理念' line with action verbs stating what the skill does, e.g. '帮助用户区分「期望」与「约定」、拆解愤怒的自我契约、评估就业自由缓冲'.

Add missing trigger variations: 拒绝/refuse, 辞职/quit, people-pleasing, boundaries/边界.

Make the what+when pairing explicit with a 'Use when…' clause in the same style as the trigger sentence.

DimensionReasoningScore

Specificity

It names the domain precisely and states specific core theses — '期望不是你的合同(约定才是); 愤怒是自我惩罚; 就业自由来自低生活成本' — but describes concepts rather than actions: no verb states what the skill actually does (区分/引导/帮助用户…). This matches anchor 3 (domain + 1-2 concrete items) rather than 4, which expects several listed specific actions.

3 / 5

Completeness

The 'when' is fully explicit with concrete trigger phrases ('当用户被别人的期望压垮、容易愤怒、或感觉被工作/责任困住、问「怎么说不」时调用'), and the 'what' is present via '核心理念: …'. It falls just short of anchor 5 because the what-side is implicit — it states the skill's theses but never enumerates what the skill does, and lacks a crisp 'Use when…' style clause tying both together.

4 / 5

Trigger Term Quality

The trigger line '期望/愤怒/自由/取悦别人/说不/就业自由/freedom/anger/expectations' covers natural terms in both Chinese and English, and the opening includes natural phrases users would say ('怎么说不/怎么不生气/怎么更自由', '被别人的期望压垮'). A few common variations are missing (拒绝/say no, 辞职/quit job, boundaries), so it sits between anchors 4 and 5 — solidly above 'a few natural terms missing' but short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The '不适用于: 违约/欠债等真正的约定责任' exclusion carves out a distinct niche and pre-empts the main confusion risk, and the trigger set is specific to the expectations/anger/freedom domain. Broad terms like 自由/freedom still overlap with adjacent emotional skills (happiness-skill, identity-work), keeping it at anchor 4 rather than 5.

4 / 5

Total

15

/

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/self-liberation/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.