CtrlK
BlogDocsLog inGet started
Tessl Logo

configure-notifications

Configure OMX notifications - unified entry point for all platforms

64

Quality

76%

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

62%

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

The content is highly actionable for the generic extensibility paths and clearly sequenced, but the headline native-platform configuration lacks executable commands and the large dev-specific OpenClaw section inflates the file without progressive disclosure. Tightening Step 3 and externalizing 4b-1 would meaningfully improve it.

Suggestions

Add executable jq write commands and explicit value-collection prompts for the native platforms in Step 3 (Discord webhook/bot, Telegram bot token + chat id, Slack incoming webhook), matching the completeness of Steps 4a/4b.

Move the large dev-specific OpenClaw/clawdbot agent workflow (4b-1) and its dev runbook into a separate reference file so the main SKILL.md stays a lean overview and improves progressive disclosure.

Generalize or relocate the hardcoded Discord channel ID and Korean per-hook instructions in 4b-1, and trim the operational notes bullet list to reduce niche inline bloat.

DimensionReasoningScore

Conciseness

The body is mostly efficient concrete jq commands, but the large 4b-1 OpenClaw/clawdbot block with a hardcoded channel ID ("1468539002985644084") and per-hook Korean instructions is niche inline bloat most users won't need and could be tightened or relocated.

2 / 3

Actionability

Steps 4a/4b provide fully executable jq writes, but Step 3 — the first-class native platforms — only directs to "write directly under native keys" without the actual collection fields or jq commands, leaving a key gap.

2 / 3

Workflow Clarity

Steps 1–7 are explicitly numbered and sequenced, with inspection (Step 1), a final smoke check ("npm run build", Step 7), and a dev runbook with error/log inspection in 4b-1 providing verification checkpoints.

3 / 3

Progressive Disclosure

The skill is a single ~260-line file with no bundle references, and the dev-specific 4b-1 workflow/runbook is content that should be split into a separate reference; structure exists but content that should be separate is inline.

2 / 3

Total

9

/

12

Passed

Description

90%

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 well-targeted, pairing a clear one-line purpose with a rich natural-language triggers list that covers verbs and platforms. It clearly answers both what the skill does and when to use it, with low conflict risk.

DimensionReasoningScore

Specificity

"Configure OMX notifications - unified entry point for all platforms" names a clear domain and a single action (Configure) but does not enumerate multiple concrete actions, matching the 'names domain and some actions' anchor rather than the multi-action level above.

2 / 3

Completeness

The description states what the skill does ("Configure OMX notifications") and the explicit `triggers` field provides equivalent explicit trigger guidance for when to use it, satisfying both 'what' and 'when' without hitting the missing-trigger cap.

3 / 3

Trigger Term Quality

The frontmatter `triggers` list covers natural user phrasings across verbs and platforms — "configure notifications", "setup discord", "telegram bot", "slack webhook" — giving broad coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The OMX notification niche with platform-specific triggers (discord/telegram/slack/openclaw) and the stated "unified and only entry point" positioning make it clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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.