Name: novu
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

novu

Novu integration. Manage data, records, and automate workflows. Use when the user wants to interact with Novu data.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/novu/SKILL.md

Quality

Content

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

The content is highly actionable with concrete, executable Membrane CLI commands and a well-instrumented connection workflow including validation and retry loops. Its only notable weakness is a padded introductory paragraph that over-explains concepts Claude already knows.

Suggestions

Trim or remove the opening paragraph explaining what Novu is and how developers use it; Claude already knows this and it costs context tokens.

Consolidate the duplicated action-search command between 'Searching for actions' and 'Popular actions' into a single canonical section to avoid repetition.

Add an explicit end-to-end numbered workflow (search -> run -> proxy fallback) with a final verification of the output field, to raise workflow clarity to anchor 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands, but opens with a two-sentence explanation of what Novu is and how developers use it — background Claude largely already knows — which is unnecessary padding, matching anchor 3 rather than the lean anchor 4-5.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands for install, login, connection ensure, action search/run, and proxy requests, plus a concrete flag table and JSON input examples covering the common cases, matching anchor 5.	5 / 5
Workflow Clarity	The connection setup has a clear state-driven sequence with explicit polling/validation checkpoints and a feedback loop (poll -> CLIENT_ACTION_REQUIRED -> user acts -> poll again), but the action-discovery and action-running sections are only loosely sequenced without the same rigor, fitting anchor 4 rather than a fully checkpointed anchor 5.	4 / 5
Progressive Disclosure	No bundle files exist and the content is single-file with reasonable section headers; for a self-contained integration skill this is well-organized, though 'Popular actions' largely re-states the earlier search command rather than adding structure, keeping it just below a clean anchor 5.	4 / 5
	Total	16 / 20 Passed

Description

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

The description correctly uses third-person voice and covers both what and when, with a clear Novu-specific niche. Its main weakness is generic, non-concrete action language and a thin set of natural trigger keywords that miss common Novu terminology.

Suggestions

Replace generic actions with concrete Novu operations, e.g. 'Manage notification templates, subscribers, integrations, topics, and events' to lift specificity.

Expand the trigger clause with natural user phrases: 'Use when the user wants to send or manage Novu notifications, templates, subscribers, or events.'

Add file-extension or domain cues (e.g. '.novu', 'docs.novu.co') to strengthen distinctiveness and trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the Novu domain and a couple of actions ('Manage data, records, and automate workflows'), but those actions are generic abstractions rather than concrete Novu operations (templates, subscribers, events, topics), placing it at anchor 3 rather than the more comprehensive anchor 4.	3 / 5
Completeness	Explicitly provides both a 'what' ('Manage data, records, and automate workflows') and a 'when' ('Use when the user wants to interact with Novu data'); the 'when' is explicit but could be more specific about Novu scenarios, fitting anchor 4 rather than the fully concrete anchor 5.	4 / 5
Trigger Term Quality	Includes the natural trigger phrase 'Use when the user wants to interact with Novu data' and the keyword 'Novu', but misses common user variations and synonyms such as 'notifications', 'notification templates', 'subscribers', or 'events', matching anchor 3.	3 / 5
Distinctiveness Conflict Risk	Targets a clear niche (the Novu platform) with a distinct trigger ('interact with Novu data') and minimal conflict risk, though the generic 'manage data, records, automate workflows' phrasing leaves minor overlap with broad data/automation skills, matching anchor 4.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/novu/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.