CtrlK
BlogDocsLog inGet started
Tessl Logo

miloco-home-promote

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

56

Quality

65%

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

Quality

Content

87%

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

The body is a lean, actionable operational guide with real CLI commands, a worked example, and a clear decision table. Its main weakness is the absence of validation/feedback steps for the destructive, batch-capable profile-write operation, which caps workflow clarity.

DimensionReasoningScore

Conciseness

The body is lean and operational — a one-line purpose, three terse steps, a compact decision table, and a single worked command, with no padding or explanation of concepts Claude already knows. Not 2 because there is no unnecessary explanation or text that could be tightened; every section earns its place.

3 / 3

Actionability

Provides real executable commands (`miloco-cli home-profile list --target both`, `profile-write --ops '[...]'`) and a complete, copy-paste-ready ops JSON example with a realistic entry. The decision table maps each relationship to concrete ops with required fields; not 2 because it is executable code rather than pseudocode, though only the `add` op is fully exemplified.

3 / 3

Workflow Clarity

Steps are clearly sequenced (list → analyze relationship → profile-write) with a decision table and a conservative-skip guard for unresolved conflicts. Not 1 because the sequence and decision logic are explicit; not 3 because there is no validation/verification step or error-recovery feedback loop after the destructive, batch-capable `profile-write` (which auto-deletes candidates), and the guidelines cap such workflows at 2.

2 / 3

Progressive Disclosure

At ~43 lines with no bundle files and no external references, the skill is organized into clear sections (执行步骤, 提升决策, 矛盾裁决参考, 注意) with headers and a table. Per the sub-50-line simple-skill guideline, well-organized sections score 3; not 2 because there is no inline bloat to split out and no references to manage.

3 / 3

Total

11

/

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 clearly scopes the skill to a single internal cron task with low conflict risk, but it is an identity/scope statement rather than a capability description: it names no concrete actions and contains no natural user-facing trigger terms or explicit 'Use when' guidance.

Suggestions

Add concrete action verbs describing what the step does, e.g. 'Promotes ready candidate knowledge into the formal area via add/merge/replace ops' to lift specificity.

Include an explicit 'Use when...' clause (or equivalent trigger guidance) so the 'when' is stated as a trigger, not just a restriction — this would raise completeness.

Add at least one natural-language keyword a user could say (e.g., 'home profile promotion', 'candidate knowledge curation') alongside the internal jargon to improve trigger-term quality.

DimensionReasoningScore

Specificity

Quotes "home-dreaming 定时任务的 Promote 步骤" name a concrete domain niche rather than vague boilerplate, but the description lists no concrete action verbs (e.g., promote/merge/replace), only an identity label. Not 1 because the scoped domain is specific, not vague; not 3 because there is no list of multiple specific concrete actions.

2 / 3

Completeness

It states what it is ("Promote 步骤") and a restrictive when ("仅由该任务调用"), so both are present but weak. There is no explicit 'Use when...' trigger guidance, which per the guidelines caps completeness at 2; not 3 for that reason, not 1 because both what and when are stated.

2 / 3

Trigger Term Quality

Terms like "home-dreaming", "Promote 步骤", and "定时任务" are internal system identifiers, not keywords a user would naturally say to invoke this skill. Matches the 'No natural keywords; technical jargon' anchor; not 2 because none of the terms are natural user-language variations.

1 / 3

Distinctiveness Conflict Risk

The exclusivity clause "仅由该任务调用" pins the skill to one specific cron task, giving it a clear niche with minimal conflict risk. Not 2 because it is more than 'somewhat specific' — it is explicitly scoped to a single internal caller; the trigger is internal rather than user-facing but conflict risk is genuinely low.

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.