CtrlK
BlogDocsLog inGet started
Tessl Logo

miloco-home-profile

家庭档案管理 — 当用户提到自己或家人的喜好、兴趣、习惯、身体状况、作息规律、家庭规则时激活,无论用户是否明确要求"记录"。也在用户修正已有记录、要求删除、或查询家庭档案时激活。

72

Quality

90%

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

80%

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

A tightly written, highly actionable CRUD skill with exact commands and a complete entry taxonomy. Its main weakness is the absence of an explicit post-write validation/verification loop for destructive operations, and a monolithic single-file structure that keeps detailed reference material inline.

Suggestions

Add an explicit post-write verification step to the workflow — e.g., re-run `miloco-cli home-profile list --target profile` after `commit` and confirm the expected entry id appears (or was removed) before reporting success, satisfying the validate→fix→retry loop for destructive delete/replace ops.

Move the detailed reference material (the type taxonomy table, subject naming rules, and pet/composition edge cases) into a `references/taxonomy.md` file referenced one level deep from SKILL.md, keeping the main file as a lean overview + workflow.

Trim or de-duplicate the '何时激活' section against the frontmatter description, which already states the same triggers, to recover tokens while keeping the passive-scenario silent-write rule.

DimensionReasoningScore

Conciseness

The body is dense and operational — exact commands, an entry-field spec, a type table, naming rules, and write principles — with no padding explaining concepts Claude already knows. The brief intro ('记录家庭档案的目的不是"存档"…') and the passive-scenario handling earn their tokens rather than restating known ideas.

3 / 3

Actionability

It gives copy-paste-ready commands (`miloco-cli home-profile list/profile-write/commit`) plus a full bash example with a concrete JSON ops array, and maps each op (add/merge/replace/delete) to its trigger condition. Not score 2 because the guidance is complete and executable rather than pseudocode or abstract.

3 / 3

Workflow Clarity

The four-step sequence (pull full profile → judge intent → write → commit) is clear and the mandatory pre-write pull is a strong safeguard, but there is no post-write verification or validate→fix→retry loop. Because the workflow covers destructive ops (delete/replace), the rubric's cap-at-2 rule for missing feedback loops applies; not score 3 because validation checkpoints are implicit rather than explicit.

2 / 3

Progressive Disclosure

Sections are well-organized with clear headers and a taxonomy table, but the skill is a single ~104-line monolithic file with no external references, and detailed reference material (type taxonomy, subject naming rules, pet/composition edge cases) is inline rather than split out. Not score 1 because it is well-structured rather than a wall of text; not score 3 because it is over 50 lines and uses no one-level-deep reference files.

2 / 3

Total

10

/

12

Passed

Description

100%

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 well-crafted description that names the domain and concrete CRUD actions, provides explicit activation triggers covering both explicit-record and passive-mention scenarios, and occupies a clear niche. It uses third-person voice and answers both 'what' and 'when' without padding.

DimensionReasoningScore

Specificity

It lists multiple concrete actions on the family-profile object — 记录 (record), 修正 (correct), 删除 (delete), 查询 (query) — alongside the domain label 家庭档案管理, matching the 'lists multiple specific concrete actions' anchor. Not score 2 because the action set is comprehensive (full CRUD) rather than partial.

3 / 3

Completeness

It states what the skill does (家庭档案管理) and gives explicit when-guidance via '当用户提到…时激活' and '也在用户…时激活'. Both what and when are explicitly present with triggers. Not score 2 because the when-clause is explicit, not merely implied.

3 / 3

Trigger Term Quality

It enumerates natural terms a user would actually say — 喜好、兴趣、习惯、身体状况、作息规律、家庭规则 — plus 修正记录、删除、查询家庭档案, giving good coverage of phrasings users naturally produce. Not score 2 because common variations are well represented rather than missing.

3 / 3

Distinctiveness Conflict Risk

The niche is clearly scoped to family profiles and family-member preferences/habits/health/routines/rules, with distinct triggers unlikely to fire for unrelated skills. Not score 2 because the trigger set is family-profile-specific rather than broadly overlapping with generic document or identity skills.

3 / 3

Total

12

/

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.