CtrlK
BlogDocsLog inGet started
Tessl Logo

miloco-home-prune

home-dreaming 定时任务的 Prune 步骤,仅由该任务调用。

52

Quality

57%

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

Quality

Content

72%

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

The content is highly actionable with concrete CLI commands and clear examples, and is well-organized as a self-contained reference. Its main gap is the absence of an explicit validation/verification checkpoint before the destructive reassign-and-commit batch operation.

Suggestions

Add an explicit verification step before commit, e.g. re-list profiles after reassign to confirm merges applied correctly before running `commit`.

Tighten the duplicated explanation between the opening paragraph and the "主体归并" intro to remove redundant binding/cleanup prose.

Document what to inspect or roll back if a reassign merges the wrong subjects, giving the workflow a feedback loop for the destructive batch operation.

DimensionReasoningScore

Conciseness

The body is mostly dense and actionable, but the opening paragraph and the "主体归并" intro restate the binding/cleanup explanation, so it could be tightened further.

2 / 3

Actionability

It provides fully executable, copy-paste-ready `miloco-cli` commands with complete JSON `--mappings` examples for both person binding and name-only consolidation.

3 / 3

Workflow Clarity

The four-step sequence is clear with a light conditional checkpoint ("如果所有 subject 已统一,直接执行 commit"), but reassign is a batch/destructive rewrite with no explicit validation or verify-before-commit feedback loop, capping this at 2.

2 / 3

Progressive Disclosure

No bundle files are present, and the skill is a self-contained, well-sectioned document (执行步骤, 主体归并, 命名原则, Commit 维护, 注意) with no nested references, which is appropriate for its scope.

3 / 3

Total

10

/

12

Passed

Description

42%

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 identifies a distinct, narrowly-scoped cron sub-step but is written as internal jargon with no natural trigger terms and no explicit usage guidance. It is specific enough to avoid conflicts yet too vague on what the step actually does.

Suggestions

Add a brief "Use when..." clause stating when this Prune step activates within the home-dreaming flow so the trigger is explicit.

Replace jargon with at least one or two concrete actions (e.g. "merges duplicate subject names, cleans expired entries, and commits") so users know what it does.

Include natural-language terms a user might say (e.g. "剪枝", "归并主体", "清理旧数据") alongside the technical name.

DimensionReasoningScore

Specificity

The description names a concrete subsystem and operation ("home-dreaming 定时任务的 Prune 步骤") but does not enumerate the concrete actions Prune performs (binding, merging, cleanup), so it stops short of comprehensive specificity.

2 / 3

Completeness

It weakly states what the step is, but offers no explicit "Use when..." trigger guidance; "仅由该任务调用" is a restrictive constraint rather than a usage trigger, which caps completeness at 2.

2 / 3

Trigger Term Quality

The phrasing is internal technical jargon ("定时任务的 Prune 步骤", "仅由该任务调用") rather than natural keywords a user would actually say, with no common variations.

1 / 3

Distinctiveness Conflict Risk

It is tightly bound to a single named cron task and explicitly marked as not standalone, making it unlikely to trigger for the wrong skill.

3 / 3

Total

8

/

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.