priority-task-reader

按优先级读取任务 Skill - 从 todos.json 读取 in-progress 和 pending 任务，按 P0-P9 优先级排序

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.trae/openclaw-skills/priority-task-reader/SKILL.md

Quality

Content

61%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 well-structured and offers executable commands that make the skill easy to run, but it is padded by duplicated rules and large output examples, and its multi-step workflow lacks validation checkpoints. It is a solid, self-contained skill with minor organization and conciseness gaps.

Suggestions

De-duplicate the priority rules: keep one authoritative '排序规则' section and have '重要原则' reference it rather than restating P0/in-progress ordering.

Move the verbose ASCII output examples into a separate examples file and link to it, or trim them to one compact representative block.

Add explicit validation/feedback checkpoints to the '推进todo' workflow (e.g., confirm the chosen task meets Assignee: AI and Feedback Required: false before executing).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but repeats the sorting rules (rule list plus '重要原则') and inlines large ASCII output-example blocks that could be trimmed, fitting anchor 3 rather than 4.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands (python3 main.py, --json, --next, --next-count, --config) covering the common cases, matching anchor 4; minor gaps (truncated --next JSON, no internal code) keep it off 5.	4 / 5
Workflow Clarity	The '推进todo' workflow lists a sequence (call skill, select task, execute) but has no explicit validation checkpoints and leaves selection criteria vague, fitting anchor 3.	3 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections with mostly appropriate placement; the inlined large output examples and absence of bundle reference files keep it just below a 5.	4 / 5
	Total	14 / 20 Passed

Description

53%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 conveys a clear, specific purpose but omits any 'when to use' trigger guidance, which caps its completeness and limits natural trigger-term quality. It is reasonably distinct thanks to its concrete todos.json/P0-P9 framing.

Suggestions

Add an explicit 'Use when...' clause stating the natural trigger situations (e.g., when the user asks to see, sort, or pick their next task).

Include natural conversational trigger phrases users would say ('show my tasks', 'what should I work on next', 'sort tasks by priority') alongside the technical terms.

Expand the action list slightly (e.g., 'group tasks by priority and surface the next actionable one') to lift specificity toward a 4.

Dimension	Reasoning	Score
Specificity	Names the domain (reading tasks from todos.json) and two concrete actions (read in-progress/pending tasks, sort by P0-P9 priority), matching anchor 3; it does not list several distinct actions so it is not a 4.	3 / 5
Completeness	The 'what' is clear (read and sort tasks from todos.json) but there is no 'Use when...' clause or explicit trigger guidance, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant domain terms like 'todos.json', 'in-progress', 'pending', and 'P0-P9 优先级' are present but lean technical; the natural phrases a user would actually say ('sort my tasks', 'what's my next task') are missing, fitting anchor 3.	3 / 5
Distinctiveness Conflict Risk	Tying the skill specifically to todos.json and the P0-P9 priority scheme gives it a clear niche with only minor overlap risk against other task-management skills, matching anchor 4.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: huangruiteng/CS-Notes
Path: .trae/openclaw-skills/priority-task-reader/SKILL.md
Commit: 43eb317

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.