CtrlK
BlogDocsLog inGet started
Tessl Logo

todo-manager

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

56

Quality

63%

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 ./.trae/openclaw-skills/todo-manager/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 content is concise and actionable with executable commands and clear organization, but the git-push workflow lacks explicit validation/verification steps despite involving a destructive batch operation. Progressive disclosure is appropriate for such a compact, single-purpose skill.

Suggestions

Add a verification step before/after todo-push.sh (e.g. confirm the whitelist/blacklist is respected, run a dry-run, or check the staged file list) since pushing is a destructive batch git operation.

Clarify how the three scripts relate as a workflow (e.g. edit via todo-manager.py, then pull/push to sync) rather than listing them as isolated commands.

Remove the duplicated first body line that restates the description verbatim to tighten the opening.

DimensionReasoningScore

Conciseness

The body is lean — sectioned functions, concrete bash commands, and short principles — with only minor padding such as the repeated intro line duplicating the description.

4 / 5

Actionability

Provides concrete, executable commands (python3 todo-manager.py, ./todo-push.sh, ./todo-pull.sh) with minor gaps around expected arguments, flags, or example output.

4 / 5

Workflow Clarity

Commands are listed as independent steps with no sequencing or validation checkpoints; because todo-push.sh is a batch/destructive git operation, the missing verify-step caps this at 3.

3 / 5

Progressive Disclosure

A short (<50 line), self-contained skill with no external reference files needed and clear sections (核心功能, 使用方法, 重要原则), satisfying the simple-skill exception.

5 / 5

Total

16

/

20

Passed

Description

55%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 states concrete capabilities but omits any explicit "when to use" trigger guidance, which limits its completeness and trigger-term quality. It is reasonably specific to a project context yet remains a fairly generic todo-management trigger.

Suggestions

Add an explicit 'Use when...' clause naming the natural situations or user phrases that should trigger this skill (e.g. 'Use when managing todos in the CS-Notes project, creating/updating tasks, or adjusting priorities').

Include common synonyms and natural phrasings users might say (e.g. 'task list', '待办', 'mark task done') to improve trigger term coverage.

Tighten distinctiveness by leading with the CS-Notes-specific scope so it is less likely to compete with generic todo skills.

DimensionReasoningScore

Specificity

Lists several concrete actions — "任务创建、状态更新、优先级管理" — within the todo-management domain, with only minor implied gaps via "等功能".

4 / 5

Completeness

Provides a clear "what" (manage CS-Notes todo tasks) but has no "Use when..." or equivalent trigger clause, capping completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Includes relevant keywords like "Todo 管理", "任务", "创建", "状态更新", "优先级" but lacks common variations, synonyms, or natural user phrasings.

3 / 5

Distinctiveness Conflict Risk

Scoping to the CS-Notes project adds some specificity, but "todo management" is a broad category that could overlap with other task-tracking skills.

3 / 5

Total

13

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
huangruiteng/CS-Notes
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.