CtrlK
BlogDocsLog inGet started
Tessl Logo

hourly-rate-time

当用户纠结时间分配、问「这个琐事/外包值不值」「怎么安排时间」「离财务自由还差什么」时调用。 核心理念: 给时间定一个高得离谱的时薪, 低于时薪的事外包或不做; 退休=不为想象中的明天牺牲今天; 不随收入升级生活方式。 不适用于: 需要享受慢节奏的时刻(休息/家庭时间按定义不是浪费)。 Triggers: 时薪/时间管理/外包/琐事/排队/财务自由/退休/hourly rate/delegate

67

Quality

81%

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

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.

A well-structured R-I-A-A2-E-B framework with concrete execution steps and clear boundaries, evaluated as an instruction skill. It loses points mainly to book-case retelling and audit-metadata noise rather than to structural problems.

Suggestions

Trim the A1 book-case retellings and the 审计信息 footer (验证通过/蒸馏时间) to reduce tokens and remove time-sensitive noise, or move audit info to a separate file.

Make step 5 ('重算自由进度') executable by giving an explicit formula or template for the 被动收入/支出 ratio rather than leaving it as '计算…比值'.

Either create the referenced test-results.md or remove the dangling '见 test-results.md' link so navigation references all resolve.

DimensionReasoningScore

Conciseness

The core methodology (I/E/B) is lean, but the A1 section retells two book cases in detail that overlap with I, and the 审计信息 footer (验证通过, 蒸馏时间: 2026-08-01) adds time-stamped metadata noise that could be trimmed.

3 / 5

Actionability

The E section gives five concrete numbered steps each with a 完成标准 and step 1 with a 判停条件, but steps like '计算被动收入/支出比值' stay conceptual rather than giving a ready-to-run formula.

4 / 5

Workflow Clarity

Five steps are clearly sequenced with completion-criteria checkpoints and an explicit stop condition on step 1; later steps lack error-recovery feedback loops, keeping it just below a 5.

4 / 5

Progressive Disclosure

The body is well organized into labeled R/I/A1/A2/E/B sections and is appropriately self-contained for a single-purpose skill, though the dangling '见 test-results.md' reference (file absent) and audit footer are minor organization blemishes.

4 / 5

Total

15

/

20

Passed

Description

95%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 tight, well-structured description that concretely states what the skill does and when to invoke it, with rich natural trigger terms and an explicit anti-trigger boundary. Voice stays third-person and there is no vague padding.

DimensionReasoningScore

Specificity

Names the domain (time valuation) and several concrete behaviors — '给时间定一个高得离谱的时薪', '低于时薪的事外包或不做', '不随收入升级生活方式' — with only minor coverage gaps versus a fully comprehensive action list.

4 / 5

Completeness

It explicitly answers 'what' (the 核心理念 block) and 'when' ('当用户纠结时间分配、问…时调用' plus the explicit Triggers line) with concrete trigger phrases, satisfying both halves.

5 / 5

Trigger Term Quality

The Triggers line covers '时薪/时间管理/外包/琐事/排队/财务自由/退休/hourly rate/delegate' plus natural user phrasings like '这个琐事/外包值不值' and '怎么安排时间', spanning synonyms and both languages.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (pricing time via an absurd hourly rate to drive delegation/retirement decisions) with specific triggers and an explicit '不适用于' boundary, minimizing overlap with adjacent skills.

5 / 5

Total

19

/

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.