CtrlK
BlogDocsLog inGet started
Tessl Logo

screen-detox

当用户刷手机/短视频/社交媒体上瘾、感觉空虚、想戒断多巴胺零食时调用。 核心理念: 所有屏幕活动与更少幸福相关(作者断言无例外); 屏幕=用长期后果换短期快感的多巴胺零食; 用习惯替换五步戒断。 不适用于: 工作需要屏幕的职业场景(区分工作屏幕与消费屏幕)。 Triggers: 刷手机/上瘾/短视频/社交媒体/多巴胺/戒断/屏幕时间/screen time/dopamine/addiction

63

Quality

75%

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/screen-detox/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, actionable instruction-only skill with clear steps and a retry condition, but it carries redundant case-study and meta sections that dilute token efficiency.

Suggestions

Trim or collapse the A1 case studies and the trailing '相关 skills'/'审计信息' sections, which duplicate the frontmatter and add little executable value.

Add an explicit completion/validation checkpoint to steps 1–3 (e.g., '确认已记录满 3 天数据再进入下一步') to mirror the step-4 feedback loop and raise workflow clarity.

Consider moving the methodology detail (I section) and case studies into a reference file so SKILL.md stays a lean overview pointing one level deep.

DimensionReasoningScore

Conciseness

Mostly efficient but includes padding: the A1 case studies and the duplicated '相关 skills'/'审计信息' sections restate frontmatter content and could be tightened, and the R quote is somewhat long.

3 / 5

Actionability

The E section gives concrete, measurable steps with 完成标准 ('记录 3 天', '告诉 3 个朋友', '移出首屏/卸载/设限额'), matching mostly-executable guidance with only minor coverage gaps.

4 / 5

Workflow Clarity

Clear 1→4 sequence with an explicit feedback loop in step 4 (判停条件: '若 7 天后复发 ≥3 次,缩小目标'); steps 1–3 lack explicit validation checkpoints, so it is not a 5.

4 / 5

Progressive Disclosure

Well-organized R/I/A/E/B sections in a single file with no nested references; over 50 lines with inlined case studies keeps it just below a 5 rather than at the simple-skill ceiling.

4 / 5

Total

15

/

20

Passed

Description

82%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 well-constructed: it states a clear what, an explicit when with bilingual trigger terms, and scopes out work-screen scenarios. Its only weakness is that capabilities are framed as philosophy rather than enumerated concrete actions.

DimensionReasoningScore

Specificity

Names the domain (screen/dopamine detox) and a concrete method ('习惯替换五步戒断'), but frames capabilities philosophically ('所有屏幕活动与更少幸福相关') rather than listing multiple specific actions.

3 / 5

Completeness

Explicitly answers both what ('用习惯替换五步戒断') and when ('当用户刷手机...时调用' plus a concrete Triggers line), matching the anchor for clearly answering both with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong bilingual coverage with natural phrases and synonyms ('刷手机/上瘾/短视频/社交媒体/多巴胺/戒断/屏幕时间/screen time/dopamine/addiction'), though a few natural terms like 'doomscrolling' are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (screen detox/dopamine management) with distinct triggers, an explicit exclusion ('不适用于: 工作需要屏幕的职业场景'), and related-skill relations that minimize overlap risk.

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