CtrlK
BlogDocsLog inGet started
Tessl Logo

miloco-miot-identity

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

60

Quality

71%

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-miot-identity/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 highly actionable with executable commands and a well-sequenced workflow that validates destructive operations, though it is somewhat repetitive and monolithic with no external reference structure.

Suggestions

Consolidate the repeated '转 register skill' boundary guidance into one authoritative section to reduce redundancy.

Consider moving the changelog (变更说明) into a separate reference file to slim the main body and improve progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly efficient and operational, but the '转 register skill' boundary is repeated across 何时激活, 异常, 边界, and 示例, and the changelog adds length that could be tightened.

3 / 5

Actionability

Concrete, copy-paste-ready miloco-cli commands with flags throughout (person add/update/delete, identity member list, sample show), and worked examples cover every common case.

5 / 5

Workflow Clarity

Clear three-step sequence (解析→执行 2a-2e→回复) with explicit 二次确认 + cascade warning on the destructive delete and an 异常 recovery table; no explicit re-validate retry loop keeps it just below 5.

4 / 5

Progressive Disclosure

No bundle files exist; the single ~225-line file is well-organized with clear section headers, but it is monolithic with nothing split into one-level-deep references.

4 / 5

Total

16

/

20

Passed

Description

67%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 states concrete capabilities and draws a sharp boundary against the register skill, but it lacks an explicit 'Use when…' trigger clause and natural trigger phrases, capping completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when…' clause with concrete user trigger phrases (e.g. '添加/删除家庭成员', '家里有哪些人') to lift completeness above 3.

Include natural synonyms and variations users actually say rather than relying on the body's routing table for trigger terms.

DimensionReasoningScore

Specificity

Lists four concrete CRUD actions (创建/列出/重命名/删除成员) plus an explicit negative boundary, giving comprehensive coverage of the skill's domain.

5 / 5

Completeness

The 'what' is clear (家庭成员档案 CRUD) but there is no explicit 'Use when…' trigger clause — only a negative boundary — so completeness is capped at 3 per the missing-trigger-guidance rule.

3 / 5

Trigger Term Quality

Contains some natural terms (录脸/录身形, 删除成员) but misses common variations and synonyms; the rich user phrasings (e.g. '家里有哪些人') live in the body rather than the description.

3 / 5

Distinctiveness Conflict Risk

Explicitly disambiguates from the sibling miloco-miot-identity-register skill, carving a clear niche (person DB CRUD) with minimal conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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