CtrlK
BlogDocsLog inGet started
Tessl Logo

miloco-habit-suggest

每日习惯洞察 —— 从家庭档案识别值得建成任务的习惯,主动 IM 推荐给主人;主人认可后据此建任务。两条路径:cron 触发的【扫描推荐】(路径 A) 与用户回应触发的【回应处理】(路径 B)。防骚扰由 miloco-cli habit 状态机裁定。

69

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced skill body with concrete commands, explicit validation checkpoints, and clean one-level delegation to sibling skills. The only meaningful weakness is mild redundancy of the anti-harassment rules across sections.

Suggestions

State the 3-time-ask cap and anti-harassment limits once in 关键规则 and reference them from the inline steps to remove the repetition in 路径 A steps 2–3 and the intro quote.

DimensionReasoningScore

Conciseness

The body is mostly lean and domain-specific with no explanation of concepts Claude already knows, but the 3-time-ask cap and anti-harassment rules are restated in four places (intro quote, step 2, step 3, 关键规则 #6), which could be tightened.

2 / 3

Actionability

Provides full copy-paste-ready CLI invocations with every flag enumerated (e.g. 'miloco-cli habit record --key … --subject … --habit … --suggestion … --title … --evidence … --item-id …') plus a concrete habit→task mapping table.

3 / 3

Workflow Clarity

Path A is an explicitly ordered hard sequence (1–4) with validation checkpoints and stop conditions ('档案为空 → 停止', 'can_ask_now=false → 停止', '只有 ok:true 才 asked'); Path B enforces 'real task_id before resolve' as an error-recovery feedback loop.

3 / 3

Progressive Disclosure

A single self-contained SKILL.md organized into clear sections, delegating detail one level deep to other skills (miloco-notify, miloco-create-task) rather than inlining — appropriate structure with no nested references.

3 / 3

Total

11

/

12

Passed

Description

85%

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 specific, well-scoped description that concretely states what the skill does and distinguishes its two trigger paths. Its main weakness is reliance on technical mechanism terms rather than natural user language for triggering.

Suggestions

Add natural-language trigger terms a user might say (e.g. 'habit', 'routine', 'suggest a task', '每天提醒') alongside the cron/reply mechanism descriptions.

Consider a short 'Use when…' framing so the trigger conditions read as guidance rather than internal mechanism notes.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: '从家庭档案识别值得建成任务的习惯', '主动 IM 推荐给主人', '主人认可后据此建任务' — each is a specific behavior rather than vague abstraction.

3 / 3

Completeness

Clearly answers 'what' (identify habits, recommend via IM, build tasks on approval) and 'when' via the explicit two-path trigger guidance (cron message → 路径 A, user reply → 路径 B), which is equivalent to a 'Use when' clause.

3 / 3

Trigger Term Quality

Trigger phrasing is mechanism-based technical jargon ('cron 触发', 'miloco-cli habit 状态机', '扫描推荐/回应处理') rather than natural terms a user would actually say, so it misses common user-language variations.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — daily habit insight → suggest task creation with anti-harassment via the miloco-cli habit state machine — making it unlikely to trigger for the wrong skill.

3 / 3

Total

11

/

12

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

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository
XiaoMi/xiaomi-miloco
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.