CtrlK
BlogDocsLog inGet started
Tessl Logo

todo-finder

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

62

Quality

73%

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

93%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 concise, highly actionable instruction skill with executable command examples and a real supporting script, well-organized for a simple single-purpose task. The only minor gap is the absence of an explicit verification step, which is not critical for a read-only search operation.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned with no padding or explanation of concepts Claude already knows; every section (适用场景, 使用步骤, 匹配方式, 输出格式, 示例) earns its place, matching the 'lean and efficient' anchor.

5 / 5

Actionability

It provides fully executable, copy-paste-ready commands referencing the real script (scripts/todo_finder.py) and covers the common matching cases with concrete examples, matching the top anchor.

5 / 5

Workflow Clarity

The 3-step sequence (prepare query, run script, read results) is unambiguous for this read-only single-purpose skill; it lacks an explicit validation checkpoint but none is needed for read-only search, placing it just below 5.

4 / 5

Progressive Disclosure

At under 50 lines with a single task and a correctly referenced bundle script, the simple-skill exception applies and the well-organized sections meet the top anchor without needing external references.

5 / 5

Total

19

/

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 states a clear 'what' with a concrete domain and matching-method action, but omits any 'when to use it' trigger guidance, which caps completeness and limits trigger-term quality. It is reasonably distinct from other skills.

Suggestions

Add an explicit 'Use when...' trigger clause in the description, e.g. 'Use when the user asks to find, search, or look up todos by ID, title, keyword, status, priority, or assignee.'

Include natural synonyms and file/format terms users might say (e.g. 'todos', 'task list', 'todos.json', 'archive') to improve trigger-term coverage.

Briefly enumerate the matching dimensions (by ID, title, keyword, status, priority, assignee) in the description to raise specificity toward a 4-5.

DimensionReasoningScore

Specificity

Names the domain (todos.json and archives) and one concrete action (lookup with multiple matching methods), matching the 'names domain and 1-2 concrete actions' anchor; it does not list several specific actions so it is not a 4.

3 / 5

Completeness

It clearly states what the skill does but provides no explicit 'when to use it' trigger clause; per the rubric guidelines a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant keywords (todos.json, 归档, 查找) but lacks synonyms, file extensions, and any 'Use when' phrase, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The named source files (todos.json, archive) and enumerated matching fields give it a clear niche with only minor overlap risk, fitting the 'mostly distinct' anchor above 3.

4 / 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.