CtrlK
BlogDocsLog inGet started
Tessl Logo

todo-manager

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

54

Quality

60%

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

65%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 lean, well-sectioned overview with copy-paste commands and a critically important safety principle about never pushing company docs. Its main gaps are missing operational detail (no usage examples for todo-manager.py itself) and the absence of any pre-push validation step despite the skill's own top rule being about preventing an irreversible git leak.

Suggestions

Show how to invoke each advertised function, e.g. one example command or subcommand for creating and updating a todo (arguments to todo-manager.py), not just bare invocation.

Add an explicit pre-push validation step, e.g. run a whitelist/blacklist check or `git status` review on staged files before ./todo-push.sh, turning the 第一原则 into an enforced checkpoint.

Drop the intro sentence that duplicates the frontmatter description verbatim, and fold the duplicated 核心功能 list into a single capability statement to save tokens.

DimensionReasoningScore

Conciseness

The body is lean — bare commands, no concept explanations — but the intro line restates the frontmatter description verbatim and the 核心功能 list repeats it, matching the 'minor instances of over-explanation that could be trimmed' anchor.

4 / 5

Actionability

The three command blocks are concrete and executable, but how to actually perform the advertised functions is never shown — no subcommands, arguments, or examples for creating or updating a todo — fitting the 'concrete guidance but incomplete; missing key details' anchor.

3 / 5

Workflow Clarity

Usage steps are listed, but the push workflow is explicitly destructive (leaking 公司项目 to a public repo is the stated 第一原则) and lacks any validation checkpoint such as verifying the whitelist/blacklist before pushing, so workflow clarity is capped at 3.

3 / 5

Progressive Disclosure

This is a simple skill under 50 lines with no need for external references; the sections (核心功能, 使用方法, 重要原则) are clear and well-organized, which earns 5 under the simple-skill exception.

5 / 5

Total

15

/

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 conveys a concrete 'what' with three specific capabilities scoped to a particular project, but it entirely lacks a 'when to use this skill' trigger clause, which caps completeness and weakens trigger-term quality. The trailing "等功能" is vague padding, and the wording overlaps with generic todo-management skills.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions todo tasks, 待办事项, task status, or priorities in the CS-Notes project".

Replace the vague "等功能" with the remaining concrete capabilities (e.g. push/pull sync via todo-push.sh / todo-pull.sh) so coverage is complete and specific.

Include natural synonym terms users would actually say (task, checklist, 待办, priority) rather than repeating the phrase "todo 管理".

DimensionReasoningScore

Specificity

Lists three concrete actions ("任务创建、状态更新、优先级管理" — task creation, status updates, priority management) in a named domain, matching the 'several specific actions; minor gaps' anchor; the vague trailing "等功能" keeps it below 5.

4 / 5

Completeness

The 'what' is clear (manages todo tasks in the CS-Notes project: creation, status, priority) but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Contains some natural keywords ("Todo", "todo 任务", "优先级") but misses common variations and synonyms (task, checklist, 待办) and mostly repeats the phrase "todo 管理", fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

Scoping to the named "CS-Notes 项目" gives it a niche, but the generic "Todo 管理" framing overlaps with any task-management skill and there are no distinct trigger phrases, matching the 'somewhat specific but could still overlap' anchor.

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.

Validation — 16 / 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.