CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gourmet-organizer

Organize menus and visit notes with grounded tasting analysis and comparisons to earlier experiences. Use when the user shares a restaurant menu, wants a tasting write-up, or asks to merge a visit into Notes/Gourmet.md without overwriting earlier visits.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 well-sequenced, highly actionable instruction skill with concrete house-style rules, source-handling policy, and a self-check step. Its only weaknesses are the duplicated trigger section at the top and a structure that is entirely inline, which is acceptable but leaves minor organization polish.

Suggestions

Remove or shrink the "Use this skill when" section, since it duplicates the frontmatter description and saves ~6 lines of body tokens.

Consider trimming the numbered subsections' prose slightly (e.g., merging step 4 "Sources and safety" bullets into step 1.5's citation rules) to tighten the file toward the lean ideal.

Add one concrete inline example of a finished visit entry (beyond the skeleton pattern) so the house style is unambiguous without adding a separate reference file.

DimensionReasoningScore

Conciseness

The body is lean and policy-dense, assuming Claude's competence with no concept over-explanation; the only trim opportunity is the "Use this skill when" section, which largely duplicates the frontmatter description, matching the efficient-with-minor-trims anchor.

4 / 5

Actionability

Guidance is fully executable for an instruction-only skill: concrete defaults ("Omit receipt-like details by default: price, quantity, serving count"), exact phrasing to use ("品鉴可看", "可与……对照"), named source types to prefer, and a copy-paste output template covering the common case.

5 / 5

Workflow Clarity

A clearly numbered sequence (find landing spot, research, normalize, analyze, write, sources/safety, check) ends with an explicit validation step ("Fix these omissions before reporting completion") forming a fix-and-recheck loop; overwrite protection for prior visits is stated in steps 1 and 4, satisfying the destructive-operation validation requirement.

5 / 5

Progressive Disclosure

The single ~85-line file has well-organized numbered sections with nothing buried or nested, and nothing here belongs in a separate reference file; it sits just above the under-50-line carve-out that would let a reference-free skill score 5, matching the good-structure anchor with only minor organization gaps.

4 / 5

Total

18

/

20

Passed

Description

87%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.

A strong description: third-person, concise, with a clear what and an explicit, concrete when-clause plus a distinctive file-path trigger. It only falls short of top marks on specificity and trigger coverage, where a few more capability verbs and synonyms would help.

DimensionReasoningScore

Specificity

"Organize menus and visit notes with grounded tasting analysis and comparisons to earlier experiences" names several concrete third-person actions, matching the several-specific-actions anchor; it is not a 5 because capabilities like public research and visit merging are only implied through the when-clause rather than stated as actions.

4 / 5

Completeness

It explicitly answers both what ("organize menus and visit notes with grounded tasting analysis and comparisons") and when ("Use when the user shares a restaurant menu, wants a tasting write-up, or asks to merge a visit into Notes/Gourmet.md") with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Natural triggers include "shares a restaurant menu", "wants a tasting write-up", and the concrete path "Notes/Gourmet.md", giving good keyword coverage; common synonyms like "dining notes", "restaurant review", or "menu photo" are missing, keeping it below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The restaurant tasting-note niche, the specific target file Notes/Gourmet.md, and the "without overwriting earlier visits" clause give it a clear niche with distinct triggers and minimal conflict risk against other skills.

5 / 5

Total

18

/

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

Path

.codex/skills/gourmet-organizer/SKILL.md

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.