CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cron

仅在需要未来定时执行或周期执行任务时,使用本 skill。使用 qwenpaw cron list/create/get/state/update/pause/resume/delete/run 管理任务,并始终显式传入 --agent-id。

64

Quality

80%

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 ./src/qwenpaw/agents/skills/cron-zh/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 a strongly actionable CLI reference: complete, executable command examples covering the common creation cases, a clear minimal workflow, and real validation checkpoints (confirm-before-create, list-before-mutate, the requires_review gate). Its weaknesses are redundancy — the --agent-id mandate and usage criteria each repeat 3–4 times across sections — and the absence of a failure-recovery loop around job execution.

DimensionReasoningScore

Conciseness

The writing is lean and command-centric (cron expressions are shown, not explained), but key rules are repeated across sections: the mandatory --agent-id appears in 决策规则, 硬规则, 常见错误 and 使用建议, and the use/don't-use criteria are restated in 错误1 and 错误3. More than minor tightening is possible.

3 / 5

Actionability

Four complete, copy-paste-ready `qwenpaw cron create` examples cover text/agent task types across cron and scheduled forms (one-off and repeating with --repeat-end-type count), plus explicit --timeout guidance and pre-creation flag checklists. Only trivial gaps remain (the job_spec.json format is never shown).

5 / 5

Workflow Clarity

The 最小工作流 gives a clear 6-step sequence, backed by a pre-creation confirmation checklist and look-before-you-delete guidance (错误4) that validates the destructive operations. Not 5 because there is no explicit validate→fix→retry feedback loop for failed executions — `cron state` is mentioned for troubleshooting but not wired into a recovery flow.

4 / 5

Progressive Disclosure

No bundle files exist; the ~290-line body is well-sectioned (什么时候用 / 硬规则 / 常用命令 / 创建任务 / 最小工作流 / Cron 表达式示例 / 常见错误) with no buried or nested references. It exceeds the 50-line simple-skill case and inlines the full example gallery, so not 5, but placement and navigation are solid.

4 / 5

Total

16

/

20

Passed

Description

78%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 is concise and well-anchored: it names the exact tool, enumerates every management subcommand, and opens with an explicit 'only use when future-scheduled or periodic execution is needed' clause. Its main gap is that the 'when' condition stays abstract rather than quoting concrete trigger phrasings (e.g., daily/hourly/repeat requests), which keeps completeness and trigger coverage at the good-but-not-excellent level.

DimensionReasoningScore

Specificity

"使用 qwenpaw cron list/create/get/state/update/pause/resume/delete/run 管理任务" names the tool and all nine concrete management subcommands. Anchor 4 rather than 5 because it never says what created jobs actually do (e.g., send fixed messages or run agent queries).

4 / 5

Completeness

Both parts are explicit: "仅在需要未来定时执行或周期执行任务时,使用本 skill" (when) and "使用 qwenpaw cron ... 管理任务" (what). Not 5 because the 'when' clause states the condition without concrete trigger phrases users would say.

4 / 5

Trigger Term Quality

"未来定时执行" and "周期执行" plus "cron" are natural trigger phrases, but common user phrasings like "每天/每小时" (daily/hourly) or "提醒" (remind me) appear only in the body, not the description — good coverage with a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche — scheduled-job management tied to the named qwenpaw cron CLI with distinct scheduling triggers — making it unlikely to fire for unrelated skills. Minimal conflict risk.

5 / 5

Total

17

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

agentscope-ai/QwenPaw

Path

src/qwenpaw/agents/skills/cron-zh/SKILL.md

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.