CtrlK
BlogDocsLog inGet started
Tessl Logo

todo-finder

从 todos.json 和归档中以多种匹配方式查找 todo

66

Quality

78%

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-finder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured, lean, and highly actionable, with executable examples, clear sequencing, and a verified script reference. It is a strong, simple-purpose skill body that meets the rubric's top anchors across all dimensions.

DimensionReasoningScore

Conciseness

The body is lean with no padding of concepts Claude already knows; each section earns its tokens, with only a near-verbatim repeat of the description in the intro as a minor imperfection.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands with a complete flag list and concrete example values, and the referenced script is verified to exist.

3 / 3

Workflow Clarity

A clear three-step sequence is given for a simple, non-destructive search task where the single action is unambiguous, so the top anchor applies without needing validation checkpoints.

3 / 3

Progressive Disclosure

Content is organized into clearly headed sections (适用场景, 使用步骤, 匹配方式, 输出格式, 示例) with a single, verified one-level script reference and no nested references.

3 / 3

Total

12

/

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, distinctive niche (finding todos in a specific data store) but is hampered by vague capability phrasing and a complete absence of explicit trigger guidance. Adding a 'Use when...' clause and naming concrete match types would lift specificity and completeness.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user wants to find or filter todos by ID, title, keyword, status, priority, or assignee.'

Replace the vague '多种匹配方式' with the concrete matching capabilities (by ID, title, keyword, status, priority, assignee, archived) so specificity reaches the top anchor.

Broaden natural trigger terms beyond '查找' to common user phrasings like '搜索', '筛选', or '找待办'.

DimensionReasoningScore

Specificity

Names the concrete data sources (todos.json and archives) and the find action, but '多种匹配方式' is vague rather than listing specific matching actions, so it is not comprehensive.

2 / 3

Completeness

Clearly states what the skill does but provides no 'Use when...' trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Includes relevant keywords like '查找 todo' and 'todos.json', but '多种匹配方式' is internal phrasing and common natural variations (e.g. searching or filtering by status) are missing.

2 / 3

Distinctiveness Conflict Risk

Scoping to a specific store (todos.json plus archives) and the todo entity gives it a clear niche unlikely to conflict with unrelated skills.

3 / 3

Total

9

/

12

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.