CtrlK
BlogDocsLog inGet started
Tessl Logo

novu-design-workflow

Design notification workflows the Novu way — choose channels, set severity, decide when a workflow is critical, configure digests, and route based on subscriber state. Applies to BOTH dashboard-authored and code-first (`@novu/framework`) workflows. Use when planning a new workflow, deciding which channels to include, picking severity, configuring digest behavior, or matching a use case (order confirmation, payment failed, account suspended, comment, trial expiring, password reset, webhook fan-out, fetch-then-notify) to a proven template.

79

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A well-structured design skill: concise, table-driven, and highly actionable with concrete defaults and copy-ready templates. It uses clean one-level-deep progressive disclosure to real reference files and includes a pitfalls checklist that doubles as a design-validation step.

DimensionReasoningScore

Conciseness

Lean and table-driven with no padding or explanation of concepts Claude already knows; every section (severity, channels, digest, user-state, templates, pitfalls) earns its place and assumes competence.

3 / 3

Actionability

Gives executable concrete guidance: exact channel priority order, specific digest defaults (type, 5-min look-back, 1-hour time, subscriberId key), a real JSON-Logic snippet, framework skip callback, and a template table with concrete severity/critical values — copy-ready for an instruction/design skill.

3 / 3

Workflow Clarity

Design decisions are sequenced into clear topical stages (severity & critical → channel selection → digest → user-state → templates → conditions) with a "When to use"/"Do not use" boundary and an 8-item Common Pitfalls checklist that functions as the validation/review checkpoint; no destructive or batch operation triggers the cap.

3 / 3

Progressive Disclosure

Clear overview in SKILL.md with well-signaled one-level-deep references to ./references/{channel-selection,severity-and-critical,digest-defaults,step-conditions,workflow-templates}.md — all five are real bundle files — plus a consolidated References section for easy navigation; no nested reference chains.

3 / 3

Total

12

/

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 high-quality description that names concrete capabilities, gives an explicit Use-when trigger clause with natural use-case keywords, and carves out a distinct Novu-specific niche. It answers what, when, and for whom without padding or first/second-person voice.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "choose channels, set severity, decide when a workflow is critical, configure digests, and route based on subscriber state" — matching the anchor for listing several specific capabilities rather than vague abstractions.

3 / 3

Completeness

Explicitly answers both what ("Design notification workflows ... choose channels, set severity ...") and when via an explicit "Use when ..." trigger clause, satisfying the top anchor; voice is third-person/imperative with no first- or second-person penalty.

3 / 3

Trigger Term Quality

Strong natural-term coverage in the "Use when" clause — "planning a new workflow", "picking severity", "configuring digest behavior" — plus concrete use-case phrases users would actually say ("order confirmation, payment failed, account suspended, ... trial expiring, password reset").

3 / 3

Distinctiveness Conflict Risk

Clear Novu-specific niche with distinct triggers and a named scope (dashboard-authored vs code-first @novu/framework), making it unlikely to fire for an unrelated skill.

3 / 3

Total

12

/

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

relative_links

Relative link issues: 11 suspicious

Warning

Total

15

/

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.