CtrlK
BlogDocsLog inGet started
Tessl Logo

note

Note deprecated shim

48

Quality

50%

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

Quality

Content

85%

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

The body is an admirably terse and clear deprecation redirect that respects the token budget and leaves no ambiguity about the single action to take. Its only gap is actionability: it names the replacement surface family but not the specific OMX surfaces or how to reach them.

Suggestions

Name the specific OMX persistent memory/notepad surfaces (and how to invoke them) so the redirect is fully actionable rather than directional.

Remove the literal 'Task: {{ARGUMENTS}}' line if the skill is hard-deprecated and should never execute, since it implies the skill still accepts a task.

DimensionReasoningScore

Conciseness

The body is a lean two-line deprecation notice with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

It gives a concrete redirect ('Use OMX persistent memory/notepad surfaces directly') but lacks specifics on which surfaces or how to access them, fitting 'some concrete guidance but incomplete' rather than fully executable level 3.

2 / 3

Workflow Clarity

This is a simple single-purpose redirect under 50 lines whose single action (do not invoke; use OMX surfaces instead) is unambiguous, so per the simple-skills scoring note workflow clarity scores 3.

3 / 3

Progressive Disclosure

The skill is under 50 lines with no need for external references and is organized under a clear '# Note deprecated' heading, meeting the simple-skills criterion for a top progressive-disclosure score.

3 / 3

Total

11

/

12

Passed

Description

15%

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 is a terse deprecation label rather than a capability statement: it conveys no concrete actions, no usage triggers, and a generic 'Note' term that risks routing conflicts. It reads as a status marker for a retired skill, not as a usable description.

Suggestions

If the skill must remain in the catalog, expand the description to state the concrete capability (e.g., 'Captures and retrieves persistent notes') rather than labeling it a 'deprecated shim'.

Add an explicit trigger clause ('Use when ...') or, for a hard-deprecated skill, state the replacement unambiguously in the description so routing avoids this entry.

Replace generic 'Note' with more specific trigger terms to reduce conflict with other note-related skills.

DimensionReasoningScore

Specificity

The description 'Note deprecated shim' is a label with no concrete actions; it names no verbs or capabilities, matching the vague/abstract anchor rather than the 'names some actions' level 2.

1 / 3

Completeness

It only weakly conveys what the skill is ('deprecated shim') and provides no 'Use when...' trigger guidance, so both what and when are very weak per the level 1 anchor.

1 / 3

Trigger Term Quality

'Note' is a natural keyword a user might say, but 'deprecated shim' is technical jargon and common variations are absent, so it sits at 'some relevant keywords' rather than level 3 coverage or level 1's 'no natural keywords'.

2 / 3

Distinctiveness Conflict Risk

The generic term 'Note' would overlap with many note-related skills, and 'deprecated shim' does not establish a distinct niche, matching the 'very generic; would conflict with many skills' anchor.

1 / 3

Total

5

/

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
Yeachan-Heo/oh-my-codex
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.