CtrlK
BlogDocsLog inGet started
Tessl Logo

gourmet-organizer

整理美食笔记,品鉴菜单,结合用户的美食品鉴经历

49

Quality

53%

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

Quality

Content

57%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 skill is compact and cleanly sectioned, but its core executable path is broken: main.py is referenced yet missing from the bundle, the example command has malformed quoting, and the workflow never explains how Gourmet.md is created, located, or validated. A user following the steps could not actually run anything.

Suggestions

Ship the referenced script in scripts/ (or correct the invocation to whatever actually exists) and fix the malformed command/quoting in 使用步骤 and 示例.

Specify the full workflow around Gourmet.md: where the file lives, what to do on first use when it doesn't exist, the expected note format/structure to append, and how to verify the entry was written correctly.

Clarify the non-obvious behaviors — the hidden-emphasis instruction (隐性强调用户感受) and web-search option — with a concrete input/output example instead of one-line feature bullets.

DimensionReasoningScore

Conciseness

The body is short and lean with no explanations of concepts Claude already knows — every section carries instructions. It earns 4 rather than 5 only because 适用场景 and 功能特点 largely restate the frontmatter description, which is slight redundancy that could be trimmed.

4 / 5

Actionability

It provides concrete commands (`python main.py "<美食内容>"` and `python main.py --file menu.txt`) with a realistic example, matching 'Some concrete guidance but incomplete'. It is not 4 because the referenced main.py does not exist anywhere in the bundle, the command line has a broken closing quote, and there is no explanation of the script's inputs, outputs, or where Gourmet.md lives.

3 / 5

Workflow Clarity

A three-step sequence is present (prepare content → run script → script organizes notes), but there are gaps: a missing closing parenthesis in step 1, no location or provenance for main.py and Gourmet.md, no guidance when Gourmet.md doesn't exist yet, and no validation or error handling — matching 'Steps listed but validation gaps; sequence present but checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

The body is short with well-labeled sections (适用场景/功能特点/使用步骤/示例), which is good, but it references files (main.py, Gourmet.md) that are absent from the bundle — no scripts/, references/, or assets/ directories exist — leaving navigation to nonexistent targets. This matches 'Some structure but could be better organized; references present but not clearly signaled'.

3 / 5

Total

13

/

20

Passed

Description

50%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 coherent, domain-scoped set of capabilities but stops there: no 'when to use' trigger clause, no synonyms or natural user phrasings, and only abstract verbs rather than concrete operations. It is serviceable but well short of the good examples that pair a concrete 'what' with an explicit 'when'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to organize food/gourmet notes, review or comment on a menu, or record a dining/tasting experience.'

Enumerate concrete actions and outputs instead of abstract verbs, e.g. 'analyze menus, record tasting impressions, merge new entries into the user's Gourmet.md note file, and optionally search the web for dish background.'

Include natural synonyms users would actually say (菜谱, 美食日记, 点评, 用餐记录) so the skill triggers on varied phrasing and stays distinct from generic note-taking skills.

DimensionReasoningScore

Specificity

The description names its domain (美食笔记/品鉴) and three actions — "整理美食笔记", "品鉴菜单", "结合用户的美食品鉴经历" — but these are abstract verbs (organize, taste, combine) without concrete operations or outputs, matching 'Names domain and 1-2 concrete actions, but not comprehensive'. It falls short of 4 because the actions lack the specificity of examples like 'Extracts text, fills forms, converts pages'.

3 / 5

Completeness

There is a clear 'what' (organize gourmet notes, taste menus, integrate the user's tasting history) but no 'Use when…' or equivalent 'when' clause at all, matching 'Has a clear what but when is missing or only weakly implied'. Per the judging guidelines, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords are present (美食笔记, 菜单, 品鉴, 经历) that a user might say, but common variations and synonyms (菜谱, 美食日记, 点评, 评价) are missing, matching 'Some relevant keywords but missing common variations or synonyms'. Not 4 because coverage is thin and no file extensions or natural trigger phrases appear.

3 / 5

Distinctiveness Conflict Risk

The gourmet/menu-tasting domain is somewhat specific, but '整理笔记' style phrasing overlaps with generic note-organizing and journaling skills, matching 'Somewhat specific but could still overlap with similar skills'. Not 4 because there is no distinct trigger phrasing to separate it from those neighbors.

3 / 5

Total

12

/

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.