CtrlK
BlogDocsLog inGet started
Tessl Logo

novu-framework-integration

Build code-first notification workflows with @novu/framework. Use when defining workflows in TypeScript (Zod / JSON Schema / Class Validator), composing channel steps (email, SMS, push, chat, in-app) with action steps (delay, digest, custom), exposing Step Controls for non-technical teammates, rendering React/Vue/Svelte Email templates, hosting the Bridge Endpoint inside Next.js, Express, NestJS, Remix, Nuxt, SvelteKit, H3, or AWS Lambda, syncing to Novu Cloud via CLI / GitHub Actions, securing production with HMAC, or implementing translations, hydration, multi-channel orchestration, and LLM-powered notification logic in code.

71

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A comprehensive, highly actionable reference with excellent progressive disclosure into a real reference bundle. The main weakness is mild verbosity and some duplicated examples that could be tightened without losing clarity.

Suggestions

Consolidate the two in-app step examples into a single illustrative block to remove redundancy and trim token weight.

For deployment/sync, add an explicit validate-fix-retry checkpoint (e.g., what to do when `npx novu sync` reports a missing or renamed workflow) to lift workflow_clarity from 4 to 5.

Prune prose around the channel-step table that restates values already shown in the table itself.

DimensionReasoningScore

Conciseness

Mostly efficient reference tables and copy-paste code with little padding or over-explanation of known concepts, but the body is long with minor redundancy (e.g., the in-app step is illustrated twice) that could be trimmed.

4 / 5

Actionability

Fully executable code for every channel/action step, every framework serve wrapper, each schema variant, and concrete CLI/CI commands — copy-paste ready and covering the common cases thoroughly.

5 / 5

Workflow Clarity

A clear sequenced 'How It Works' and numbered Quick Start, plus an explicit Common Pitfalls checklist serving as validation guidance; the GitOps deploy flow is sequenced, though without an explicit validate-fix-retry loop for sync failures.

4 / 5

Progressive Disclosure

An overview body with well-signaled, one-level-deep references to 9 real reference files (e.g., ./references/bridge-endpoint.md, verified present), with the bulk of exhaustive detail pushed into those files and a clear References map at the end.

5 / 5

Total

18

/

20

Passed

Description

92%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, concrete description that covers what the skill does and when to invoke it, with comprehensive action and trigger coverage. The only minor gap is that the trigger enumeration is technical rather than phrased as natural user utterances.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'defining workflows in TypeScript (Zod / JSON Schema / Class Validator)', 'composing channel steps (email, SMS, push, chat, in-app) with action steps (delay, digest, custom)', 'hosting the Bridge Endpoint inside Next.js, Express, NestJS...', 'securing production with HMAC' — comprehensive coverage of the skill's surface.

5 / 5

Completeness

Explicitly answers both — 'what' ('Build code-first notification workflows with @novu/framework') and 'when' ('Use when defining workflows in TypeScript...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong coverage of natural terms ('notification workflows', 'email, SMS, push, chat, in-app', framework names, 'syncing', 'HMAC', 'translations', 'digest') but the 'Use when' clause leans on a long technical enumeration rather than natural user phrasings like 'when the user mentions X'.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to '@novu/framework' and code-first workflows, with the cross-reference to trigger-notification for dashboard workflows sharpening the niche; minimal overlap with sibling skills.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (831 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 5 suspicious

Warning

Total

13

/

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.