CtrlK
BlogDocsLog inGet started
Tessl Logo

novu-dashboard-workflows

Author step content for Novu workflows defined in the Dashboard or generated/edited via the Novu MCP. Use when filling in step controls (subject, body, editorType, headers, body, conditions) for email, in-app, sms, push, chat, delay, digest, throttle, or HTTP Request steps.

72

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary routing-style skill: concise, entirely composed of non-obvious domain rules, with concrete right/wrong examples and a clean one-level-deep reference structure that matches the actual bundle. The only gap is a missing post-edit verification checkpoint, which keeps workflow clarity at 4 rather than 5.

DimensionReasoningScore

Conciseness

The body is lean and every token is domain knowledge Claude cannot infer (Block Editor bare-variable exception, responseBodySchema-only response fields, empty-array vs empty key/value entries). It assumes competence and includes no padding or generic explanation of Novu, Liquid, or notifications.

5 / 5

Actionability

Guidance is fully concrete and copy-paste ready: exact variable syntax ('{{ subscriber.firstName }}'), explicit wrong/right examples ('"{{ payload.actionUrl }}"' is wrong; '"payload.actionUrl"' is right), a worked steps.fetch-user.name example, and exact JSON for merge/replace/null condition semantics, covering the common cases per step type.

5 / 5

Workflow Clarity

The routing sequence is clear and coherent ('Open the matching reference before writing controls', when-to-use examples, add-vs-replace decision rules), but there is no validation checkpoint after writing step content (e.g., confirming the workflow validates or renders correctly) — a minor checkpoint gap.

4 / 5

Progressive Disclosure

The SKILL.md is a clear overview that routes each of the ten step types to a real one-level-deep reference file via a well-signaled table, keeps common pitfalls inline, and cross-links sibling skills — easy navigation with content appropriately split.

5 / 5

Total

19

/

20

Passed

Description

88%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: it states a clear, concrete 'what' with an exhaustive enumeration of controls and step types, and an explicit 'Use when' clause with natural trigger terms. The only weaknesses are a few missing synonyms and the absence of an explicit boundary against adjacent Novu skills.

DimensionReasoningScore

Specificity

The description names multiple concrete actions ('Author step content', 'filling in step controls') and enumerates the specific controls (subject, body, editorType, headers, conditions) plus all nine step types, giving comprehensive coverage of the domain rather than minor gaps.

5 / 5

Completeness

It explicitly answers both parts: 'Author step content for Novu workflows defined in the Dashboard or generated/edited via the Novu MCP' states what it does, and 'Use when filling in step controls (...) for email, in-app, sms, push, chat, delay, digest, throttle, or HTTP Request steps' gives concrete trigger phrases for when to use it.

5 / 5

Trigger Term Quality

Good natural keyword coverage — 'email', 'sms', 'subject', 'body', 'headers', 'Novu', 'Dashboard', 'MCP' — that users would plausibly say when needing this skill. A few natural synonyms like 'notification', 'message', or 'template' are missing, so it falls just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The Novu Dashboard/MCP step-content niche is distinct with channel-specific triggers, but the description does not delimit against closely related sibling skills (e.g., code-based @novu/framework authoring or workflow triggering), leaving minor overlap risk.

4 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 5 suspicious

Warning

Total

14

/

16

Passed

Repository
novuhq/novu
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.