CtrlK
BlogDocsLog inGet started
Tessl Logo

miloco-home-patrol

miloco-home-patrol 定时任务的内部例程,仅由该任务调用。

49

Quality

53%

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 ./plugins/skills/miloco-home-patrol/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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-engineered, highly actionable procedural skill with a clear sequenced workflow, explicit validation gates, and thorough edge-case handling. Its only weakness is mild redundancy from restating the identity red lines in multiple sections.

DimensionReasoningScore

Conciseness

The body is dense and domain-specific without explaining concepts Claude already knows, though deliberate cross-referenced repetition of the §1.3 red lines across §5.3 and §7.3 could be tightened slightly.

4 / 5

Actionability

It gives concrete executable guidance — exact CLI command ('miloco-cli home-profile list --target profile'), exact file paths, and a copy-ready log format template — with minor gaps where miloco-devices/miloco-notify skill details are external.

4 / 5

Workflow Clarity

A clear 5-step sequence with explicit ordering, early-exit conditions, three validation gates (去重/时效/身份) as checkpoints, and an exception table covering log-write failure and backlogged events.

5 / 5

Progressive Disclosure

Well-organized into numbered §1–§9 sections with consistent §-link cross-references and easy navigation; all content lives appropriately in one self-contained procedural file with no bundle files needed.

4 / 5

Total

17

/

20

Passed

Description

25%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 functions as a guard clause scoping the skill to a specific cron task but fails to communicate what the skill actually does or when it should run. It is too vague to serve as effective trigger guidance.

Suggestions

State the concrete actions the routine performs, e.g. '巡检家庭感知记忆,按档案执行设备自动化并发送关怀提醒' (inspects perception memory, runs device automation per profile, sends care reminders).

Add an explicit trigger/usage clause such as '仅由 miloco-home-patrol cron 任务调用;不在交互会话中单独使用' to make the 'when' concrete.

Include natural domain terms (巡检/家庭状态/设备控制/提醒) so the skill's purpose is recognizable rather than only the opaque task name.

DimensionReasoningScore

Specificity

The description names the domain ('miloco-home-patrol 定时任务的内部例程') but provides no concrete actions — '内部例程' (internal routine) is generic, so it sits between the vague anchor and the domain-named anchor.

2 / 5

Completeness

It states only a vague 'what' (an internal routine) and a weak 'when' ('仅由该任务调用'), with no explicit 'Use when...' trigger guidance or statement of what the routine actually does.

2 / 5

Trigger Term Quality

It contains only technical jargon ('miloco-home-patrol', '定时任务', '内部例程') with no natural keywords a user would say; this is an internal cron routine users never invoke, matching the no-natural-keywords anchor.

1 / 5

Distinctiveness Conflict Risk

Scoping to the specific named 'miloco-home-patrol' cron task makes it mostly distinct with minimal conflict risk, though the vague capability leaves minor overlap ambiguity.

4 / 5

Total

9

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.