todo-manager

Todo 管理 - 管理 CS-Notes 项目中的 todo 任务，包括任务创建、状态更新、优先级管理等功能。

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.trae/openclaw-skills/todo-manager/SKILL.md

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 concise and actionably concrete with executable commands and clear organization, but the workflow around the destructive git-push lacks explicit validation checkpoints, which caps workflow clarity at 2.

Suggestions

Add an explicit validate-before-push step in the workflow, e.g. run a whitelist/blacklist check (confirm '公司项目/' is excluded) before executing todo-push.sh, and a re-check loop if validation fails.

Sequence the 使用方法 section as an ordered workflow (run todo-manager.py → validate → push/pull) rather than three independent command blocks so the intended process is unambiguous.

Replace the verbatim restatement of the description in the opening line with a more compact contextual lead-in to remove redundancy.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it lists features and gives direct executable commands without explaining basic concepts, so every token earns its place; only a minor redundant restatement of the description keeps it from feeling padded.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands with specific absolute paths ('cd /root/.openclaw/workspace/CS-Notes/Notes/snippets/' and 'python3 todo-manager.py', './todo-push.sh', './todo-pull.sh').	3 / 3
Workflow Clarity	Commands are presented as separate labeled sections, but there is no sequenced workflow with validation checkpoints, and since the operations involve a destructive git-push the missing validate-before-proceed feedback loop caps workflow clarity at 2 per the judging notes.	2 / 3
Progressive Disclosure	This is a short single-purpose skill (under 50 lines) with no external bundle files needed; its well-organized sections (核心功能, 使用方法, 重要原则) satisfy the simple-skills note allowing a score of 3 without external references.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 and a distinct niche, but lacks an explicit 'Use when...' trigger clause and only partially enumerates its capabilities, capping completeness and trigger-term quality at 2.

Suggestions

Add an explicit trigger clause, e.g. 'Use when managing todo tasks in the CS-Notes project — creating, updating, prioritizing, or tracking task status.'

Enumerate concrete actions explicitly (create, read, update, delete tasks; set priority high/medium/low; transition status todo/in-progress/done) to lift specificity from 2 to 3.

Include common natural-language variations users might say ('to-do list', 'task tracking', 'task status') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names a clear domain (CS-Notes todo) and several concrete actions ('任务创建、状态更新、优先级管理'), but the actions are summarized rather than a comprehensive enumerated list, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	Clearly states what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Contains relevant natural terms ('todo 任务', 'CS-Notes', '优先级') but misses common variations a user might say (e.g. 'to-do list', 'task tracking'), fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Scoped specifically to the CS-Notes project's todo system with a distinct niche ('管理 CS-Notes 项目中的 todo 任务'), making it unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 12 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/todo-manager/SKILL.md
Commit: a2e95c0

Reviewed: about 15 hours 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.