CtrlK
BlogDocsLog inGet started
Tessl Logo

miloco-terminate-task

任务终止 —— 用户主动取消或任务到期时触发,调 `miloco-cli task delete --reason X` 一笔走完 backend(写 task_terminate_log + 删 task,FK CASCADE 同步清 rule / cron / task_record_* 主表/子表),顺序跑返回的 agent_pending 让 openclaw 老通路 external cron 一并下线。

68

Quality

82%

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

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

A strong, highly actionable destructive-operation skill with clear sequencing, validation gates, and feedback loops. The only real weakness is mild redundancy of a few critical invariants that could be consolidated.

DimensionReasoningScore

Conciseness

Largely efficient operational prose assuming domain competence, but a few critical invariants are repeated across sections (FK CASCADE clearing, the 'agent_pending is cron-only' point) and could be tightened into a single canonical statement.

4 / 5

Actionability

Fully executable guidance throughout — concrete commands (`miloco-cli task delete/get/disable`, OpenClaw cron `action=remove`), exact return structures in jsonc, a complete output schema, and a fully worked end-to-end example covering all three user-response branches.

5 / 5

Workflow Clarity

A destructive operation with an explicitly sequenced 0→1→2→3 workflow, a pre-delete confirmation gate, 404/noop handling, acceptance criteria, a failure-handling table, and a feedback loop (status=partial/failed → system.failureAlert for archive_maintenance rescan) — validation checkpoints are present, so the destructive cap does not apply.

5 / 5

Progressive Disclosure

Well-organized single-file skill with clear section headers (何时激活, 第零/一/二/三步, 输出格式, 验收标准, 失败处理, 关键约定, 示例); no bundle files exist and none are clearly needed for this CLI-driven workflow, so it stays appropriately monolithic with minor structural redundancy.

4 / 5

Total

18

/

20

Passed

Description

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

A dense, technically specific description that conveys both the what and the when with strong distinctiveness. Its main weakness is trigger-term naturalness — it uses formal system vocabulary rather than the phrases users actually say.

Suggestions

Add an explicit 'Use when the user says things like 「不喝了/不记药了/取消那个监控」 or when a recurring task reaches its valid_until expiry' clause to raise completeness and trigger-term quality.

Surface 1-2 natural user-facing synonyms (取消/到期) alongside the formal trigger-source terms so the description matches how users actually phrase the request.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in one sentence — calls `miloco-cli task delete --reason X`, writes `task_terminate_log`, deletes task with FK CASCADE clearing of rule/cron/task_record_*, and sequentially runs `agent_pending` to retire external cron — comprehensive coverage of the operational mechanics.

5 / 5

Completeness

Clearly answers 'what' (the full transactional flow) and provides an equivalent 'when' ('用户主动取消或任务到期时触发'), but the 'when' is tied to system trigger sources rather than an explicit 'Use when...' clause with concrete user-facing trigger phrases.

4 / 5

Trigger Term Quality

It names the trigger conditions '用户主动取消' and '任务到期', which are relevant but somewhat formal; it lacks the natural phrasings a user would actually say (e.g. '不喝了/取消那个监控') and common synonyms that appear only in the body.

3 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (task termination via a specific `miloco-cli task delete` command) with distinct, narrow triggers; minimal risk of conflicting with other skills.

5 / 5

Total

17

/

20

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.