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.

74

Quality

93%

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

87%

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

A well-organized, concise instruction skill that routes to per-step-type references and gives concrete syntax rules with right/wrong pitfall pairs. Its main gap is the absence of an explicit validation/checkpoint step after MCP step writes, which keeps workflow clarity below top.

Suggestions

Add an explicit validation checkpoint after writing step controls (e.g., re-read the step via the MCP or confirm editorType/variables resolve) so the workflow has a verify-then-fix feedback loop.

Surface a short post-edit checklist (variables resolve, no hardcoded URLs, editorType preserved, conditions merged vs replaced as requested) that mirrors the Common Pitfalls section as a closing verification step.

Make the recommended order explicit in one line — e.g. 'identify the step type → open its reference → fill controls → run the verification checklist' — so the sequence is unambiguous rather than implied by section order.

DimensionReasoningScore

Conciseness

Lean body that assumes Claude knows Novu concepts — no padding explaining what Novu or workflows are — with rules given as tight bullets and concrete syntax examples; every section earns its place.

3 / 3

Actionability

Concrete, specific guidance throughout — exact Liquid variable syntax ({{ subscriber.firstName }}, {{ payload.* }}), bare-vs-curly rules for Block Editor, and right/wrong pitfall pairs — which is actionable for an instruction-only skill even without executable code.

3 / 3

Workflow Clarity

A clear sequence is present (When to use → Step Content Guidelines → step-type table → Common Pitfalls) and the pitfalls act as a checklist, but there is no explicit validation/checkpoint step for verifying MCP-written step content, so it sits at the 'sequence present but checkpoints implicit' level rather than 3.

2 / 3

Progressive Disclosure

SKILL.md is a concise overview with one-level-deep references via the step-type table and inline links; all 10 referenced files (email-step.md, in-app-step.md, etc.) exist under references/ and navigation is easy.

3 / 3

Total

11

/

12

Passed

Description

100%

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, third-person description that names concrete control fields and a comprehensive list of step types, with an explicit 'Use when' trigger clause and a clear Novu-specific niche. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and specific control fields — "filling in step controls (subject, body, editorType, headers, body, conditions)" across a named set of step types — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both 'what' ("Author step content for Novu workflows...") and 'when' ("Use when filling in step controls...") with an explicit Use-when clause.

3 / 3

Trigger Term Quality

Natural terms users would say are well covered — "email, in-app, sms, push, chat, delay, digest, throttle, or HTTP Request steps" plus "Novu workflows", "Dashboard", and "Novu MCP".

3 / 3

Distinctiveness Conflict Risk

The Novu / Dashboard / MCP niche and enumerated step types make it clearly distinguishable and unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation14 / 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.