CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

decision-heuristics

当用户在重大选择上纠结(换工作/买房/搬城/合伙/结婚)、列了利弊表还是拿不定主意时调用。 核心理念: 无法决定就答否; 三个重大决定(住哪/和谁/做什么)值得花一两年; 两个均等选择选短期更痛苦的路。 不适用于: 日常琐碎选择(晚饭吃什么)、信息查询。 Triggers: 纠结/拿不定主意/要不要/该不该/利弊/decision/hesitate/should I

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

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, appropriately sized advisory skill body: lean sections, concrete heuristics, execution steps with explicit completion criteria and stop conditions, and honest boundary/limitation analysis. The main deductions are duplicated trigger/adjacent-skill content across sections and a dangling test-results.md reference pointing to a nonexistent bundle file.

Suggestions

Remove or resolve the dangling reference 「测试通过率: 见 test-results.md」 — either ship test-results.md in the bundle or drop the line, since a reference to a nonexistent file breaks navigation.

Deduplicate the trigger material: the A2 section (触发场景/语言信号) and the 与相邻 skill 的区分 in A2 largely restate the frontmatter description and are repeated again in B (容易混淆的邻近方法论); consolidate into one location to tighten token use.

Add one short worked example in the E section (e.g., a fictional 跳槽 vs 留下 choice walked through the decision gate and short-term-pain test) to move the guidance from concrete to fully executable.

DimensionReasoningScore

Conciseness

The R/I/A/E/B structure is tight and each section carries weight (verbatim source quote, distilled heuristics, execution steps with completion criteria, boundaries), with no padding explaining concepts Claude already knows. It is not a 5 because the A2 trigger scenarios and language signals largely duplicate the frontmatter description, and the adjacent-skill distinctions appear twice (A2 与相邻 skill 的区分 and B 容易混淆的邻近方法论) — minor repetition that could be tightened.

4 / 5

Actionability

The E section gives four numbered steps, each with a completion criterion (完成标准) and one stop condition (判停条件: 若选项不等……直接排除差的,不套启发式), plus concrete thresholds like 「住哪/和谁/做什么」类(锁定 ≥5 年)and a 1–2 年调研窗口. As an instruction-only skill the guidance is concrete and executable, but the steps are judgment heuristics without worked examples of applying them to a real choice, keeping it at anchor 4 rather than fully-executable anchor 5.

4 / 5

Workflow Clarity

The four E steps are clearly sequenced with explicit gates: step 1 gates whether the skill applies at all, step 2 gives a default action (答否) with an escape hatch (除非有非常确定的新证据), and step 3 has an explicit stop condition for non-equal options. This is not a destructive/batch operation, so no validation feedback loop is required; the per-step 完成标准 serve as checkpoints with only minor gaps, matching anchor 4 rather than the feedback-loop-rich anchor 5.

4 / 5

Progressive Disclosure

The body (~110 lines) is appropriately inline at this scale with clear, well-signaled section headers and a logical R→I→A→E→B flow; cross-skill pointers (judgment-training, acceptance, hourly-rate-time) are clearly labeled. The one real defect is a dangling reference: 测试通过率: 见 test-results.md points to a file that does not exist in the bundle — a minor navigation gap that holds this at anchor 4 (minor organization gaps) rather than 5.

4 / 5

Total

16

/

20

Passed

Description

91%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, well-scoped description: concrete domain examples, an explicit dual-language trigger list, a clear statement of the three heuristics, and an explicit exclusion clause. The only gaps are that the 'what' reads slightly more as philosophy than as a complete inventory of skill behaviors, and minor overlap risk with general decision-support skills.

DimensionReasoningScore

Specificity

The description names the domain (major life choices: 换工作/买房/搬城/合伙/结婚) and lists the three concrete heuristics the skill delivers (「无法决定就答否」「三个重大决定值得花一两年」「两个均等选择选短期更痛苦的路」). It is a few concrete actions short of comprehensive — the heuristics are principles rather than a full inventory of what the skill does — matching anchor 4 rather than 5.

4 / 5

Completeness

It explicitly answers both questions: 当用户在重大选择上纠结……列了利弊表还是拿不定主意时调用 gives a concrete 'when' with trigger phrases, and 核心理念 plus the three heuristics give a clear 'what', further sharpened by an explicit 不适用于 exclusion clause. This matches the anchor-5 example structure (what + when with concrete trigger phrases).

5 / 5

Trigger Term Quality

An explicit Triggers line covers natural synonyms in both Chinese and English: 纠结/拿不定主意/要不要/该不该/利弊/decision/hesitate/should I. These are exactly the phrases a stuck user would say, and bilingual synonym coverage matches the comprehensive-synonyms anchor; it cannot be the 4 anchor because almost no common phrasing of this need is missing.

5 / 5

Distinctiveness Conflict Risk

The domain (重大人生选择纠结) and the explicit 不适用于 exclusions (日常琐碎选择、信息查询) make it mostly distinct with a clear niche. Minor overlap remains with generic decision-analysis or pros/cons skills, so it fits anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

18

/

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/decision-heuristics/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.