CtrlK
BlogDocsLog inGet started
Tessl Logo

configure-notifications

Configure OMX notifications - unified entry point for all platforms

58

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/oh-my-codex/skills/configure-notifications/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 body is highly actionable, with executable commands throughout and a clear sequenced workflow ending in explicit validation. It is lean and well-structured, with only minor conciseness and organization gaps concentrated in the OpenClaw section.

DimensionReasoningScore

Conciseness

The body is lean and command-driven with minimal conceptual padding, though the long inline Korean instruction strings in section 4 and some explanatory prose add tokens that could be factored out.

4 / 5

Actionability

Provides fully executable, copy-paste-ready jq/bash commands for every provider path with clearly marked substitution variables, covering the common configuration cases.

5 / 5

Workflow Clarity

A clear numbered sequence (inspect/choose, native, aliases, OpenClaw, cross-cutting) with an explicit end-of-edit validation checkpoint ("Run `jq empty \"$CONFIG_FILE\"`") and atomic tmp+mv writes; the fix-retry loop is only spelled out at the end rather than per step.

4 / 5

Progressive Disclosure

Well-organized numbered sections with one clearly signaled one-level-deep reference ("Shared ... rules live in `templates/AGENTS.md`"); most detail is appropriately inline for the skill's complexity, with minor organization gaps from the dense OpenClaw block.

4 / 5

Total

17

/

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 is concise and names a clear niche, but it states only a single generic action and provides no explicit "when to use" guidance. Adding platform keywords and a Use-when clause would raise specificity, trigger quality, and completeness.

Suggestions

Add an explicit "Use when..." clause listing concrete trigger phrases (e.g., "Use when configuring Discord, Telegram, Slack, or OpenClaw notifications").

Replace the single generic verb "Configure" with several concrete actions (e.g., "inspect, enable, and disable notifications across Discord, Telegram, Slack, and OpenClaw").

Surface the platform names (Discord, Telegram, Slack, OpenClaw) in the description so natural trigger terms are present, not only in the triggers list.

DimensionReasoningScore

Specificity

Names the domain ("OMX notifications") and a concrete action ("Configure") plus platform scope ("unified entry point for all platforms"), but the verb set is minimal and generic rather than a list of specific actions.

3 / 5

Completeness

Provides a clear "what" but no "Use when..." clause or explicit trigger guidance, so completeness is capped at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Includes relevant natural terms ("configure", "notifications") but omits the platform-specific phrases users would say (Discord, Telegram, Slack); "OMX" and "unified entry point" are technical positioning rather than natural keywords.

3 / 5

Distinctiveness Conflict Risk

"Configure OMX notifications" carves a clear niche with low conflict risk; only minor overlap risk because the description itself lacks the platform-specific triggers that sharpen distinctiveness.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

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.