miloco-miot-identity

家庭成员档案 CRUD —— 创建/列出/重命名/删除成员。**身份样本注册(给某人录脸/录身形)走 miloco-miot-identity-register,本 skill 不做。**

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/skills/miloco-miot-identity/SKILL.md

Quality

Content

77%

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

The body is highly actionable with exact commands and clearly sequenced workflows that include a destructive-delete confirmation, but it is a verbose monolith that repeats the register handoff many times and buries dated changelog info inline.

Suggestions

Collapse the repeated register-skill handoff into one canonical routing rule and remove the restatements in 异常/示例/边界.

Move the v2.0/v2.1 变更说明 changelog into a separate references/CHANGELOG.md or a clearly marked deprecation section to cut inline time-sensitive bulk.

Split the detailed examples and routing table into reference files so SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the register-skill handoff is restated 6+ times (何时激活/关键规则/异常/示例/边界) and the dated v2.0/v2.1 变更说明 adds time-sensitive bulk inline.	2 / 3
Actionability	Provides exact `miloco-cli person add --name … --role …` commands with flags, example JSON responses, and copy-paste reply templates — fully executable and copy-paste ready.	3 / 3
Workflow Clarity	A numbered 三步 workflow (解析意图→执行 2a-2e→回复) with an explicit 二次确认 checkpoint for the destructive delete and a clear list→per-person sequence for the 2e status view.	3 / 3
Progressive Disclosure	Well-organized into clear sections, but it is a ~210-line single-file monolith with no bundle/reference files; the changelog and detailed examples stay inline rather than being split out.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 states concrete CRUD actions and cleanly distinguishes the skill from its sibling register skill, but it lacks a positive 'Use when…' trigger clause and leans on formal verbs over natural user phrasings.

Suggestions

Add a positive 'Use when…' clause with natural user triggers, e.g. 'Use when adding/listing/renaming/deleting family members — 添加我爸叫张三, 家里有哪些人'.

Swap formal verbs for the natural terms users say (添加/查看/改名/删除) to raise trigger-term quality.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — '创建/列出/重命名/删除成员' — matching the score-3 anchor of enumerating several concrete actions rather than vague language.	3 / 3
Completeness	States what it does (CRUD) and a negative trigger ('身份样本注册…走 miloco-miot-identity-register,本 skill 不做'), but has no positive 'Use when…' clause, which caps completeness at 2 per the guideline.	2 / 3
Trigger Term Quality	Uses formal action verbs ('创建/列出/重命名/删除成员') but omits the natural phrasings users actually say ('添加我爸叫张三', '家里有哪些人') that only appear in the body, so coverage of natural terms is partial.	2 / 3
Distinctiveness Conflict Risk	Carves out a clear person-DB-CRUD niche and explicitly redirects the overlapping sample-registration case to miloco-miot-identity-register, making wrong-skill triggering unlikely.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning
relative_links	Relative link issues: 2 suspicious	Warning

	Total	14 / 16 Passed

Repository: XiaoMi/xiaomi-miloco
Path: plugins/skills/miloco-miot-identity/SKILL.md
Commit: f156d34

Reviewed: 2 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.