miloco-notify

需要主动触达家庭成员时使用——感知告警、危险预警、任务到期、定时播报、设备反馈、关怀提醒等一切「主动告知 / 通知 / 触达」的场景。负责决策：通知给谁 → 走哪个渠道（音箱 TTS / IM / 米家推送）→ 写什么文案 → 交付执行。只要不是被动回答用户当前的提问、而是系统或 agent 要主动找人，就加载本 skill。用户想配置 / 绑定 / 解绑通知接收渠道时也走本 skill（见 references/channel-config.md）。

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

86%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 highly actionable, well-structured skill body with concrete commands, worked examples, and strong termination discipline for an irreversible-notification task. The main improvement is consolidating the triple-reinforced no-probe/no-loop rule and adding an explicit pre-send decision checkpoint.

Suggestions

Consolidate the no-dry-run / no-probe / no-loop rule into a single canonical statement; have the other two locations reference it rather than restate it.

Add an explicit pre-send validation checkpoint in the 工作流 (e.g. a 'confirm decision' step between 选渠道/写文案 and 交付执行) to complement the existing post-send termination discipline.

Consider extracting the per-channel 文案示例 table into references/ once the examples grow, to keep the main body as a lean decision overview.

Dimension	Reasoning	Score
Conciseness	Dense, decision-packed content that assumes Claude's intelligence (no padding about what TTS/IM are), but the no-dry-run/no-probe/no-loop rule is restated in 重要原则 #4, the 交付执行 note, and 注意事项 #6, which is deliberate but trimmable repetition.	4 / 5
Actionability	Provides concrete executable commands (miloco-cli notify push --text, miloco_im_push(message=...)), explicit skill handoff for TTS, per-channel format tables, and worked same-event examples across all three channels with the placeholder rule clearly stated.	5 / 5
Workflow Clarity	Clear 6-step sequence with decision tables at each branch and explicit post-send termination/downgrade feedback loops (needsBind, ok=false) appropriate for an irreversible skill, but there is no explicit pre-send validation checkpoint gating 交付.	4 / 5
Progressive Disclosure	SKILL.md is a well-organized overview; channel-config detail is split one level deep into references/channel-config.md (a real file) via clearly signaled links, and TTS device handling is delegated to the separate miloco-devices skill rather than inlined.	5 / 5
	Total	18 / 20 Passed

Description

92%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, specific description that concretely states the decision chain it owns and gives explicit positive and negative trigger guidance. Minor room to add a few more natural synonyms, but it clearly answers what and when.

Dimension	Reasoning	Score
Specificity	Names the domain (主动触达家庭成员) and the full concrete decision chain — 通知给谁 → 走哪个渠道（音箱 TTS / IM / 米家推送）→ 写什么文案 → 交付执行 — listing multiple specific actions with comprehensive coverage.	5 / 5
Completeness	Explicitly answers both 'what' (the decision chain it owns) and 'when' with concrete triggers (主动触达、系统/agent 要主动找人、配置/绑定/解绑渠道), including an explicit negative boundary (不是被动回答用户提问).	5 / 5
Trigger Term Quality	Includes natural trigger phrases users would say (告警、危险预警、提醒、通知、主动找人、定时播报、关怀提醒) plus an explicit negation trigger, but a few natural synonyms (e.g. 播报、推送的口语说法) are not exhaustively covered.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (proactive family notification) with distinct triggers and an explicit boundary against the most likely conflict case (passive answers to the current user question), giving minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: XiaoMi/xiaomi-miloco
Path: plugins/skills/miloco-notify/SKILL.md
Commit: 095782d

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.